Arguably, a workaround might be to remove support for the interval options now, and then treat it as "one day", and just check that %Y-%m-%d for today != the one for the stamp.
This addresses the problem with DST, and breaks every non-default configuration. Which is something we will have to live with eventually anyway I guess.
So basically speaking, under systemd, intervals will always be "not the same day", other settings will be ignored and produce a warning, and you're supposed to configure the timer. This still allows us to play catch up by running the timer multiple times per day, until we get a fixed systemd.
Under non-systemd systems in Debian, stuff will continue to work as it does now.
Arguably, a workaround might be to remove support for the interval options now, and then treat it as "one day", and just check that %Y-%m-%d for today != the one for the stamp.
This addresses the problem with DST, and breaks every non-default configuration. Which is something we will have to live with eventually anyway I guess.
So basically speaking, under systemd, intervals will always be "not the same day", other settings will be ignored and produce a warning, and you're supposed to configure the timer. This still allows us to play catch up by running the timer multiple times per day, until we get a fixed systemd.
Under non-systemd systems in Debian, stuff will continue to work as it does now.