Hello, вс, 2 окт. 2022 г. в 22:36, Steve Langasek <vor...@debian.org>: > > On Sun, Oct 02, 2022 at 03:53:00PM +0100, Steve McIntyre wrote: > > >What's the plan for upgraded systems with an existing > > >/etc/apt/sources.list. > > >Will the new n-f-f section added on upgrades automatically(if non-free was > > >enabled before)? > > > So this is the one bit that I don't think we currently have a good > > answer for. We've never had a specific script to run on upgrades (like > > Ubuntu do), so this kind of potentially breaking change doesn't really > > have an obvious place to be fixed. > > > Obviously we'll need to mention this in the release notes for > > bookworm. Should we maybe talk about adding an upgrade helper tool? > > I heartily endorse ubuntu-release-upgrader, it has been useful in addressing > uncounted upgrade issues over the years and I think something like this > would be a nice addition to Debian as well. Two caveats:
I'd kindly ask against additional upgrade scripts. It is too easy to miss them, especially if one has been using Debian for ages with bare apt-get update && apt-get dist-upgrade. Moreover such a script will not help people that are already using testing. For the past few decades, updating the setup was always a job of the package scripts. Thus we potentially can have an addon in the apt's postinstall script that will check if the user is running bookworm, the non-free repo is enabled and non-free-firmware is not. In such case postinst can present user with a choice of ignoring n-f-f, attempting automatic '/bookworm/s/non-free/non-free non-free-firmware/' or letting user to fix setup. This way the user will be present with such choice whichever path he uses to update to bookworm. -- With best wishes Dmitry
