Hi Michael, Sorry for the delay, I forgot to actually send :(
On Sat, Jul 4, 2020, 14:06 Michael Biebl <bi...@debian.org> wrote: > Hi Felipe > > On Tue, 20 Dec 2016 09:46:38 -0300 Felipe Sateler <fsate...@debian.org> > wrote: > > Control: forwarded -1 https://github.com/systemd/systemd/issues/4930 > > > > On Mon, 17 Nov 2014 12:46:38 +0100 Alexandre Detiste > > <alexandre.deti...@gmail.com> wrote: > > > Package: init-system-helpers > > > Version: 1.21 > > > Severity: minor > > > > > > Dear Maintainer, > > > > > > When a timer unit with flag "Persistant=true" is purged, > > > a loose time stamp (0 byte file) is left loose > > > in /var/lib/systemd/timers/stamp-<unit-name>.timer > > > > > > This file could be safely removed by deb-systemd-helper during a purge. > > > > I'd really rather not rely on implementation details. I have forwarded > > the bug to systemd upstream so they provide an interface to clear the > > stamp files. When that is done, we can add that invocation in > > deb-systemd-helper. > > We now do have a "systemctl clean" interface. > Should we simply run that unconditionally on deb-systemd-helper purge? > For all unit types or only timers? > Maybe we could just have a trigger in systemd? > I also note, that this apparently doesn't work in chroots: > # systemctl clean apt-daily.timer > Running in chroot, ignoring request: clean > Bummer, but I don't think it is too important. After all, chroots wouldn't have run systemd in the first place, and thus wouldn't have the file. > Not sure if this is something we should be concerned about. > I don't think it is too important. After all, this is mostly a nice to have. Saludos > Regards, > Michael > > > >