summaryrefslogtreecommitdiff
path: root/test/integration/test-bug-632221-cross-dependency-satisfaction
diff options
context:
space:
mode:
authorColin Watson <cjwatson@ubuntu.com>2013-08-01 13:19:43 +0200
committerMichael Vogt <mvo@debian.org>2013-08-01 21:28:11 +0200
commit58f3aec5837ac1d88747530bb41add0ac93019d0 (patch)
tree41eaa3159fcbd3a81fd7620025b21a496b68baad /test/integration/test-bug-632221-cross-dependency-satisfaction
parent1819ccef3c9ac0a6b1a413b89b435b4f7d601afd (diff)
prefer native arch over higher priority for providers
The rational from the buglog: > The problem here is that the Priority field in one of the Packages files > is incorrect due to a mishap with reprepro configuration, […] the > amd64 version is Priority: standard but the arm64 version is Priority: > optional (and has a stray "optional: interpreters" field). > […] > However, Priority is a rather weak property of a package because it's > typically applied via overrides, and it's easy for maintainers of > third-party repositories to misconfigure them so that overrides aren't > applied correctly. It shouldn't be ranked ahead of choosing packages > from the native architecture. In this case, I have no user-mode > 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
Diffstat (limited to 'test/integration/test-bug-632221-cross-dependency-satisfaction')
0 files changed, 0 insertions, 0 deletions