Debian Bug report logs - #862055
apt: Rework daily timers for buster, drop internal timestamps

Package: apt; Maintainer for apt is APT Development Team <[email protected]>; Source for apt is src:apt (PTS, buildd, popcon).

Reported by: Julian Andres Klode <[email protected]>

Date: Sun, 7 May 2017 20:51:01 UTC

Severity: normal

Tags: confirmed

Reply or subscribe to this bug.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to [email protected], [email protected], APT Development Team <[email protected]>:
Bug#862055; Package apt. (Sun, 07 May 2017 20:51:04 GMT) (full text, mbox, link).


Acknowledgement sent to Julian Andres Klode <[email protected]>:
New Bug report received and forwarded. Copy sent to [email protected], APT Development Team <[email protected]>. (Sun, 07 May 2017 20:51:04 GMT) (full text, mbox, link).


Message #5 received at [email protected] (full text, mbox, reply):

From: Julian Andres Klode <[email protected]>
To: Debian Bug Tracking System <[email protected]>
Subject: apt: Rework daily timers for buster, drop internal timestamps
Date: Sun, 7 May 2017 22:46:10 +0200
Package: apt
Severity: normal
Control: tag -1 confirmed

APT's daily cron job and systemd timers currently keep internal
timestamps. systemd keeps its own internal timestamp, leading
to two timestamps: When the systemd timestamp is old enough,
the apt timestamp might not be causing confusion because the
service started and did nothing.

We currently have 6 timestamps:

* update
* download upgradable
* unattended-upgrade
* backup archive/
* autoclean
* clean

I propose to refactor this into three groups:

* download (update, download-upgradable, download u-u upgrades)
* upgrade (run unattended-upgrade)
* maintenance (backup/autoclean/clean)

And the existing options for intervals become booleans for systemd
users, where the intervals are configured by overriding the systemd
timer units apt-daily-download, apt-daily-upgrade, apt-daily-maintenance
instead.

This means systemd systems will have 3 timers with 3 time stamps,
clearly defined behavior when starting the service (always performing
the action), and things will just work in a reasonable way.

This will also allow us to implement retrying on failure efficiently
and generally have a better working solution than now.

-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev
                  |  Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline').  Thank you.



Added tag(s) confirmed. Request was from Julian Andres Klode <[email protected]> to [email protected]. (Sun, 07 May 2017 20:51:04 GMT) (full text, mbox, link).


Send a report that this bug log contains spam.


Debian bug tracking system administrator <[email protected]>. Last modified: Mon Nov 11 13:29:14 2024; Machine Name: buxtehude

Debian Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.