<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/debian/tests, 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-17T07:52:32Z</updated>
<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>debian: make autopkgtest run with CMake build dir</title>
<updated>2016-08-10T14:11:48Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-08-08T09:31:06Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=7c317e9e90ccbaaab88550f69b902e88e379055c'/>
<id>urn:sha1:7c317e9e90ccbaaab88550f69b902e88e379055c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>CMake: debian: Switch packaging over to CMake and dh 9</title>
<updated>2016-08-06T20:36:02Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-08-06T19:40:01Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=e825742bbbbe99b99d525a3b34832b25a7396c84'/>
<id>urn:sha1:e825742bbbbe99b99d525a3b34832b25a7396c84</id>
<content type='text'>
This new packaging is much easier to read, although the duplication
in the install files is a bit annoying. We should probably also get
rid of the movefiles for solvers, planners, and https method; but
then we have to keep track of which methods exist in the apt package.

Another disadvantage is that building only the documentation packages
also requires building the code, as there's no way to turn off code
building in the project.
</content>
</entry>
<entry>
<title>eipp: let apt make a plan, not make stuff plane</title>
<updated>2016-06-29T10:17:41Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-06-29T07:16:53Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=8e99b22c31eb47d0422e9a69e83dc99bb315ded8'/>
<id>urn:sha1:8e99b22c31eb47d0422e9a69e83dc99bb315ded8</id>
<content type='text'>
Julian noticed on IRC that I fall victim to a lovely false friend by
calling referring to a 'planer' all the time even through these are
machines to e.g. remove splinters from woodwork ("make stuff plane").
The term I meant is written in german in this way (= with a single n)
but in english there are two, aka: 'planner'.

As that is unreleased code switching all instances without any
transitional provisions. Also the reason why its skipped in changelog.

Thanks: Julian Andres Klode
Gbp-Dch: Ignore
</content>
</entry>
<entry>
<title>eipp: provide the internal planer as an external one</title>
<updated>2016-06-27T09:57:12Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-05-28T13:40:59Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=f74d99c6a78caafdc6e32d8cb135683b7154795c'/>
<id>urn:sha1:f74d99c6a78caafdc6e32d8cb135683b7154795c</id>
<content type='text'>
Testing the current implementation can benefit from being able to be
feed an EIPP request and produce a fully compliant response. It is also
a great test for EIPP in general.
</content>
</entry>
<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>tests: Depend on libfile-fcntllock-perl to shut up dpkg-gencontrol</title>
<updated>2015-12-14T09:00:32Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2015-12-14T08:58:59Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=369ddff642effc810129c9b28b3fbbc0976c46e9'/>
<id>urn:sha1:369ddff642effc810129c9b28b3fbbc0976c46e9</id>
<content type='text'>
Ubuntu's autopkgtest server always prints

  dpkg-gencontrol: warning: File::FcntlLock not available; using flock which is not NFS-safe

which is somewhat annoying. Work around that by depending on that
perl stuff for the test suite.

Gbp-Dch: ignore
</content>
</entry>
<entry>
<title>autopkgtest: use the quiet mode as for travis and co</title>
<updated>2015-11-28T12:27:06Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-11-28T00:30:53Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=052a7f48e769c10fb25d5b8adbc71dc085913add'/>
<id>urn:sha1:052a7f48e769c10fb25d5b8adbc71dc085913add</id>
<content type='text'>
Git-Dch: Ignore
</content>
</entry>
<entry>
<title>tests: don't use hardcoded port for http and https</title>
<updated>2015-09-15T08:16:09Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-09-14T22:33:12Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=6c0765c096ffb4df14169236c865bbb2b10974ae'/>
<id>urn:sha1:6c0765c096ffb4df14169236c865bbb2b10974ae</id>
<content type='text'>
This allows running tests in parallel.

Git-Dch: Ignore
</content>
</entry>
<entry>
<title>sync TFRewrite*Order arrays with dpkg and dak</title>
<updated>2015-05-11T15:22:32Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-05-09T16:55:41Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=e8fb1cdfdd13e45f2b3abbd57a28b57ae6137f14'/>
<id>urn:sha1:e8fb1cdfdd13e45f2b3abbd57a28b57ae6137f14</id>
<content type='text'>
dpkg and dak know various field names and order them in their output,
while we have yet another order and have to play catch up with them as
we are sitting between chairs here and neither order is ideal for us,
too.

A little testcase is from now on supposed to help ensureing that we do
not derivate to far away from which fields dpkg knows and orders.
</content>
</entry>
</feed>
