<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/test/integration/framework, branch 1.7.0_alpha0</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.7.0_alpha0</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.7.0_alpha0'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2018-04-15T18:57:53Z</updated>
<entry>
<title>Merge branch 'pu/zstd' into 'master'</title>
<updated>2018-04-15T18:57:53Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2018-04-15T18:57:53Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=1cbb4c95f3fdd0872a7f1cb0f970f50a68c13959'/>
<id>urn:sha1:1cbb4c95f3fdd0872a7f1cb0f970f50a68c13959</id>
<content type='text'>
pu/zstd

See merge request apt-team/apt!8</content>
</entry>
<entry>
<title>test: export GCOV_ERROR_FILE=/dev/null to make it fail less/no tests</title>
<updated>2018-04-06T13:24:03Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2018-04-06T13:24:03Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=be63b9a35f6bc2e3cb00ad9f11a757ee1c4bb79d'/>
<id>urn:sha1:be63b9a35f6bc2e3cb00ad9f11a757ee1c4bb79d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>apt-pkg: Add support for zstd</title>
<updated>2018-03-12T07:56:59Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2018-03-08T08:33:39Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=4de4200ec2717e777bbf99ed82d1b4344f078ec2'/>
<id>urn:sha1:4de4200ec2717e777bbf99ed82d1b4344f078ec2</id>
<content type='text'>
zstd is a compression algorithm developed by facebook. At level 19,
it is about 6% worse in size than xz -6, but decompression is multiple
times faster, saving about 40% install time, especially with eatmydata
on cloud instances.
</content>
</entry>
<entry>
<title>Merge branch 'pu/not-valid-before' into 'master'</title>
<updated>2018-02-19T15:06:06Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2018-02-19T15:06:06Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=928ecff984be22632c27a69e072741e74491292c'/>
<id>urn:sha1:928ecff984be22632c27a69e072741e74491292c</id>
<content type='text'>
Check that Date of Release file is not in the future

See merge request apt-team/apt!3</content>
</entry>
<entry>
<title>Check that Date of Release file is not in the future</title>
<updated>2018-02-19T15:05:01Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2018-01-29T15:15:41Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=9e5899cac1a6367e3769af52a724821880e538f6'/>
<id>urn:sha1:9e5899cac1a6367e3769af52a724821880e538f6</id>
<content type='text'>
By restricting the Date field to be in the past, an attacker cannot
just create a repository from the future that would be accepted as
a valid update for a repository.

This check can be disabled by Acquire::Check-Date set to false. This
will also disable Check-Valid-Until and any future date related checking,
if any - the option means: "my computers date cannot be trusted."

Modify the tests to allow repositories to be up to 10 hours in the
future, so we can keep using hours there to simulate time changes.
</content>
</entry>
<entry>
<title>tests: set debhelper compat 10 and R³ by default</title>
<updated>2018-02-19T14:56:09Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2018-01-27T01:15:35Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=7aaf9b2c63aa8bdd87de4c19dcf1742c686a1cc2'/>
<id>urn:sha1:7aaf9b2c63aa8bdd87de4c19dcf1742c686a1cc2</id>
<content type='text'>
The testpackages hardly need debhelper at all, so any version would do,
and they build without root rights by definition, but declaring it
explicitly can't hurt and in the case of debhelper it would be sad if
our testcases break one day because the old compat level is removed.

Gbp-Dch: Ignore
</content>
</entry>
<entry>
<title>allow the apt/lists/auxfiles/ directory to be missing</title>
<updated>2018-01-19T20:55:39Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2018-01-19T01:20:40Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=38d444af2632219ab399dabadaaefaa4dcdd6ebf'/>
<id>urn:sha1:38d444af2632219ab399dabadaaefaa4dcdd6ebf</id>
<content type='text'>
apt 1.6~alpha6 introduced aux requests to revamp the implementation of
a-t-mirror. This already included the potential of running as non-root,
but the detection wasn't complete resulting in errors or could produce
spurious warnings along the way if the directory didn't exist yet.

References: ef9677831f62a1554a888ebc7b162517d7881116
Closes: 887624
</content>
</entry>
<entry>
<title>allow a method to request auxiliary files</title>
<updated>2018-01-03T17:55:41Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2017-08-12T14:21:13Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=ef9677831f62a1554a888ebc7b162517d7881116'/>
<id>urn:sha1:ef9677831f62a1554a888ebc7b162517d7881116</id>
<content type='text'>
If a method needs a file to operate like e.g. mirror needs to get a list
of mirrors before it can redirect the the actual requests to them. That
could easily be solved by moving the logic into libapt directly, but by
allowing a method to request other methods to do something we can keep
this logic contained in the method and allow e.g. also methods which
perform binary patching or similar things.

Previously they would need to implement their own acquire system inside
the existing one which in all likelyhood will not support the same
features and methods nor operate with similar security compared to what
we have already running 'above' the requesting method. That said, to
avoid methods producing conflicts with "proper" files we are downloading
a new directory is introduced to keep the auxiliary files in.

[The message magic number 351 is a tribute to the german Grundgesetz
article 35 paragraph 1 which defines that all authorities of the
state(s) help each other on request.]
</content>
</entry>
<entry>
<title>implement fallback to alternative URIs for all items</title>
<updated>2017-12-13T22:56:29Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2017-10-27T17:09:45Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=355e1aceac1dd05c4c7daf3420b09bd860fd169d'/>
<id>urn:sha1:355e1aceac1dd05c4c7daf3420b09bd860fd169d</id>
<content type='text'>
For deb files we always supported falling back from one server to the
other if one failed to download the deb, but that was hardwired in the
handling of this specific item. Moving this alongside the retry
infrastructure we can implement it for all items and allow methods to
use this as well by providing additional URIs in a redirect.
</content>
</entry>
<entry>
<title>implement Acquire::Retries support for all items</title>
<updated>2017-12-13T22:56:29Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2017-10-25T23:09:48Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=dff555d40bb9776b5b809e06527e46b15e78736c'/>
<id>urn:sha1:dff555d40bb9776b5b809e06527e46b15e78736c</id>
<content type='text'>
Moving the Retry-implementation from individual items to the worker
implementation not only gives every file retry capability instead of
just a selected few but also avoids needing to implement it in each item
(incorrectly).
</content>
</entry>
</feed>
