Hello Helge, > Do you have any idea what both anacron.service and anacron.timer are > disabled? > > So somehow anacron -34 disabled both the service and the timer. > > Anything you want me to look at? > > Next step would be how to properly enable them again… > > Thanks! > > Greetings > > Helge
I believe I've found the issue! Sorry it has taken so long to get back to you but I believe I have an answer. It seems to be related to an inadequate cleanup. I don't have a great explanation but I found something that works. The -33 version that removed the symlinks *somehow* (I am not sure) corrupted the whole install. I've found that uninstalling anacron, removing the files associated with anacron and then re-installing the package (-35) will yield a service that works. Specifically, I removed: /var/lib/systemd/deb-systemd-helper-*/ ... anacron files [might not be needed?] /var/lib/dpkg/info/anacron.* files [might not be needed?] /var/spool/anacron /etc/anacrontab [I think this file is the problem!!] Since you already have cron files, perhaps you could back them up, uninstall anacron, remove the files, and then re-install anacron (-35), and then overlay your existing cron files? Would you be so kind to test this out on your machine and see if this fixes it? If it does, I will need to ask mentors on the best solution for this problem as it seems to be introduced in -33 but will only impact users who upgraded to -33 at some point. Going from -32 to -35, for instance, should not cause problems. I've even made a notional -36 version to verify that once the service is running, the upgrade works smoothly. Thank you for your help in tracking this down! Lance Lin <lqi...@protonmail.com> GPG Fingerprint: 4A31 DB5A 1EE4 096C 8739 9880 9036 4929 4C33 F9B7
signature.asc
Description: OpenPGP digital signature
