<feed xmlns='http://www.w3.org/2005/Atom'>
<title>apt/test/integration/test-prefer-native-architecture-over-higher-priority, 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>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>Fix the test suite again</title>
<updated>2015-08-17T16:37:18Z</updated>
<author>
<name>Julian Andres Klode</name>
<email>jak@debian.org</email>
</author>
<published>2015-08-17T16:37:09Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=e7ebb41440cbe298b07c7fb7c6b20a64a17200f0'/>
<id>urn:sha1:e7ebb41440cbe298b07c7fb7c6b20a64a17200f0</id>
<content type='text'>
Gbp-Dch: ignore
</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>prefer native arch over higher priority for providers</title>
<updated>2013-08-01T11:37:52Z</updated>
<author>
<name>Colin Watson</name>
<email>cjwatson@ubuntu.com</email>
</author>
<published>2013-08-01T11:19:43Z</published>
<link rel='alternate' type='text/html' href='https://git.kalnischkies.de/apt/commit/?id=096bd9f59750f6bea754d3a05e240c9eea0f6b53'/>
<id>urn:sha1:096bd9f59750f6bea754d3a05e240c9eea0f6b53</id>
<content type='text'>
The rational from the buglog:
&gt; The problem here is that the Priority field in one of the Packages files
&gt; is incorrect due to a mishap with reprepro configuration, […] the
&gt; amd64 version is Priority: standard but the arm64 version is Priority:
&gt; optional (and has a stray "optional: interpreters" field).
&gt; […]
&gt; However, Priority is a rather weak property of a package because it's
&gt; typically applied via overrides, and it's easy for maintainers of
&gt; third-party repositories to misconfigure them so that overrides aren't
&gt; applied correctly.  It shouldn't be ranked ahead of choosing packages
&gt; from the native architecture.  In this case, I have no user-mode
&gt; emulation for arm64 set up, so choosing m4:arm64 simply won't work.

This effectly makes the priority the least interesting data point in
chosing a provider, which is in line with the other checks we have
already order above priority in the past and also has a certain appeal by
the soft irony it provides.

Closes: #718482
</content>
</entry>
</feed>
