<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/debian/tests/control, branch master</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=master</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2019-08-15T07:53:41Z</updated>
<entry>
<title>test: Use valgrind to ensure Acquire::Queue-Mode=access does not crash</title>
<updated>2019-08-15T07:53:41Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>julian.klode@canonical.com</email>
</author>
<published>2019-08-15T07:50:22Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=56820d4c244e896a62f57ff96801dc1283b8b0e2'/>
<id>urn:sha1:56820d4c244e896a62f57ff96801dc1283b8b0e2</id>
<content type='text'>
Unfortunately for us, apt update with Acquire::Queue-Mode=access
does not always crash on a real system, so run the whole thing
in valgrind.
</content>
</entry>
<entry>
<title>Add pkg-config files for the apt-pkg and apt-inst libraries</title>
<updated>2019-03-08T18:13:06Z</updated>
<author>
<name>Corentin Noël</name>
<email>corentin.noel@collabora.com</email>
</author>
<published>2018-06-03T15:37:44Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=7c461f0396d413acb9a950f3df9ea6d062896cd7'/>
<id>urn:sha1:7c461f0396d413acb9a950f3df9ea6d062896cd7</id>
<content type='text'>
Closes: #439121
</content>
</entry>
<entry>
<title>tests: install aptitude for test-method-mirror</title>
<updated>2018-02-19T14:57:43Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2018-02-07T00:45:03Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=13c85c9cec9e071e90ea190a74cbaabe7c51024c'/>
<id>urn:sha1:13c85c9cec9e071e90ea190a74cbaabe7c51024c</id>
<content type='text'>
This is an optional dependency for the test, but the skipping of the
test is very noisy and checking that an unchanged aptitude isn't
downright exploding with our libapt isn't a bad idea either.

Gbp-Dch: Ignore
</content>
</entry>
<entry>
<title>debian/tests/control: Add dpkg so we get triggered by it</title>
<updated>2017-10-26T11:21:23Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2017-10-26T11:21:23Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=b1989ab988cf4da47f979933e551b6dda694dcf2'/>
<id>urn:sha1:b1989ab988cf4da47f979933e551b6dda694dcf2</id>
<content type='text'>
We do want to get our autopkgtests triggered by dpkg uploads
in Ubuntu, but this does not happen because we don't have
an explicit dependency on it. Add one.
</content>
</entry>
<entry>
<title>tests/control: Handle the gpg1/gpg2 mess a bit better</title>
<updated>2016-08-19T14:50:23Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-08-18T12:21:16Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=6fbe5739701f4c63bcd5c68d9ecc19e9e28288de'/>
<id>urn:sha1:6fbe5739701f4c63bcd5c68d9ecc19e9e28288de</id>
<content type='text'>
Hardcoding gpgv1 and gnupg1 breaks Ubuntu, because on Ubuntu,
these packages do not exist yet. Instead allow gnupg (&lt;&lt; 2)
for gnupg1 and gnupg2 for gnupg (&gt;= 2), so we cover all
potential combinations.
</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>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>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>add gnupg and gnupg2 as test-dependency</title>
<updated>2014-09-26T22:12:15Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2014-09-26T21:09:01Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=98f0d7b3d9d7ed0a5cf11d8f9327a021954816b6'/>
<id>urn:sha1:98f0d7b3d9d7ed0a5cf11d8f9327a021954816b6</id>
<content type='text'>
apt can work with both, so it has an or-dependency on them,
but the tests want to play with both of them.

Git-Dch: Ignore
</content>
</entry>
</feed>
