On 2016-12-23 20:10:23 +0100, Martin Steigerwald wrote: > Am Freitag, 23. Dezember 2016, 19:37:33 CET schrieb Vincent Lefevre: > > This is not an inflated severity. Under no circumstances, the > > installation of a package should make dpkg fail and leave the > > packaging system in an inconsistent state (this can block the > > correct installation of other packages). Well, actually here > > the problem came from the old package from experimental, but > > I wasn't aware of this. > > The packaging system is not in an inconsistent state: You can always remove > the package that fails to upgrade. Or pin it to a certain version to prevent > an update.
No, I mean that is case of error, it may happen that other packages in the upgrade do not get configured (I already got this problem), and the user needs to fix this manually (e.g. dpkg --configure -a), otherwise some part of the system may be broken. > Yes. So to really test this: > > - Downgrade to atop 1.26 > - Reboot, or make sure atopacctd is stopped and remove /run/pacct_shadow.d > directory. > - Upgrade to 2.26. After removing the /run/pacct_shadow.d directory, this works. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
