From 0dde581905291223e3f3b67cc739bd4db1e2055f Mon Sep 17 00:00:00 2001 From: David Kalnischkies Date: Wed, 18 Jan 2017 11:31:13 +0100 Subject: don't show update stats if cache generation is disabled Unlikely that anyone is actually running into this, but if we asked to not generate a cache and avoid it in the first step we shouldn't create one implicitly anyway by displaying the statistics. (cherry picked from commit 33f982b90a4f77be18cb82daf8c79e9c5513761c) (cherry picked from commit 1d017d04c5fdbf71a35e8f154f01bc94305ad798) --- test/integration/test-apt-cli-update | 1 + 1 file changed, 1 insertion(+) (limited to 'test/integration/test-apt-cli-update') diff --git a/test/integration/test-apt-cli-update b/test/integration/test-apt-cli-update index b423072c3..cc8d051d2 100755 --- a/test/integration/test-apt-cli-update +++ b/test/integration/test-apt-cli-update @@ -15,6 +15,7 @@ setupaptarchive --no-update testfailuremsg 'E: The update command takes no arguments' apt update arguments +testempty apt update -qq -o pkgCacheFile::Generate=false testsuccessequal "1 package can be upgraded. Run 'apt list --upgradable' to see it." apt update -qq cp dpkg.status rootdir/var/lib/dpkg/status -- cgit v1.2.3