On Wed, Mar 05, 2025 at 10:12:05PM +0100, Matthias Urlichs wrote:
On 05.03.25 21:35, Marc Haber wrote:
And which of the millions of changes would that be that would break
YOUR system?
The number of changes that can adversely impact your ability to boot
*or* your network connectivity (but which won't fail the upgrade!) can
safely be assumed to be smaller than five or so.
And which of the millions are those five? Any small number of "false
alerts" already will cause users to stop reading.
Maybe we could introduce a new header field where a package might create
itself as "probably harmful to the reboot" (like grub, initramfs-tools,
network-manager, systemd etc) and have their NEWS entries sorted first
by apt-listchanges.
But I think that it is unrealistic to expect maintainers to classify
their changes whether they might affect reboot.
Running a headless server without console access is a challenge. You
_really_ need to know your way to debug such a situation. I don't think
that we as a distribtion can change that.
In the current case, it's only a matter of hooking up a display and
keyboard to a physically accessible system. It could be a housing server
in a datacenter next time (been there, done that).
Greetings
Marc
--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
