<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/test/integration/framework, branch 1.3.1</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.3.1</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.3.1'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2016-09-07T12:00:38Z</updated>
<entry>
<title>test: Always install dpkg into our tests, regardless of MA</title>
<updated>2016-09-07T12:00:38Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-09-07T11:35:40Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=561a3557e7fa6c4ed693c3bb486d189a468a8080'/>
<id>urn:sha1:561a3557e7fa6c4ed693c3bb486d189a468a8080</id>
<content type='text'>
Even if we only configure a single architecture, install dpkg, so
dpkg can assert multi arch correctly. This also has the nice side
effect of making single architecture and multiple architecture
test cases more uniform.

This fixes a regression from f878d3a862128bc1385616751ae1d78246b1bd01
("test: Assert multi-arch in the chroot").
</content>
</entry>
<entry>
<title>test: framework: Ensure copied status files have trailing lines</title>
<updated>2016-09-07T12:00:37Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-09-07T11:23:26Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=c382e0dff11beb00632d67d9361831358a38e465'/>
<id>urn:sha1:c382e0dff11beb00632d67d9361831358a38e465</id>
<content type='text'>
If we copied one of the existing status files, we might not have
a trailing newline, so let's add one.

Gbp-Dch: ignore
</content>
</entry>
<entry>
<title>test: Pass -d to dpkg-buildpackage</title>
<updated>2016-08-30T15:37:59Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-08-30T15:37:59Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=9109c3c309e95a6d99a88f945f17c37e5c04c105'/>
<id>urn:sha1:9109c3c309e95a6d99a88f945f17c37e5c04c105</id>
<content type='text'>
This works around an issue on Fedora where dpkg complains about
missing  build-essential:

	dpkg-checkbuilddeps: Unmet build dependencies: build-essential:native

Gbp-Dch: ignore
</content>
</entry>
<entry>
<title>test, travis: Quieter testing with a new -qq mode</title>
<updated>2016-08-29T13:42:06Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-08-19T18:37:28Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=30ea7a60404ee53393235827202968393951d106'/>
<id>urn:sha1:30ea7a60404ee53393235827202968393951d106</id>
<content type='text'>
Introduce a new -qq mode for our integration test framework,
and make travis use it.

The new -qq mode sets MSGLEVEL to 1. In MSGLEVEL=1, no messages
are generated for passed tests, and all testcase filenames are
printed in the same line.

Also install first in travis, do not ls the installed output
and run the install with chronic, so we only get output if it
failed.

Gbp-Dch: ignore
</content>
</entry>
<entry>
<title>randomize acquire order for same type index files</title>
<updated>2016-08-29T07:22:25Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-08-28T10:58:20Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=4ff5e237d5685be187a75c563b86e80ea3e7cc01'/>
<id>urn:sha1:4ff5e237d5685be187a75c563b86e80ea3e7cc01</id>
<content type='text'>
Without randomizing the order in which we download the index files we
leak needlessly information to the mirrors of which architecture is
native or foreign on this system. More importantly, we leak the order in
which description translations will be used which in most cases will e.g.
have the native tongue first.

Note that the leak effect in practice is limited as apt detects if a file
it wants to download is already available in the latest version from a
previous download and does not query the server in such cases. Combined
with the fact that Translation files are usually updated infrequently
and not all at the same time, so a mirror can never be sure if it got asked
about all files the user wants.
</content>
</entry>
<entry>
<title>Merge branch 'portability/freebsd'</title>
<updated>2016-08-26T22:31:03Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-08-26T22:31:03Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=6a68315e938eb2611806658828ecea86805822e7'/>
<id>urn:sha1:6a68315e938eb2611806658828ecea86805822e7</id>
<content type='text'>
</content>
</entry>
<entry>
<title>test: Use :$(id -gn) instead of :root (when run as root)</title>
<updated>2016-08-26T20:24:24Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-08-25T13:35:32Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=757ec4e1ef633f9867928559df82adf3d0ac7b78'/>
<id>urn:sha1:757ec4e1ef633f9867928559df82adf3d0ac7b78</id>
<content type='text'>
On BSD systems, the root group is wheel, not root, so let's
just use the default group here.

Gbp-Dch: ignore
</content>
</entry>
<entry>
<title>test: Assert multi-arch in the chroot</title>
<updated>2016-08-26T20:24:24Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-08-25T13:02:13Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=f878d3a862128bc1385616751ae1d78246b1bd01'/>
<id>urn:sha1:f878d3a862128bc1385616751ae1d78246b1bd01</id>
<content type='text'>
The host system might not have a dpkg installed, which makes
dpkg fail with:

  dpkg not recorded as installed, cannot check for multi-arch support!

That's entirely useless of course. We want to know if dpkg could
support multi-arch in our chroot, so we pseudo-install dpkg into
the chroot and pretend it's version is one version higher than
the minimum dpkg version, so dpkg --assert-multi-arch works on
recent dpkgs.

Gbp-Dch: ignore
</content>
</entry>
<entry>
<title>test: More portable check for dpkg versions</title>
<updated>2016-08-26T20:22:47Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-08-24T14:21:12Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=03ae49aca57b499f8ef497c2777b3eaef2516d1a'/>
<id>urn:sha1:03ae49aca57b499f8ef497c2777b3eaef2516d1a</id>
<content type='text'>
This check should work regardless if dpkg was installed by dpkg
or by a native package manager like RPM or pkg.

Gbp-Dch: ignore
</content>
</entry>
<entry>
<title>test: Use a file to determine TEST_DEFAULT_GROUP</title>
<updated>2016-08-26T20:17:55Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2016-08-24T14:05:37Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=71e22da91ff888cf645e5083fbac7839846111d2'/>
<id>urn:sha1:71e22da91ff888cf645e5083fbac7839846111d2</id>
<content type='text'>
This is more safe against sticky bits. For example, in FreeBSD
all files created in /tmp have the group set to wheel.

Gbp-Dch: ignore
</content>
</entry>
</feed>
