summaryrefslogtreecommitdiff
path: root/test
diff options
context:
space:
mode:
authorJulian Andres Klode <jak@debian.org>2016-08-25 15:02:13 +0200
committerJulian Andres Klode <jak@debian.org>2016-08-26 22:24:24 +0200
commitf878d3a862128bc1385616751ae1d78246b1bd01 (patch)
tree7fd62c11232d5f9c8dc12409995fa47c7608382c /test
parent2ed62ba6abcad809d1898a40950f86217af73812 (diff)
downloadapt-f878d3a862128bc1385616751ae1d78246b1bd01.tar.gz
test: Assert multi-arch in the chroot
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
Diffstat (limited to 'test')
-rw-r--r--test/integration/framework2
1 files changed, 1 insertions, 1 deletions
diff --git a/test/integration/framework b/test/integration/framework
index ec57a23c3..546f070d7 100644
--- a/test/integration/framework
+++ b/test/integration/framework
@@ -531,7 +531,7 @@ configdpkg() {
insertinstalledpackage 'dpkg' "all" '1.16.2+fake'
fi
fi
- if command dpkg --assert-multi-arch >/dev/null 2>&1 ; then
+ if dpkg --assert-multi-arch >/dev/null 2>&1 ; then
local ARCHS="$(getarchitectures)"
local DPKGARCH="$(dpkg --print-architecture)"
# this ensures that even if multi-arch isn't active in the view