<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/test/integration/test-apt-ftparchive-src-cachedb, branch feature/rred</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=feature%2Frred</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=feature%2Frred'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2015-12-19T22:04:34Z</updated>
<entry>
<title>tests: support spaces in path and TMPDIR</title>
<updated>2015-12-19T22:04:34Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-12-15T16:20:26Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=3abb6a6a1e485b3bc899b64b0a1b7dc2db25a9c2'/>
<id>urn:sha1:3abb6a6a1e485b3bc899b64b0a1b7dc2db25a9c2</id>
<content type='text'>
This doesn't allow all tests to run cleanly, but it at least allows to
write tests which could run successfully in such environments.

Git-Dch: Ignore
</content>
</entry>
<entry>
<title>tests: use quiet level 0 by default in tests</title>
<updated>2015-11-19T16:13:56Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-11-19T15:00:33Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=87d6947d51717e8b0e975d913986161598a7259a'/>
<id>urn:sha1:87d6947d51717e8b0e975d913986161598a7259a</id>
<content type='text'>
Git-Dch: Ignore
</content>
</entry>
<entry>
<title>tests: use SHA1 checksum only by default in tests</title>
<updated>2015-09-14T13:22:19Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-09-13T15:25:23Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=c5ede4cac6e6496ce19ccea3313ac6b49ba5e8d6'/>
<id>urn:sha1:c5ede4cac6e6496ce19ccea3313ac6b49ba5e8d6</id>
<content type='text'>
This is mostly a small speedup for the testcases, but it is also handy
to document which tests actually deal with a specific hash compared to
those which 'just' need some hash which can be important while adding
new hashes.

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>
<entry>
<title>test exitcode as well as string equality</title>
<updated>2015-03-16T17:01:54Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-03-09T23:59:44Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=25b86db159fbc3c043628e285c0c1ef24dec2c6e'/>
<id>urn:sha1:25b86db159fbc3c043628e285c0c1ef24dec2c6e</id>
<content type='text'>
We use test{success,failure} now all over the place in the framework, so
its only consequencial to do this in the situations in which we test for
a specific output as well.

Git-Dch: Ignore
</content>
</entry>
<entry>
<title>merge debian/sid into debian/experimental</title>
<updated>2015-03-16T16:59:31Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-03-09T00:34:10Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=d61960d9244340956a27f4ca46aecd15cc75e18b'/>
<id>urn:sha1:d61960d9244340956a27f4ca46aecd15cc75e18b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>128 KiB DSC files ought to be enough for everyone</title>
<updated>2015-01-10T12:31:14Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2015-01-09T00:03:31Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=31be38d205406d4c756684e20b93d62c4701e091'/>
<id>urn:sha1:31be38d205406d4c756684e20b93d62c4701e091</id>
<content type='text'>
Your mileage may vary, but don't worry: There is more than one way to
do it, but our one size fits all is not a bigger hammer, but an entire
roundhouse kick! So brace yourself for the tl;dr: The limit is gone.*

Beware: This fixes also the problem that a double newline is
unconditionally added 'later' which is an overcommitment in case
the dsc filesize is limit-2 &lt;= x &lt;= limit.

* limited to numbers fitting into an unsigned long long.

Closes: 774893
</content>
</entry>
<entry>
<title>use the same code to detect quiet setting in all tools</title>
<updated>2014-11-09T20:45:55Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2014-11-08T19:44:44Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=d9e518c6f7dc0ad464495b586d1b8e115d54d41a'/>
<id>urn:sha1:d9e518c6f7dc0ad464495b586d1b8e115d54d41a</id>
<content type='text'>
Git-Dch: Ignore
</content>
</entry>
<entry>
<title>(try to) fix travis-ci build failures</title>
<updated>2014-05-29T09:23:31Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2014-05-12T19:25:43Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=e1a69e71efc0679815f722480169f16bf02622ab'/>
<id>urn:sha1:e1a69e71efc0679815f722480169f16bf02622ab</id>
<content type='text'>
dpkg on Ubuntu 12.04 does not seem to support parsing arch-specific
dependencies, so we try to detect if we face such a dpkg in the test.

In the other test the order depends on libdb, which changes per arch, so
we just run it through our sorting binary and be happy (hopefully).

Git-Dch: Ignore
</content>
</entry>
<entry>
<title>(try to) fix travis-ci build failures</title>
<updated>2014-05-12T19:25:43Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2014-05-12T19:25:43Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=4f6d26b4d41474aa390329b7e9cb167eb70b2821'/>
<id>urn:sha1:4f6d26b4d41474aa390329b7e9cb167eb70b2821</id>
<content type='text'>
dpkg on Ubuntu 12.04 does not seem to support parsing arch-specific
dependencies, so we try to detect if we face such a dpkg in the test.

In the other test the order depends on libdb, which changes per arch, so
we just run it through our sorting binary and be happy (hopefully).

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