<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/test/integration/framework, branch 1.4</title>
<subtitle>Debians commandline package manager</subtitle>
<id>https://git.kalnischkies.de/apt/atom?h=1.4</id>
<link rel='self' href='https://git.kalnischkies.de/apt/atom?h=1.4'/>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/'/>
<updated>2017-01-19T14:59:38Z</updated>
<entry>
<title>fix various typos reported by spellintian</title>
<updated>2017-01-19T14:59:38Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2017-01-19T14:14:19Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=93cff633a830e222693fc0f3d78e6e534d1126ee'/>
<id>urn:sha1:93cff633a830e222693fc0f3d78e6e534d1126ee</id>
<content type='text'>
Most of them in (old) code comments. The two instances of user visible
string changes the po files of the manpages are fixed up as well.

Gbp-Dch: Ignore
Reported-By: spellintian
</content>
</entry>
<entry>
<title>allow warning generation for non-whitelisted options</title>
<updated>2016-12-31T17:24:12Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-12-31T17:24:12Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=ae73a2944a89e0d2406a2aab4a4c082e1e9da3f9'/>
<id>urn:sha1:ae73a2944a89e0d2406a2aab4a4c082e1e9da3f9</id>
<content type='text'>
The idea is simple: Each¹ Find*( call starts with a call check if the
given option (with the requested type) exists in the whitelist. The
whitelist is specified via our configure-index file so that we have
a better chance at keeping it current. the whitelist is loaded via a
special (undocumented for now) configuration stanza and if none is
loaded the empty whitelist will make it so that no warnings are shown.

Much needs to be done still, but that is as good a time as any to take a
snapshot of the current state and release it into the wild given that it
found some bugs already and has no practical effect on users.

¹ not all in this iteration, but many
</content>
</entry>
<entry>
<title>tests: cache the apt-key homedir used for Release signing</title>
<updated>2016-12-21T18:36:10Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-12-18T16:42:17Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=4ce2f35248123ff2366c8c365ad6a94945578d66'/>
<id>urn:sha1:4ce2f35248123ff2366c8c365ad6a94945578d66</id>
<content type='text'>
Importing a new secret key into gpg(2) can be increadibly slow which
prolongs the test runs significantly – by caching the homedir we gain a
significant speedbonus as reimporting already present keys seems like a
far less costly operation.

Git-Dch: Ignore
</content>
</entry>
<entry>
<title>optional write aptwebserver log to client specific files</title>
<updated>2016-11-24T23:15:13Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-11-24T11:14:39Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=e1ae0531bfad0fce8590c26d1e38825df22d812a'/>
<id>urn:sha1:e1ae0531bfad0fce8590c26d1e38825df22d812a</id>
<content type='text'>
The test test-handle-redirect-as-used-mirror-change serves multiple
clients at the same time, so the order of the output is undefined and
once in a while the two clients will intermix their lines causing the
grep we perform on it later to fail making our tests fail.

Solved by introducing client-specific logfiles which we all grep and
sort the result to have the results more stable.

Git-Dch: Ignore
</content>
</entry>
<entry>
<title>apt-ftparchive: Support NotAutomatic and ButAutomaticUpgrades fields</title>
<updated>2016-11-11T22:40:39Z</updated>
<author>
<name>James Clarke</name>
<email>jrtc27@jrtc27.com</email>
</author>
<published>2016-11-11T16:33:25Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=a658ffbf1911ae9b9838615d0a60f4613e642553'/>
<id>urn:sha1:a658ffbf1911ae9b9838615d0a60f4613e642553</id>
<content type='text'>
This also changes Acquire-By-Hash to be "yes" rather than "true", so it
is consistent with dak's output.

Closes: #272557
</content>
</entry>
<entry>
<title>travis: ignore profiling warning in test diffs</title>
<updated>2016-11-10T20:28:12Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-11-10T20:28:12Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=58608941e6b58a46109b7cd875716b3d8054c4bf'/>
<id>urn:sha1:58608941e6b58a46109b7cd875716b3d8054c4bf</id>
<content type='text'>
On Travis CI running tests with code coverage enabled sometimes
generates lines like:
  profiling:/path/to/file.gcda:Merge mismatch for function 257
It would be nice if we could resolve this somehow as it garbles the
statistics, but until then it is far more annoying that this causes
test failures for no good reason.

Gbp-Dch: Ignore
</content>
</entry>
<entry>
<title>reset HOME, USER(NAME), TMPDIR &amp; SHELL in DropPrivileges</title>
<updated>2016-11-09T18:33:33Z</updated>
<author>
<name>David Kalnischkies</name>
<email>david@kalnischkies.de</email>
</author>
<published>2016-11-09T18:15:01Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=34b491e735ad47c4805e63f3b83a659b8d10262b'/>
<id>urn:sha1:34b491e735ad47c4805e63f3b83a659b8d10262b</id>
<content type='text'>
We can't cleanup the environment like e.g. sudo would do as you usually
want the environment to "leak" into these helpers, but some variables
like HOME should really not have still the value of the root user – it
could confuse the helpers (USER) and HOME isn't accessible anyhow.

Closes: 842877
</content>
</entry>
<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>
</feed>
