apt, branch 1.7.0_alpha2Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.7.0_alpha22018-07-09T14:03:19ZRelease 1.7.0~alpha22018-07-09T14:03:19ZJulian Andres Klodejulian.klode@canonical.com2018-07-09T14:02:49Zurn:sha1:91671efc7f63b3e2ff2a573d86ac3225e9b5f9cdUse cheaper entropy source for randomizing items to fetch2018-07-06T08:40:28ZJulian Andres Klodejulian.klode@canonical.com2018-07-05T15:45:40Zurn:sha1:420009e46ce7c0d97a2dc5e216ffce48dd7c0846
The random_device fails if not enough entropy is available. We do
not need high-quality entropy here, though, so let's switch to a
seed based on the current time in nanoseconds, XORed with the PID.
Merge branch 'pu/lp1776218-allow-hooks-to-not-handshake' into 'master'2018-06-28T08:12:50ZJulian Andres Klodejak@debian.org2018-06-28T08:12:50Zurn:sha1:a7b4dd425c10730b886f3ea0b2e045ee5015cfe5
Handle JSON hooks that just close the file/exit and fix some other errors
See merge request apt-team/apt!21Handle JSON hooks that just close the file/exit and fix some other errors2018-06-27T13:09:45ZJulian Andres Klodejulian.klode@canonical.com2018-06-27T09:31:21Zurn:sha1:1d53cffad22c92645090e0e6ddde31fe4f7c3b05
JSON hooks might disappear and the common idiom to work around hooks
disappearing is to check for the hook in the shell snippet that is
in the apt.conf file and if it does not exist, do nothing. This caused
APT to fail however, expecting it to acknowledge the handshake.
Ignoring ECONNRESET on handshakes solves the problem.
The error case, and the other error cases also did not stop execution
of the hook, causing more errors to pile up. Fix this by directly going
to the closing part of the code.
LP: #1776218
Release 1.7.0~alpha12018-06-25T15:12:47ZJulian Andres Klodejulian.klode@canonical.com2018-06-25T15:12:47Zurn:sha1:8c3cb66e65cddf1ac297daba5bb442b415577137gitlab-ci: chmod 755 /root2018-06-25T13:38:57ZJulian Andres Klodejulian.klode@canonical.com2018-06-25T13:38:57Zurn:sha1:3a37521aec0b02e12deaef58772ae0bca9a75496
This should avoid test failures on ubuntu:bionic
Ensure that we are online in apt-daily-upgrade.service2018-06-25T11:19:49ZJulian Andres Klodejulian.klode@canonical.com2018-06-25T11:19:49Zurn: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 environments2018-06-25T10:30:58ZJulian Andres Klodejulian.klode@canonical.com2018-06-25T10:30:12Zurn:sha1:551ded4b63f6f47f022c5ca841031fc2566a58ff
This ensures that we don't hang waiting for debconf.
Fix lock counting in debSystem2018-06-13T21:36:08ZJulian Andres Klodejulian.klode@canonical.com2018-06-13T16:45:12Zurn: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 update2018-06-02T09:01:08ZFrans SpiesschaertFrans.Spiesschaert@yucom.be2018-06-02T07:50:29Zurn:sha1:15df82d2c8a29ac179ddcd57eb849d3ad0f2561f
Closes: #900602