apt, branch 1.7.0_alpha1 Debians commandline package manager https://git.kalnischkies.de/apt/atom?h=1.7.0_alpha1 2018-06-25T15:12:47Z Release 1.7.0~alpha1 2018-06-25T15:12:47Z Julian Andres Klode julian.klode@canonical.com 2018-06-25T15:12:47Z urn:sha1:8c3cb66e65cddf1ac297daba5bb442b415577137 gitlab-ci: chmod 755 /root 2018-06-25T13:38:57Z Julian Andres Klode julian.klode@canonical.com 2018-06-25T13:38:57Z urn:sha1:3a37521aec0b02e12deaef58772ae0bca9a75496 This should avoid test failures on ubuntu:bionic Ensure that we are online in apt-daily-upgrade.service 2018-06-25T11:19:49Z Julian Andres Klode julian.klode@canonical.com 2018-06-25T11:19:49Z urn:sha1:005c5150d16e80c2322e0380dec9906be9cb7c08 Installer packages need us to be online, or they are blocking shutdowns in the worst case :( LP: #1723761 CI: Export DEBIAN_FRONTEND=noninteractive in all CI environments 2018-06-25T10:30:58Z Julian Andres Klode julian.klode@canonical.com 2018-06-25T10:30:12Z urn:sha1:551ded4b63f6f47f022c5ca841031fc2566a58ff This ensures that we don't hang waiting for debconf. Fix lock counting in debSystem 2018-06-13T21:36:08Z Julian Andres Klode julian.klode@canonical.com 2018-06-13T16:45:12Z urn:sha1:79f012bd09ae99d4c9d63dc0ac960376b5338b32 debSystem uses a reference counted lock, so you can acquire it multiple times in your applications, possibly nested. Nesting locks causes a fd leak, though, as we only increment the lock count when we already have locked twice, rather than once, and hence when we call lock the second time, instead of increasing the lock count, we open another lock fd. This fixes the code to check if we have locked at all (> 0). There is no practical problem here aside from the fd leak, as closing the new fd releases the lock on the old one due to the weird semantics of fcntl locks. Dutch manpage translation update 2018-06-02T09:01:08Z Frans Spiesschaert Frans.Spiesschaert@yucom.be 2018-06-02T07:50:29Z urn:sha1:15df82d2c8a29ac179ddcd57eb849d3ad0f2561f Closes: #900602 Dutch program translation update 2018-06-02T09:01:08Z Frans Spiesschaert Frans.Spiesschaert@yucom.be 2018-06-02T07:42:35Z urn:sha1:a3352eb10e4eea63c23aeb1378cac92c30f9484e Closes: #900589 Merge branch 'fix/usesteadyclockforprogress' into 'master' 2018-05-30T11:45:16Z Julian Andres Klode jak@debian.org 2018-05-30T11:45:16Z urn:sha1:c105a808366867e5476bd4d1ea7fe1c1e9795948 Fix/usesteadyclockforprogress See merge request apt-team/apt!19 apt-key: Pass all instead of gpg-agent to gpgconf --kill 2018-05-29T15:57:35Z Julian Andres Klode julian.klode@canonical.com 2018-05-29T15:57:35Z urn:sha1:819426013c6ca6310bb469440702b6295dba4498 We want to kill everything using our temporary directory. LP: #1773992 Use steady clock source for bandwidth limitation 2018-05-29T11:04:59Z David Kalnischkies david@kalnischkies.de 2018-05-26T19:26:03Z urn:sha1:f6655a1138a11e80884959014939a25f23a1e308 Using the time of day for this is slightly wrong just like it is for progress, just less visible.