Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.8.0_alpha2 2018-01-02T12:54:19Z 2018-01-02T12:54:19Z Christian Göttsche cgzones@googlemail.com 2018-01-02T12:54:19Z urn:sha1:b20fd95ef94e302208018a148e98693b0f69c0e6 Various corrections, mostly quoting, which shouldn't be a problem for us as we tend to act in "sane" environments, but just to be sure. [commit message written by committer] References: Debian bugreport #849636 2018-01-02T12:43:21Z David Kalnischkies david@kalnischkies.de 2018-01-02T12:43:21Z urn:sha1:06a03c972b04159a6ae57cd9e4959eaa1d164d7b The signal was introduced with the introduction of the script itself, but seems to have never got any user as all references to it I can find are references to other code appearing in the cronjob. It is also the wrong place nowadays as the cronjob is just one place an update can be triggered by, so if notifications about an update being run are desired it is better to use a hook which will be called by all update calls (script, cron, user, …). Removing this code solves also the problem of improving the check to avoid running into problems with security systems like SELinux. References: 0c1326826fd23ce859db8e923c37b7199c6da2c8 Closes: 849636 2017-07-12T21:59:35Z Paul Wise pabs@debian.org 2017-07-12T21:30:25Z urn:sha1:0f3f9e620e9b977ff72bbcbcc205a1e60ed5b836 Gbp-Dch: ignore 2017-07-12T13:27:02Z Paul Wise pabs@debian.org 2017-04-07T00:19:59Z urn:sha1:1d9e29c9e2a5591b42a99a721b901fc003ed9149 2017-07-12T13:26:45Z Paul Wise pabs@debian.org 2017-04-07T00:18:17Z urn:sha1:ca90c388045b4498fe32e706bd1bdcf7a6ac8e17 [squashed:] apt.systemd.daily: check_stamp: check for 'always' before numerical values Prevents a crash when the configuration actually uses 'always': apt.systemd.daily: 402: [: Illegal number: always 2017-06-01T07:16:37Z Julian Andres Klode jak@debian.org 2017-06-01T07:16:37Z urn:sha1:cedf80c55766868eadc7ed59a27537c9a5d91edf Using dry-run as in the previous commit is not really correct, as it logs dpkg debugging output too. So, let's assume unattended-upgrade gets a --download-only option and use that if it is available. This lets us add the downloading part to unattended-upgrades later on, without requiring versioned dependencies between the two. Closes: #863859 2017-06-01T06:24:12Z Julian Andres Klode jak@debian.org 2017-06-01T06:24:12Z urn:sha1:31c81a37ac6dceda0c94ce088b338b6b09afd5a4 We want to download stuff: --dry-run Simulation, download but do not install not debug: -d, --debug print debug messages Confusion everywhere! Closes: #863859 2017-05-16T21:18:07Z Julian Andres Klode jak@debian.org 2017-05-16T21:18:07Z urn:sha1:3819004c2cb3893bfa136f3c44a5783c42cd2a8d Gbp-Dch: ignore 2017-05-16T21:16:43Z Alan Jenkins alan.christopher.jenkins@gmail.com 2017-05-14T17:11:59Z urn: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 2017-05-04T20:49:48Z Julian Andres Klode jak@debian.org 2017-04-28T09:11:53Z urn:sha1:ea49b66372912354143b810e2826301d651a2b37 Use a lock file to make sure only one instance of the script is running at the same time.