| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Only protect two kernels, not last installed one | Julian Andres Klode | 2022-04-07 | 1 | -0/+1 |
| | | | | | | | | | | | | | The kernel autoremoval algorithm was written to accomodate for Ubuntu's boot partition sizing, which was written to accomodate 3 kernels - 2 installed ones + a new one being unpacked. It seems that when the algorithm was designed, it was overlooked that it actually kept 3 kernels. LP: #1968154 | ||||
| * | debian: Run wrap-and-sort | Julian Andres Klode | 2016-08-19 | 1 | -1/+0 |
| | | | | | | Manually clean up the apt.maintscript, it moved stuff from before the comment to after the comment... | ||||
| * | Use systemd.timer instead of a cron job | Michael Vogt | 2016-04-01 | 1 | -1/+2 |
| | | | | | | | | | | | | | | | | | | | | | | | The rational is that we need to spread the load on the mirrors that apt update and unattended-upgrades cause. To do so, we leverage the RandomizeDelay feature of systemd. The other advantage is that the timer is not run at a fixed daily.daily time but instead every 24h. This also fixes the problem that the randomized deplay in the current apt.cron.daily causes other cron jobs to be deplayed. A compatibility cron job is also provided for systems that do not use systemd. Note that the time is fired two times a day, but the logic inside of apt.systemd.daily will ensure (via stamp files) that the servers are hit at most every 24h. Firing two times a day helps with the worst case update time and it also helps with systems that are not always on. LP: #246381, #727685 Closes: #600262, #709675, #663290 | ||||
| * | Fix maintscript to properly remove 20changelog | Julian Andres Klode | 2016-02-15 | 1 | -1/+1 |
| | | | | | Closes: #814754 | ||||
| * | provide support for debian/apt.conf.$(lsb_release -i -s) vendor specific ↵ | Michael Vogt | 2014-04-25 | 1 | -0/+3 |
| config files | |||||
