<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt, branch 1.3_exp1</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.3_exp1</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.3_exp1'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2016-05-11T08:51:06Z</updated>
<entry>
<title>Release 1.3~exp1</title>
<updated>2016-05-11T08:51:06Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-05-11T08:51:06Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=5b0577488ff60e7163fe7dc62a044329d398d726'/>
<id>urn:sha1:5b0577488ff60e7163fe7dc62a044329d398d726</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Dutch program translation update</title>
<updated>2016-05-10T21:24:01Z</updated>
<author>
<name>Frans Spiesschaert</name>
<email>Frans.Spiesschaert@yucom.be</email>
</author>
<published>2016-05-10T21:21:46Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=6fb0b9ed8c6e3b5af5aac14e8f57c4d0ec2cc638'/>
<id>urn:sha1:6fb0b9ed8c6e3b5af5aac14e8f57c4d0ec2cc638</id>
<content type='text'>
Closes: 823976
</content>
</entry>
<entry>
<title>edsp: support generic and solver-specific configs</title>
<updated>2016-05-10T20:48:31Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-05-10T20:48:31Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=eb1000f6e5fa7035c764d0e7aa9ca71c7aa8d52d'/>
<id>urn:sha1:eb1000f6e5fa7035c764d0e7aa9ca71c7aa8d52d</id>
<content type='text'>
The spec was slightly inconsistent if the preferences setting is
available only as generic or specific setting &amp; the code only supported
the specific one, while for the strict-pinning was only generic…

As the usual pattern for apt is to have both options we adapt the spec
and code to support both as well.

This also adds a purely informal "Solver" field so in case the request
is saved in a file, we know to which solver the sent preferences apply.

Closes: 823918
</content>
</entry>
<entry>
<title>update: Run Post-Invoke-Success if not all sources failed</title>
<updated>2016-05-10T18:14:02Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-05-10T17:15:17Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=35664152e47a1d4d712fd52e0f0a2dc8ed359d32'/>
<id>urn:sha1:35664152e47a1d4d712fd52e0f0a2dc8ed359d32</id>
<content type='text'>
Failures can happen and APT regardless will do a partial cache
update anyway. Because APT ensures that the list directory is
in a sane state, it makes sense to also call success hooks if
success was only partial - otherwise it loses sync with APT.

Most importantly, this causes the appstream cache to be empty,
see launchpad bug #1562733.

This is somewhat overly optimistic though: As soon as any repository
has nonexisting optional files, the missing optional files are also
treated as success, which means a single broken repository without an
InRelease file still runs Success hooks, even though it really should
not.
</content>
</entry>
<entry>
<title>Strip trailing commas for created signed-by fingerprint lists</title>
<updated>2016-05-10T17:09:19Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-05-10T17:09:19Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=c7b7d4da7f8b8edd9c3d6b13f0b935853ad8a039'/>
<id>urn:sha1:c7b7d4da7f8b8edd9c3d6b13f0b935853ad8a039</id>
<content type='text'>
This prevented some sources.list entries from working, an example
of which can be found in the test.
</content>
</entry>
<entry>
<title>Merge pull request julian-klode/apt#3 from adrian17/master</title>
<updated>2016-05-10T16:32:06Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-05-10T16:32:06Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=a9c2517e9ce961a761022dfa8eb0b62f68f5df9e'/>
<id>urn:sha1:a9c2517e9ce961a761022dfa8eb0b62f68f5df9e</id>
<content type='text'>
Improve GetLocalitySortedVersionSet, speeds up apt search by 30%
</content>
</entry>
<entry>
<title>don't sent uninstallable rc-only versions via EDSP</title>
<updated>2016-05-10T12:51:30Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-05-10T12:51:30Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=33190fe3d3c200dcd417cd336f9db11f5f4408d5'/>
<id>urn:sha1:33190fe3d3c200dcd417cd336f9db11f5f4408d5</id>
<content type='text'>
Versions which are only available in dpkg/status aren't installable and
apt doesn't pick them as candidate for this reason – for the same reason
such packages shouldn't be sent to an external solver via EDSP. The
packages are pinned to -1, but if the solver has strict pinning disabled
it could end up picking this version anyhow – which is a request apt can
not satisfy.

Reported-By: Maximiliano Curia &lt;maxy@debian.org&gt; on IRC
</content>
</entry>
<entry>
<title>Speed up GetLocalitySortedVersionSet.</title>
<updated>2016-05-09T19:19:26Z</updated>
<author>
<name>Adrian Wielgosik</name>
<email>adrian.wielgosik@gmail.com</email>
</author>
<published>2016-05-08T19:59:45Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=326a2ecfa9c6fa9d6941d7133e698510d7355ded'/>
<id>urn:sha1:326a2ecfa9c6fa9d6941d7133e698510d7355ded</id>
<content type='text'>
</content>
</entry>
<entry>
<title>gpgv: show always webportal error on NODATA</title>
<updated>2016-05-08T17:46:34Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-05-08T17:46:34Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=2fac0dd5a7a62b67a869cd4c71c9d09159aaa31d'/>
<id>urn:sha1:2fac0dd5a7a62b67a869cd4c71c9d09159aaa31d</id>
<content type='text'>
gpg doesn't give use a UID on NODATA, which we were "expecting" (but not
using for anything), but just an error number. Instead of collecting
these as badsigners which will trigger a "invald signature" error with
remarks like "NODATA 1" we instead adapt a message similar to the NODATA
error of a clearsigned file (which is actually not reached anymore as we
split them up, which fails with a NOSPLIT error, which uses the same
general error message).

In other words: Not a security relevant change, just a user experience
improvement as we now point them to the most likely cause of the
problem instead of saying "invalid signature" which would point them in
the direction of the archive being broken (for everyone) instead.

Closes: 823746
</content>
</entry>
<entry>
<title>implement Identifier field for IndexTargets</title>
<updated>2016-05-08T16:15:28Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-05-08T16:03:48Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=39c724b4848ef8d85c8c425f982dda85f0df1277'/>
<id>urn:sha1:39c724b4848ef8d85c8c425f982dda85f0df1277</id>
<content type='text'>
A frontend like apt-file is only interested in a specific set of files
and selects those easily via "Created-By". If it supports two locations
for those files through it would need to select both and a user would
need to know that implementation detail for sources.list configuration.

The "Identifier" field is hence introduced which by default has the same
value as "Created-By", but can be freely configured – especially it can
be used to give two indexes the same identifier.
</content>
</entry>
</feed>
