apt/debian, branch 1.4.4Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.4.42017-05-16T21:20:29ZRelease 1.4.42017-05-16T21:20:29ZJulian Andres Klodejak@debian.org2017-05-16T21:20:29Zurn:sha1:5dc951d7cfd064ca63e045d32749e79846881d56apt.systemd.daily: Drop the LOCKFD variable2017-05-16T21:18:07ZJulian Andres Klodejak@debian.org2017-05-16T21:18:07Zurn:sha1:3819004c2cb3893bfa136f3c44a5783c42cd2a8d
Gbp-Dch: ignore
apt.systemd.daily: fix error from locking code2017-05-16T21:16:43ZAlan Jenkinsalan.christopher.jenkins@gmail.com2017-05-14T17:11:59Zurn:sha1:7b4581cbe8fcf6e2bd56a27c5a7a1e6ea33d2973
Error:
pkgs that look like they should be upgraded:
Error in function stop
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apt/progress/text.py", line 240,
in stop
apt_pkg.size_to_str(self.current_cps))).rstrip("\n"))
File "/usr/lib/python3/dist-packages/apt/progress/text.py", line 51,
in _write
self._file.write("\r")
AttributeError: 'NoneType' object has no attribute 'write'
fetch.run() result: 0
Caused by:
LOCKFD=3
unattended_upgrades $LOCKFD>&-
Unfortunately this code does not work, it is equivalent to
unattended_upgrades 3 >&-
I.e. it left fd 3 open, but closed stdout!
Closes: #862567
Release 1.4.32017-05-11T12:46:58ZJulian Andres Klodejak@debian.org2017-05-11T12:46:58Zurn:sha1:59929e14271f82baa4c7cba4a071df21fe5b9d27Do not try to (re)start timers outside 'apt' package2017-05-07T10:23:23ZJulian Andres Klodejak@debian.org2017-05-07T10:17:05Zurn:sha1:315d6aac02b657a4742b5fe2695707904c6033dd
dh_systemd_start inserted postinst commands in all packages,
rather than just the package containing the timers.
This also gets rid of postinst scripts for all other
packages, yay.
Closes: #862001
Release 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