<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/apt-pkg, branch 1.8.0_alpha1</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.8.0_alpha1</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.8.0_alpha1'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2018-10-30T21:43:35Z</updated>
<entry>
<title>Fix typos encountered while updating de translation</title>
<updated>2018-10-30T21:43:35Z</updated>
<author>
<name>Chris Leick</name>
<email>c.leick@vollbio.de</email>
</author>
<published>2018-10-30T21:32:34Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=b6b159cc5eedca24d2ca0e27e230865ad2b4ad0f'/>
<id>urn:sha1:b6b159cc5eedca24d2ca0e27e230865ad2b4ad0f</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge branch 'feature/subkeys' into 'master'</title>
<updated>2018-10-14T19:23:41Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2018-10-14T19:23:41Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=b80e48783c183aeaf1d30d898a7743f091d96336'/>
<id>urn:sha1:b80e48783c183aeaf1d30d898a7743f091d96336</id>
<content type='text'>
Support subkeys and multiple keyrings in Signed-By options

See merge request apt-team/apt!27</content>
</entry>
<entry>
<title>Default to https: scheme for fetching Debian changelogs</title>
<updated>2018-10-13T17:22:16Z</updated>
<author>
<name>Ben Hutchings</name>
<email>ben@decadent.org.uk</email>
</author>
<published>2018-10-13T16:15:34Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=4814a58f9f0c81fac9441b31cea954f028121dff'/>
<id>urn:sha1:4814a58f9f0c81fac9441b31cea954f028121dff</id>
<content type='text'>
Closes: #910941
</content>
</entry>
<entry>
<title>Set DPKG_FRONTEND_LOCKED when running {pre,post}-invoke scripts</title>
<updated>2018-10-05T10:45:47Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2018-10-05T10:29:39Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=6675601c81de85b40dc89772c1d6d17f1811c5ba'/>
<id>urn:sha1:6675601c81de85b40dc89772c1d6d17f1811c5ba</id>
<content type='text'>
Some post-invoke scripts install packages, which fails because
the environment variable is not set. This sets the variable for
all three kinds of scripts {pre,post-}invoke and pre-install-pkgs,
but we will only allow post-invoke at a later time.

Gbp-Dch: full
</content>
</entry>
<entry>
<title>pkgCacheFile: Only unlock in destructor if locked before</title>
<updated>2018-09-24T10:13:03Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2018-09-24T09:38:55Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=e02297b8e22dae04872fe6fab6dba966de65dbba'/>
<id>urn:sha1:e02297b8e22dae04872fe6fab6dba966de65dbba</id>
<content type='text'>
pkgCacheFile's destructor unlocks the system, which is confusing
if you did not open the cachefile with WithLock set. Create a private
data instance that holds the value of WithLock.

This regression was introduced in commit b2e465d6d32d2dc884f58b94acb7e35f671a87fe:

    Join with aliencode
    Author: jgg
    Date: 2001-02-20 07:03:16 GMT
    Join with aliencode

by replacing a "Lock" member that was only initialized when the lock
was taken by calls to Lock, UnLock; with the latter also taking place
if the former did not occur.

Regression-Of: b2e465d6d32d2dc884f58b94acb7e35f671a87fe
LP: #1794053
</content>
</entry>
<entry>
<title>Fix calculation of elapsed usec in downloads</title>
<updated>2018-09-24T07:27:01Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2018-09-24T07:27:01Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=089e627153781ae7c320a5a0724c6c70d684b689'/>
<id>urn:sha1:089e627153781ae7c320a5a0724c6c70d684b689</id>
<content type='text'>
A recent change to use chronos inadvertently replaced the
difference of new usec - old usec with new sec - old usec,
which is obviously wrong.
</content>
</entry>
<entry>
<title>Support multiple keyrings in sources.list Signed-By</title>
<updated>2018-09-11T11:16:11Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2018-08-17T14:33:41Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=8375d5b58038fc026098dcccc3de87cd9d740334'/>
<id>urn:sha1:8375d5b58038fc026098dcccc3de87cd9d740334</id>
<content type='text'>
A user can specify multiple fingerprints for a while now, so its seems
counter-intuitive to support only one keyring, especially if this isn't
really checked or enforced and while unlikely mixtures of both should
work properly, too, instead of a kinda random behaviour.
</content>
</entry>
<entry>
<title>Support subkeys properly in Signed-By options</title>
<updated>2018-09-11T11:16:11Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2018-08-17T09:59:45Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=ff8fa4ab4b80384a9240f0df63181f71077a8d83'/>
<id>urn:sha1:ff8fa4ab4b80384a9240f0df63181f71077a8d83</id>
<content type='text'>
If we limit a file to be signed by a certain key it should usually
accept also being signed by any of this keys subkeys instead of
requiring each subkey to be listed explicitly. If the later is really
wanted we support now also the same syntax as gpg does with appending an
exclamation mark at the end of the fingerprint to force no mapping.
</content>
</entry>
<entry>
<title>Reorder progress report messages</title>
<updated>2018-09-11T11:08:58Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2018-09-10T19:34:11Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=329c8d5e149465003ea9007661a7af1099c75c43'/>
<id>urn:sha1:329c8d5e149465003ea9007661a7af1099c75c43</id>
<content type='text'>
We are seeing 'processing' messages from dpkg first, so it makes sense
to translate them to "Preparing" messages instead of using "Installing"
and co to override these shortly after with the "Preparing" messages.

The difference isn't all to visible as later messages tend to linger far
longer in the display than the ealier ones, but at least in a listing it
seems more logical.
</content>
</entry>
<entry>
<title>Don't expect duplicated dpkg status-fd messages</title>
<updated>2018-09-11T11:08:58Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2018-09-10T16:43:34Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=f484906eff85c8c9eadc13ce817d8857abdd08e8'/>
<id>urn:sha1:f484906eff85c8c9eadc13ce817d8857abdd08e8</id>
<content type='text'>
The progress reporting relies on parsing the status reports of
dpkg which used to repeat being in the same state multiple times
in the same run, but by fixing #365921 it will stop doing so.

The problem is in theory just with 'config-files' in case we do purge as
this (can) do remove + purge in one step, but we remove this also for
the unpack + configure combination althrough we handle these currently
in two independent dpkg calls.
</content>
</entry>
</feed>
