This IS related to daylight saving.
The script: /usr/lib/apt/apt.systemd.daily check that the script is not
run twice at the same period.
The script checks the date of today and the date of the last timestamp to
determine the the diff.
The interval is calculated using the number of seconds per d
It will not run after 36h either. It will not run until next day because
"yesterday" did not have 24 hours until next day.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1824088
Setting TZ for the complete script will not work as it will make strange
behaviour if you are far away from UTC/GMT TZ. You can set it for just
the date command that returns the epoch time.
I did a patch that does that for the bionic version. It also applys
directly on Focal.
I attach the patch t
** Patch added: "apt.systemd.daily.diff"
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1824088/+attachment/5344224/+files/apt.systemd.daily.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://b
The interesting about the code is that it always only treat the
timestamp of the file as "-MM-DD" and nothing else (this also
includes "now").
The code has functions for allowing the interval to be set down to 1s
but is does not mean anything to the outcome of the script as it always
looks for
The thing is that it's only the delta that is handled in UTC not the
iso-8601-part so it will work just fine.
My first idé was to fix the interval calculations must like yours.
The workaround for us was to set interval to always. We have local
mirrors that can handle the load just fine even if we
6 matches
Mail list logo
