From 94ff66799a94576ff8003b99d78be6765e6f4500 Mon Sep 17 00:00:00 2001 From: David Kalnischkies Date: Thu, 19 Mar 2026 09:25:19 +0000 Subject: Do not use unexpected operator in test-apt-get-satisfy Observing a testrun carefully included: ./test-apt-get-satisfy: 101: [: unexpected operator Yes, == is not a valid operator here, should just be =. The result is that we unconditionally skip a single check, hardly so much the end of the world that we need to tell everyone as no tests were failed, but no good anyhow. Fixes: 5e8e69cdd6b512480f3208298725e1e44c80f06e Gbp-Dch: Ignore --- test/integration/test-apt-get-satisfy | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'test') diff --git a/test/integration/test-apt-get-satisfy b/test/integration/test-apt-get-satisfy index 3d215ff86..b40467d34 100755 --- a/test/integration/test-apt-get-satisfy +++ b/test/integration/test-apt-get-satisfy @@ -98,7 +98,7 @@ The following packages have unmet dependencies: satisfy:command-line : Depends: depends (>= 2) but it is not going to be installed E: Unable to correct problems, you have held broken packages." aptget satisfy --simulate "depends (>= 2)" "Conflicts: conflicts:i386 (>= 1) [i386], conflicts:amd64 (>= 1) [amd64]" --solver internal -if [ "$APT_SOLVER" == "internal" ]; then +if [ "$APT_SOLVER" = "internal" ]; then # FIXME: solver3 doesn't produce nice errors in the external solver scenario testfailureequal "Reading package lists... Building dependency tree... -- cgit v1.2.3-70-g09d2