Removals keep removing dependencies if removal of a package fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| apt (Debian) |
Fix Released
|
Unknown
|
||
| apt (Ubuntu) |
High
|
Julian Andres Klode | ||
| Disco |
Undecided
|
Unassigned |
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-
[Regression potential]
We now abort earlier in removal failures, that might be harder to recover from or not, nobody really knows.
description: | updated |
Changed in apt (Ubuntu): | |
importance: | Undecided → High |
status: | New → Fix Committed |
assignee: | nobody → Julian Andres Klode (juliank) |
Changed in apt (Debian): | |
status: | Unknown → New |
Launchpad Janitor (janitor) wrote : | #1 |
Changed in apt (Ubuntu): | |
status: | Fix Committed → Fix Released |
Changed in apt (Debian): | |
status: | New → Fix Released |
Hello Julian, or anyone else affected,
Accepted apt into disco-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Changed in apt (Ubuntu Disco): | |
status: | New → Fix Committed |
tags: | added: verification-needed verification-needed-disco |
All autopkgtests for the newly accepted apt (1.8.4) for disco have finished running.
The following regressions have been reported in tests triggered by the package:
reprotest/0.7.8 (s390x)
gcc-snapshot/
apt/1.8.4 (amd64, armhf, s390x, ppc64el, arm64, i386)
autopkgtest/
gcc-7/7.
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
https:/
[1] https:/
Thank you!
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 address hidden> Thu, 19 Sep 2019 11:13:47 +0200