Lucie / minute
I heard we merged Linux kernel 6.19 for MNT Reform series, available now in an `apt` near you! thanks to @josch for leading this effort and to everyone who tested, including @vimja and @vagrantc
Mar 21 at 1:37pmWeb
Show threadwakest likes your bugs ⁂6d ago
@mntmn @josch maybe a good opportunity to remind people to `apt full-upgrade` so they don't bork their system like I did!
Show threadjosch5d ago
@liaizon @mntmn Well, you can still bork your system with "apt full-upgrade" and maybe even more so because it will happily remove packages. We had people in the forum who didn't pay attention and ended up removing important packages during an "apt full-upgrade". Nevertheless I suggested this change for the handbook here: https://source.mnt.re/reform/reform-handbook/-/merge_requests/22
src/source/software.rst: suggest using "apt full-upgrade" instead of "apt upgrade" (!22) · Merge requests · Reform / reform-handbook · GitLab

The difference between "apt upgrade" and "apt full-upgrade" is, that the latter is allowed to remove packages and old kernel images. The former is recommended for Debian stable...

GitLab
Show threadChristian Gmeiner6d ago
@mntmn @josch @vimja @vagrantc wonderful - thanks a lot!
Show threadBenis5d ago
@mntmn @josch Is Josch the only person who does this? Or how does this work for MNT devices?
Show threadjosch5d ago
@b3nis Far from it. The usual process is, that once a new kernel release gets uploaded by the Debian kernel team somebody (sometimes me, sometimes @vimja sometimes @mntmn starts porting the patch stack of the current version to the new version and opens a merge request against reform-debian-packages. Then people install the Debian packages produced as CI artifacts, report and fix issues on all platforms MNT supports. Once everything checks out, @mntmn merges or gives the go-ahead to do so.
Show threadBenis5d ago
@josch @vimja @mntmn Ah, glad to hear that. And thanks for explaining.