[Bug 1844634] Autopkgtest regression report (apt/1.8.4)

[Ubuntu SRU Bot]

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/unknown (armhf)
apt/1.8.4 (amd64, armhf, s390x, ppc64el, arm64, i386)
autopkgtest/5.10ubuntu1 (amd64, i386)
gcc-7/7.4.0-8ubuntu1 (armhf)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/disco/update_excuses.html#apt

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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 source package in Disco:
  Fix Committed
Status in apt package in Debian:
  Fix Released

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