How do I know when #Guix has merged the ’core-updates’ branch bringing many package updates? 🤔 when I pause my current tasks and instead fix annoyances. 😀
How do I know when #Guix has merged the ’core-updates’ branch bringing many package updates? 🤔 when I pause my current tasks and instead fix annoyances. 😀
@zimoun The tiny-teensy team that took care of ‘core-updates’ (myself included) did lots of testing, tons of fixing, and put out calls for testing and an advanced notice before the merge.
I think it’s the first time this branch is merged with so few problems detected afterwards.
The Emacs and Git issues are problematic; apparently they could only be detected through regular use, and perhaps individuals didn’t go that far when testing things on their machine before the merge.
Gregory's Server
@zimoun The tiny-teensy team that took care of ‘core-updates’ (myself included) did lots of testing, tons of fixing, and put out calls for testing and an advanced notice before the merge.
I think it’s the first time this branch is merged with so few problems detected afterwards.
The Emacs and Git issues are problematic; apparently they could only be detected through regular use, and perhaps individuals didn’t go that far when testing things on their machine before the merge.
@khinsen
@zimoun (Actually, the Emacs ‘transient.el’ issue predates the ‘core-updates’ merge.)
@khinsen
@zimoun Thanks for the info, I was about to debug the transient issue myself! 😃