<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/test, branch 1.2.7</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.2.7</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.2.7'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2016-03-15T17:55:02Z</updated>
<entry>
<title>Fix bug where the problemresolve can put a pkg into a heisenstate</title>
<updated>2016-03-15T17:55:02Z</updated>
<author>
<name>Michael Vogt</name>
<email>mvo@ubuntu.com</email>
</author>
<published>2016-03-15T12:13:54Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=0390edd5452b081f8efcf412f96d535a1d959457'/>
<id>urn:sha1:0390edd5452b081f8efcf412f96d535a1d959457</id>
<content type='text'>
The problemresolver will set the candidate version for pkg P back
to the current version if it encounters an impossible to satisfy
critical dependency on P. However it did not set the State of
the package back as well which lead to a situation where P is
neither in Keep,Install,Upgrade,Delete state.

Note that this can not be tested via the traditional sh based
framework. I added a python-apt based test for this.

LP: #1550741

[jak@debian.org: Make the test not fail if apt_pkg cannot be
 imported]
</content>
</entry>
<entry>
<title>test: Move --weak-digest initialization to the right place</title>
<updated>2016-03-14T12:49:25Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-03-14T12:49:25Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=0cbb7e29c5dad2178896d8eaf41ad616bb0111da'/>
<id>urn:sha1:0cbb7e29c5dad2178896d8eaf41ad616bb0111da</id>
<content type='text'>
This was wrong and caused some issues because apt-key invoked
host apt-config with our library.

Gbp-Dch: ignore
</content>
</entry>
<entry>
<title>test: Use SHA512 digests for GPG, reject SHA1-based signatures</title>
<updated>2016-03-14T12:46:33Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-03-14T12:24:17Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=493a813e8a743cfe763bf5eb18073ef9f51dabc2'/>
<id>urn:sha1:493a813e8a743cfe763bf5eb18073ef9f51dabc2</id>
<content type='text'>
This makes the test suite safe if we ever need to reject SHA1
signatures in an update.
</content>
</entry>
<entry>
<title>enforce verify of filesize in 'apt-get source'</title>
<updated>2016-03-14T10:54:08Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-03-13T21:44:37Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=d4c45145553781418c25343ac1478f62da645851'/>
<id>urn:sha1:d4c45145553781418c25343ac1478f62da645851</id>
<content type='text'>
The structure we parse the data into has a dedicated size field, but it
tends to be easier to handle it as a (very weak) checksum.
</content>
</entry>
<entry>
<title>don't use Desc.URI to calculate .diff/Index filenames</title>
<updated>2016-03-14T10:47:19Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-03-13T00:02:30Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=b7a1076f18022cbeb7baf4d82ab8bae0f725a573'/>
<id>urn:sha1:b7a1076f18022cbeb7baf4d82ab8bae0f725a573</id>
<content type='text'>
The URI descibing an item can change via mirrors/redirectors which
causes the .diff/Index files to get the wrong names in storage.

Git-Dch: Ignore
</content>
</entry>
<entry>
<title>flush line-clearing on progress stop before post-invoke</title>
<updated>2016-03-14T10:47:19Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-03-10T12:06:29Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=915f4ac6d9ae239bd1aef47892075d019ec8b581'/>
<id>urn:sha1:915f4ac6d9ae239bd1aef47892075d019ec8b581</id>
<content type='text'>
All other interactions with std::cout are flushed directly, just in the
stop case we hadn't done it – no problem expect if there is still output
coming after apt is done like in the case of a post-invoke script
producing output.

Closes: 793672
</content>
</entry>
<entry>
<title>aptwebserver: fix html validation issues</title>
<updated>2016-03-14T10:47:19Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-03-13T22:30:05Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=12f40394b3940573c0e63d74722a95148fb1ad39'/>
<id>urn:sha1:12f40394b3940573c0e63d74722a95148fb1ad39</id>
<content type='text'>
Iceweasel^WFirefox complains about the missing encoding in its console
which can be a bit annoying in interactive sessions, so fixing these
issues has no effect on apt itself, but on the testers.

Git-Dch: Ignore
</content>
</entry>
<entry>
<title>require $(HASH)-Download field in .diff/Index files</title>
<updated>2016-03-14T10:47:19Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-03-14T00:09:32Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=4a808deaac462e7714a345dac676c6da294a2ee0'/>
<id>urn:sha1:4a808deaac462e7714a345dac676c6da294a2ee0</id>
<content type='text'>
Now that we ignore SHA1-only files it makes sense to require also the
provision of hashes for the compressed patches as this was introduced in
the same patchset as support for non-SHA1 hashes in the file itself in
dak and adding support in other archive creators (if they support pdiffs
at all) will likely be in the same batch.

The reason for the change itself is simple: If you are 'scared' enough
about the security of SHA1, you shouldn't uncompress a file you haven't
verified at all – after all, it could be exploiting a bug or a zip bomb.
</content>
</entry>
<entry>
<title>test: remove SHA1 support testing as unsupported</title>
<updated>2016-03-14T10:47:18Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-03-13T20:49:37Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=8d0d92558c00d1825e413ce67be51a46a5c18aea'/>
<id>urn:sha1:8d0d92558c00d1825e413ce67be51a46a5c18aea</id>
<content type='text'>
Given that we refuse to use SHA1-only .diff/Indexes no point in shipping
and running code which pretends to check support for it which given that
all these tests are run 3 times eats a noticeable amount of time.

Git-Dch: Ignore
</content>
</entry>
<entry>
<title>Test that SHA1-only .diff/Index files are not used</title>
<updated>2016-03-13T12:05:30Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-03-13T12:05:30Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=f345d0571d055c2cd5da3a9e423753f1ac21a9aa'/>
<id>urn:sha1:f345d0571d055c2cd5da3a9e423753f1ac21a9aa</id>
<content type='text'>
Ensure that .diff/Index files that only contain SHA1 values and no
SHA2 values are not used.
</content>
</entry>
</feed>
