apt/debian, branch 1.4.2Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.4.22017-05-04T20:57:12ZRelease 1.4.22017-05-04T20:57:12ZJulian Andres Klodejak@debian.org2017-05-04T20:57:12Zurn:sha1:1179ac70e9ad100d507c276e6d8de1f9aba08104Split apt-daily timer into two2017-05-04T20:49:48ZJulian Andres Klodejak@debian.org2017-04-26T18:03:56Zurn:sha1:496313fb8e83af2ba71f6ce3d729be687c293dfd
The timer doing downloading runs throughout the day, whereas
automatic upgrade and clean actions only happen in the morning.
The upgrade service and timer have After= ordering requirements
on their non-upgrade counterparts to ensure that upgrading at
boot takes place after downloading.
LP: #1686470
apt.systemd.daily: Add locking2017-05-04T20:49:48ZJulian Andres Klodejak@debian.org2017-04-28T09:11:53Zurn:sha1:ea49b66372912354143b810e2826301d651a2b37
Use a lock file to make sure only one instance of the
script is running at the same time.
Run unattended-upgrade -d in download part2017-05-03T17:08:50ZJulian Andres Klodejak@debian.org2017-04-26T19:39:16Zurn:sha1:01e324a6893164feace153bc17fe6453b6fa97db
We want to download the upgrades first, if unattended-upgrades
is configured. We don't want to use the normal dist-upgrade -d
thing for it, though, as unattended-upgrades only upgrades a
subset.
Allow the daily script to be run in two phases2017-04-26T18:45:38ZJulian Andres Klodejak@debian.org2017-04-26T17:58:56Zurn:sha1:007b22ee6fd33d9b03637577f8401a43c5e7c90c
This adds an argument to the script which may be update, install,
or empty. In the update cases, downloads are performed. In the
install case, installs are performed. If empty, both are run.
Gbp-Dch: ignore
Release 1.4.12017-04-24T16:48:35ZJulian Andres Klodejak@debian.org2017-04-24T16:48:35Zurn:sha1:7f18715769a93da7a99438f6de4e2533ac8c7ed8debian/rules: Actually invoke dh_clean in override_dh_clean2017-04-24T16:44:34ZJulian Andres Klodejak@debian.org2017-04-23T20:26:21Zurn:sha1:5a97eaeb839470a7d08a8e21a5529e6b4a2a7e25
Regression from commit f5e9be1da89725f9bf1915bdf86fdc4a77edf917
systemd: Rework timing and add After=network-online2017-04-24T16:44:34ZJulian Andres Klodejak@debian.org2017-04-21T19:18:59Zurn:sha1:b4f32b13055287d2ac46a08255db475af195b5f7
The timeout values were so large that the timer could run at any
random time of the day, possibly easily interfering with business
hours, and causing trouble. Reduce them to 30 minutes of random
delay and an accuracy to the default value (1 minute).
Also drop the 18:00 event. People still actively use their device
during that time, and for servers, there might be less attendance
than in the regular 06:00 time slot, so longer time to fix things
if something breaks.
During a boot, the service might be run to catch up with a timer
that would have normally elapsed. Due to no dependencies, it would
have run before the network is online - that's bad. Adding an After
and a Wants fixes that for boots, but still leaves the same issue
for Resume.
LP: #1615482
Release the April Fools' release2017-04-01T19:43:23ZJulian Andres Klodejak@debian.org2017-04-01T19:43:23Zurn:sha1:47e53fe58e28dc1a2fa0098c6705f380f37f5902auto-removal: Ignore running kernel if attempting a reproducible build2017-03-13T15:31:38ZChris Lamblamby@debian.org2017-03-13T10:02:49Zurn:sha1:a9b56a0101628ac04aad0d4e50363b9c18566832
If one is attempting to create a reproducible ISO image we do not want to
include the build system's kernel version, not only due to it breaking
reproducibility, but it could be somewhat misleading and/or the
wrong thing to put in this file anyway.
Closes: #857632