This bug was fixed in the package apt - 1.9.4
---------------
apt (1.9.4) experimental; urgency=medium
* CMake: Pass -Werror=return-type to gcc
* CMake: Produce a fatal error if triehash could not be found
* apt.systemd.daily: Do not numerically check if intervals equal 0
(LP: #1840995)
* srvrec: Use re-entrant resolver functions
* Pass --abort-after=1 to dpkg when using --force-depends (Closes: #935910)
(LP: #1844634)
* Fix use of GTest to adjust for GTest 1.9
-- Julian Andres Klode <[email protected]> Thu, 19 Sep 2019 11:13:47
+0200
** Changed in: apt (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1844634
Title:
Removals keep removing dependencies if removal of a package fails
Status in apt package in Ubuntu:
Fix Released
Status in apt package in Debian:
New
Bug description:
[Impact]
Assuming packages A and B, with A depending on B. A has a failing
prerm script.
Expected behavior:
- A fails to be removed, A and B stay unchanged
Actual behavior:
- A fails to be removed
- B is still removed
This might crash their system (e.g. if A is systemd and B is
libsystemd0).
[Test case]
See Impact. An automated version of the test case
(test-apt-get-remove-depends) is included and run on autopkgtest.
[Regression potential]
We now abort earlier in removal failures, that might be harder to recover
from or not, nobody really knows.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1844634/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
