<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/test, 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-14T19:23:41Z</updated>
<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>Deal with descriptions embedded in displayed record correctly</title>
<updated>2018-09-20T16:36:03Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2018-09-20T15:22:54Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=6f1d622c84b3b7f821683bf69b8fcdb6dcf272a2'/>
<id>urn:sha1:6f1d622c84b3b7f821683bf69b8fcdb6dcf272a2</id>
<content type='text'>
The implementation of "apt-cache show" (not "apt show") incorrectly
resets the currently used parser if the record itself and the
description to show come from the same file (as it is the case if no
Translation-* files are available e.g. after debootstrap).

The code is more complex than you would hope to support some rather
unusual setups involving Descriptions and their translations as tested
for by ./test-bug-712435-missing-descriptions as otherwise this could
be a one-line change.

Regression-Of: bf53f39c9a0221b670ffff74053ed36fc502d5a0
Closes: #909155
</content>
</entry>
<entry>
<title>Merge branch 'bugfix/statusfd' into 'master'</title>
<updated>2018-09-18T12:05:20Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2018-09-18T12:05:20Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=252a0a5020726a7b1ee53f2ed5f00e1210f5f4d1'/>
<id>urn:sha1:252a0a5020726a7b1ee53f2ed5f00e1210f5f4d1</id>
<content type='text'>
Process all of --status-fd and don't expect duplicate status msg

See merge request apt-team/apt!26</content>
</entry>
<entry>
<title>Show all architectures in 'apt list' output</title>
<updated>2018-09-15T15:45:16Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2018-09-15T15:45:16Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=32e0587d1819ca4b09cd146b0114a1c56ce4a8a9'/>
<id>urn:sha1:32e0587d1819ca4b09cd146b0114a1c56ce4a8a9</id>
<content type='text'>
The uniqueness in std::set containers is ensured by the ordering
operator we provide, but it was not considering that different versions
can have the same description like the different architectures for a
version of a package.

Closes: #908218
</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>
