On 2023-01-08 02:56 +0100, Vincent Lefevre wrote: > On 2023-01-07 20:05:59 +0100, Sven Joachim wrote: >> >> If not, you may have been bitten by bug #1019554 in >> >> anacron which needs manual restore as mentioned in >> >> https://lists.debian.org/debian-devel-announce/2022/11/msg00001.html. >> > >> > 2022-07-14 20:57:59 upgrade anacron:amd64 2.3-32 2.3-33 >> > 2022-07-14 20:57:59 status half-configured anacron:amd64 2.3-32 >> > 2022-07-14 20:57:59 status unpacked anacron:amd64 2.3-32 >> > 2022-07-14 20:57:59 status half-installed anacron:amd64 2.3-32 >> > 2022-07-14 20:57:59 status unpacked anacron:amd64 2.3-33 >> >> Note that the anacron bug only makes itself apparent after the upgrade >> to a later version, since that would run the faulty postrm from 2.3-33. > > I track the diffs in etc, and it seems that 2.3-33 and later did > nothing wrong.
This assumption is incorrect, see #1019554 and siblings. > Dangling symlinks were removed after the upgrade > to anacron 2.3-34, but these were *dangling* symlinks, so that > this should have no effect. See the bug I reported: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993348 > > Dangling symlinks are bad as they can break other tools > (e.g. checkrestart, which was the reason I reported this bug). I do not like dangling symlinks either, however systemd works fine with them. Even if the unit is below /usr/lib/systemd/system and the symlink in /etc points to a file below /lib/systemd/system, systemd still activates the unit to accommodate system without a merged /usr. >> What does "systemctl status anacron.service" print? > > ○ anacron.service - Run anacron jobs > Loaded: loaded (/lib/systemd/system/anacron.service; disabled; preset: > enabled) > Active: inactive (dead) > Docs: man:anacron > man:anacrontab > > And anacron is no longer in the timers (systemctl list-timers). That is your problem, you need to reenable and restart these units. # systemctl enable anacron.service anacron.timer # systemctl start anacron.service anacron.timer See the d-d-a link I gave in my first reply, https://lists.debian.org/debian-devel-announce/2022/11/msg00001.html. Cheers, Sven