On 2023-01-10 13:35:03 +0000, Lance Lin wrote: > > Something should be done, such as a warning in the NEWS.Debian file > > (or perhaps in some script during an upgrade). > > Would adding to the README.Debian file be sufficient? If so I'll > push a new update.
No, it wouldn't. I doubt that any user reads the README.Debian file of any upgraded package, possibly except when a breakage is noticeable. Here, the issue with anacron is only due to an upgrade, and the breakage is typically not noticeable as the cron scripts do not give any feedback (except in case of error, which normally doesn't occur). In my case, it took me 3 months to notice that something was wrong, and I didn't even know that the cause was that anacron was disabled. On the opposite, new entries of NEWS.Debian are shown after upgrades thanks to apt-listchanges. This file is normally used to inform the admin of major changes of the behavior (either on purpose or due to bugs), and the fact that anacron got disabled is such a major change (here, due to a bug). Alternatively, the postinst script could check whether the symlinks are missing (and remember that for the future upgrades), and if they are missing, this is probably due to this bug. So it could propose the user to re-enable anacron. -- 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)
