Dear Lance,
This is a problem, since obviously many things rely on these cron jobs running
regularly.
For example, one of my SSL certificates expired because of this.
Kind regards,
Ralf
I have merged this bug with #1019554.
The problem was introduced in -33. I've noticed that it resulted in an
incomplete cleanup on upgrade. It has been fixed in -35 but the service still
doesn't start due to the cleanup.
Ah, indeed the service was 'disabled'.
My tested working solution is to backup existing cron files, remove anacron,
manually remove the files and install the -35 version.
Specifically, I removed:
/var/lib/systemd/deb-systemd-helper-*/ ... anacron files
/var/lib/dpkg/info/anacron.* files
/var/spool/anacron
/etc/anacrontab
Sorry for the inconvenience. Please let me know if this works as it seems to
fix it on my system.
Uh, that sounds pretty scary. I already have the -35 installed so the buggy
postrm should be gone. Shouldn't it be enough to manually enable and start the
service and timer? I have done that now.
FWIW I agree with the sentiment in that bug that anacron should not touch any of
these systemd files in its postrm or purge logic. That's what the
init-system-helpers are for. They are very well-tested and if they leave behind
dangling symlinks that should be brought up with them. Fixing it only for
anacron wouldn't help other packages.
Kind regards,
Ralf
