<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/cmdline, branch 1.3_rc2</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.3_rc2</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.3_rc2'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2016-08-17T12:12:24Z</updated>
<entry>
<title>allow spaces in fingerprints for 'apt-key del'</title>
<updated>2016-08-17T12:12:24Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-08-17T06:10:29Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=e289907f5e7241034cb0d37055dc2cba4e3a19af'/>
<id>urn:sha1:e289907f5e7241034cb0d37055dc2cba4e3a19af</id>
<content type='text'>
Fingerprints tend to be displayed in space-separated octet pairs so be
nice and allow delete to remove a key based on such a string rather than
requiring that the user is deleting all the spaces manually.
</content>
</entry>
<entry>
<title>add the gpg-classic variant to the gpgv/gnupg or-group</title>
<updated>2016-08-17T07:52:32Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-08-16T13:46:19Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=19fdf93d7363261227811a62157063081b9f1a5d'/>
<id>urn:sha1:19fdf93d7363261227811a62157063081b9f1a5d</id>
<content type='text'>
We need to support partial upgrades anyhow, so we have to deal with the
different versions and your tests try to ensure that we do, so we
shouldn't make any explicit higher requirements.
</content>
</entry>
<entry>
<title>Get rid of the old buildsystem</title>
<updated>2016-08-10T14:17:19Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-08-09T15:40:01Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=c85c4bed0a4b32ee2dcbd86ea819e39f3d8beb84'/>
<id>urn:sha1:c85c4bed0a4b32ee2dcbd86ea819e39f3d8beb84</id>
<content type='text'>
Bye, bye, old friend.
</content>
</entry>
<entry>
<title>CMake: Add basic CMake build system</title>
<updated>2016-08-06T20:36:02Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-08-06T19:03:43Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=f3de2dbaf657f9040a4da448c57267de0fef7d33'/>
<id>urn:sha1:f3de2dbaf657f9040a4da448c57267de0fef7d33</id>
<content type='text'>
Introduce an initial CMake buildsystem. This build system can build
a fully working apt system without translation or documentation.

The FindBerkelyDB module is from kdelibs, with some small adjustements
to also look in db5 directories.

Initial work on this CMake build system started in 2009, and was
resumed in August 2016.
</content>
</entry>
<entry>
<title>apt-key: ignore any error produced by gpgconf --kill</title>
<updated>2016-07-31T08:29:25Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-07-31T08:29:25Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=215598df84c092f801fe154e510c68fcc263b3ba'/>
<id>urn:sha1:215598df84c092f801fe154e510c68fcc263b3ba</id>
<content type='text'>
gpgconf wasn't always equipped with a --kill option as highlighted by
our testcases failing on Travis and co as these use a much older version
of gpg2. As this is just for cleaning up slightly faster we ignore any
error a call might produce and carry on. Use a recent enough gpg2
version if you need the immediate killing…

Gbp-Dch: Ignore
Reported-By: Travis CI
</content>
</entry>
<entry>
<title>apt-key: kill gpg-agent explicitly in cleanup</title>
<updated>2016-07-31T07:56:26Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-07-31T07:27:19Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=4039798d971752325d097bfbdc9011b5e9efd29c'/>
<id>urn:sha1:4039798d971752325d097bfbdc9011b5e9efd29c</id>
<content type='text'>
apt-key has (usually) no secret key material so it doesn't really need
the agent at all, but newer gpgs insist on starting it anyhow. The
agents die off rather quickly after the underlying home-directory is
cleaned up, but that is still not fast enough for tools like sbuild
which want to unmount but can't as the agent is still hanging onto a
non-existent homedir.

Reported-By: Johannes 'josch' Schauer on IRC
</content>
</entry>
<entry>
<title>use the right key for compressor configuration dump</title>
<updated>2016-07-05T18:44:45Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-07-05T12:08:57Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=52bafeade99b700eeb4585608c5eee086b94dfa8'/>
<id>urn:sha1:52bafeade99b700eeb4585608c5eee086b94dfa8</id>
<content type='text'>
The generated dump output is incorrect in sofar as it uses the name as
the key for this compressor, but they don't need to be equal as is the
case if you force some of the inbuilt ones to be disabled as our testing
framework does it at times.

This is hidden from changelog as nobody will actually notice while
describing it in a few words make it sound like an important change…

Git-Dch: Ignore
</content>
</entry>
<entry>
<title>indextargets: Check that cache could be built before using it</title>
<updated>2016-07-05T06:22:52Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-07-05T06:21:28Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=8823972649b0d3049c9c0d34b5f1d31160234fb4'/>
<id>urn:sha1:8823972649b0d3049c9c0d34b5f1d31160234fb4</id>
<content type='text'>
This caused a crash because the cache was a nullptr.

Closes: #829651
</content>
</entry>
<entry>
<title>use +0000 instead of UTC by default as timezone in output</title>
<updated>2016-07-02T10:01:17Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-07-02T09:28:42Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=0b45b6e5de1ba4224ced67a9952e009d0f4139a0'/>
<id>urn:sha1:0b45b6e5de1ba4224ced67a9952e009d0f4139a0</id>
<content type='text'>
All apt versions support numeric as well as 3-character timezones just
fine and its actually hard to write code which doesn't "accidently"
accepts it. So why change? Documenting the Date/Valid-Until fields in
the Release file is easy to do in terms of referencing the
datetime format used e.g. in the Debian changelogs (policy §4.4). This
format specifies only the numeric timezones through, not the nowadays
obsolete 3-character ones, so in the interest of least surprise we should
use the same format even through it carries a small risk of regression
in other clients (which encounter repositories created with
apt-ftparchive).

In case it is really regressing in practice, the hidden option
  -o APT::FTPArchive::Release::NumericTimezone=0
can be used to go back to good old UTC as timezone.

The EDSP and EIPP protocols use this 'new' format, the text interface
used to communicate with the acquire methods does not for compatibility
reasons even if none of our methods would be effected and I doubt any
other would (in these instances the timezone is 'GMT' as that is what
HTTP/1.1 requires). Note that this is only true for apt talking to
methods, (libapt-based) methods talking to apt will respond with the
'new' format.  It is therefore strongly adviced to support both also in
method input.
</content>
</entry>
<entry>
<title>deprecate 'apt-key update' and no-op it in Debian</title>
<updated>2016-07-01T22:03:20Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-07-01T21:44:37Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=f4dcab0504a68595d9e95c953ce66f46f9ad30aa'/>
<id>urn:sha1:f4dcab0504a68595d9e95c953ce66f46f9ad30aa</id>
<content type='text'>
Debian isn't using 'update' anymore for years and the command is in
direct conflict with our goal of not requiring gnupg anymore, so it
is high time to officially declare this command as deprecated.
</content>
</entry>
</feed>
