Il 06/03/2025 09:43, Holger Levsen ha scritto:
On Tue, Mar 04, 2025 at 08:39:43PM -0500, Helmut K. C. Tessarek wrote:
Both network "outages" could have been prevented by adding a note at the end
of the dist-upgrade output.
they could also have been prevented by reading the release notes and following
their advice.

that would also have prevented this wonderful bikeshedding thread.

sorry to state the obvious.


I think the things to do can be summed up as follows: read release note of new major version and NEWS entries

If you are upgrading important or critical systems try also:

- test before in a testing system, or vm. or even just start from a less critical one

- try to have additional access in case of unforeseen events (there are not only the network ones mentioned in this discussion that can prevent the boot but also other undocumented and/or specific ones to the system or to a part of it). I mean for example an access from the host in case of vm or an ipmi system in case of physical server.

- if you don't have much time to read the whole release note read at least the "Upgrade specific items" part, for example for buster there is "5.1.6. Migrating from legacy network interface names".

- if you don't have time to read NEWS every update do it at least for the first time so you can see all the common ones on the basic packages, for example however it can be useful to have a quick look at each update and read those of specific programs to be aware of important or essential changes and save time rather than having problems later, perhaps not noticing the problems immediately or not being able to find the cause immediately


Regarding possible improvements I think the only thing that can be added is a check to the upgrade operations and if it is detected that you are upgrading to packages of the next major version add a simple initial warning (but not a big "image" as suggested in topic start) in which it is recommended to read the release notes, especially the "Upgrade specific items" part, and the NEWS of the packages.

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to