Awesome work Magnus. Well done!
Since the bug is related to APT, is Debian then considered the upstream
of this source?
Would it be appropriate to also file a bug in their bug tracker? If so,
I can arrange that.
--
You received this bug notification because you are a member of Ubuntu
Touch
How about this idea?
What if we add this line to the beginning of
usr/lib/apt/apt.systemd.daily:
export TZ="UTC0"
(I got this idea from the GNU Coreutils manual. See
https://www.gnu.org/software/coreutils/manual/html_node/Relative-items-
in-date-strings.html)
--
You received this bug
If we look at lines 131 and 132 in /usr/lib/apt/apt.systemd.daily, we
will se the following:
interval="${interval%d}"
interval=$((interval*60*60*24))
I’m not 100% certain but I think that this time logic is what cause the
bug to occur, in accordance with what Magnus has pointed out in his
** Attachment added: "Log data from apt"
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1824088/+attachment/5254618/+files/history.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
Public bug reported:
I have noticed a strange behaviour in unattended upgrades. The host in
question is scheduled to run upgrades on Mondays every second week.
However, this week it ran upgrades on Tuesday instead (2019-04-09).
This is the first time I’ve noticed this behaviour. I checked the
5 matches
Mail list logo
