On Thu, 24 Sep 2015, Marvin Renich wrote: > How does failing the upgrade solve anything? The upgrade should only > fail if the failure of the service to start was because something in the > upgrade itself was broken; this is rarely the case.
... > What makes this even worse is that when installing or upgrading a large > number of packages, this kind of incorrect failure sometimes affects > many completely unrelated packages. For an unattended upgrade, this is > so much worse than having one service that (for a correct reason) > refused to restart after the upgrade. What we really want is a "do not fail upgrade, BUT report that some services *that were previously running* failed to restart after the upgrade run". ESPECIALLY if you are going to take "unattended upgrades" seriously. Still, that would need some proper design work, and a reasonable amount of code to be written and tested. Some of it will hook into the package system, some of it needs to interface to the services subsystem (systemd, sysvinit, others). -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
