apt/test/integration/test-essential-force-loopbreak, branch 2.3.9Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.3.92021-04-23T15:13:55ZSupport deconfiguring Essential packages2021-04-23T15:13:55ZJulian Andres Klodejulian.klode@canonical.com2021-04-23T15:06:40Zurn:sha1:a7f2152f0ce46322791f0574d76aadfdfbde6bec
dpkg 1.20.8 also made --force-remove-essential optional for
deconfiguring essential packages, so let's do this.
Also extend the test case to make sure we actuall pass
auto-deconfigure and do not make any --remove calls, or
pass --force-remove to dpkg.
regression fix: do require force-loopbreak for Conflicts2021-03-01T20:43:54ZJulian Andres Klodejulian.klode@canonical.com2021-03-01T20:43:03Zurn:sha1:0d51cf142884801c903df0cddaec5545f0174553
Conflicts do require removing the package temporarily, so they really
should not be used.
We need to improve that eventually such that we can deconfigure packages
when we have to remove their dependencies due to conflicts.
Do not require force-loopbreak on Protected packages2021-02-23T18:10:29ZJulian Andres Klodejulian.klode@canonical.com2021-02-23T17:23:30Zurn:sha1:f8ff3afcd42d8b2e6506bc6f44a894149bf87442
dpkg will be changed in 1.20.8 to not require --force-remove for
deconfiguration anymore, but we want to decouple our changes from the
dpkg ones, so let's always pass --force-remove-protected when installing
packages such that we can deconfigure protected packages.
Closes: #983014
pass --force-remove-essential to dpkg only if needed2016-08-10T21:18:04ZDavid Kalnischkiesdavid@kalnischkies.de2016-07-03T11:57:25Zurn:sha1:d3930f8716f439c229cd3d11813823d847a2ecff
APT (usually) knows which package is essential or not, so we can avoid
passing this force flag to dpkg unconditionally if the user hasn't
chosen a non-default essential handling obscuring the information.
tests: support spaces in path and TMPDIR2015-12-19T22:04:34ZDavid Kalnischkiesdavid@kalnischkies.de2015-12-15T16:20:26Zurn:sha1:3abb6a6a1e485b3bc899b64b0a1b7dc2db25a9c2
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
Fix the test suite again2015-08-17T16:37:18ZJulian Andres Klodejak@debian.org2015-08-17T16:37:09Zurn:sha1:e7ebb41440cbe298b07c7fb7c6b20a64a17200f0
Gbp-Dch: ignore
test exitcode as well as string equality2015-03-16T17:01:54ZDavid Kalnischkiesdavid@kalnischkies.de2015-03-09T23:59:44Zurn:sha1:25b86db159fbc3c043628e285c0c1ef24dec2c6e
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
check for failure message in testsuccess/failure2014-10-20T08:37:46ZDavid Kalnischkiesdavid@kalnischkies.de2014-10-19T12:14:37Zurn:sha1:1df24acfdb8ba1cd8bbbaa166f170dda480ce41e
These functions check the exit code of the command, but for apt commands
we can go further and require an error message for non-zero exits and
none for zero exits.
Git-Dch: Ignore
test/integration/test-essential-force-loopbreak: fix on non-amd64 systems2014-06-12T08:09:24ZMichael Vogtmvo@ubuntu.com2014-06-12T08:09:24Zurn:sha1:eb197ed71b1535f3c1715c8a751485ef927b51b7use 'native' instead of 'amd64' as pkg arch2014-05-30T21:15:28ZDavid Kalnischkiesdavid@kalnischkies.de2014-05-30T21:15:28Zurn:sha1:d91e3cfa1992599c088673ef68bcdfd4d0aedc85
Git-Dch: Ignore