[Bug 1775660] Re: ubuntu-release-upgrader should purge obsolete packages, not just remove them
Launchpad Bug Tracker
1775660 at bugs.launchpad.net
Thu Jul 19 12:50:48 UTC 2018
This bug was fixed in the package ubuntu-release-upgrader - 1:18.04.21
---------------
ubuntu-release-upgrader (1:18.04.21) bionic; urgency=medium
* DistUpgradeQuirks.py: when a snap fails to install try the next one
instead of trying to check the return code of the called process which
causes a Traceback. (LP: #1781412)
* data/mirrors.cfg: Update the list of official mirrors.
ubuntu-release-upgrader (1:18.04.20) bionic; urgency=medium
* Purge obsolete packages, if user agrees to remove obsolete
packages. LP: #1775660
* DistUpgradeQuirks.py, DistUpgradeController.py: move inhibiting of
gnome-session idle so that it is called immediately after the upgrade
starts (LP: #1778817), present a dialog notifying that the lock screen has
been disabled (LP: #1174093), and do not reenable the lock screen as it
may fail to work after a release upgrade. (LP: #1780342)
* DistUpgradeQuirks.py: Add in a quirk for upgrading to Bionic that will
check if the system has connectivity to the snap store and replace some
desktop packages with snaps to ensure the system is similar to a fresh
install. (LP: #1780841)
* data/mirrors.cfg: Update the list of official mirrors.
-- Brian Murray <brian at ubuntu.com> Sun, 15 Jul 2018 10:16:16 -0700
** Changed in: ubuntu-release-upgrader (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-release-upgrader in
Ubuntu.
https://bugs.launchpad.net/bugs/1775660
Title:
ubuntu-release-upgrader should purge obsolete packages, not just
remove them
Status in ubuntu-release-upgrader package in Ubuntu:
Fix Released
Status in ubuntu-release-upgrader source package in Bionic:
Fix Released
Bug description:
[Justification]
When an obsolete package leaves conffiles behind, these conffiles can sometimes interact poorly with the system and cause bugs. Since the obsoleted package no longer exists in the targeted release, this can be difficult to resolve by applying fixes to a package. Furthermore, removing-but-not-purging packages on upgrade means that a system which is upgraded will as a rule be inconsistent with a newly-installed system, which should always be considered a bug.
Wherever possible, we should strive to make an upgraded system look
exactly like a newly installed system, to minimize the combinatorics
of configurations that must be supported.
Examples of cases where this has been a problem in practice:
LP: #1770965
LP: #1749199
[Test case]
1. Do an upgrade from xenial with the release ubuntu-release-upgrader. Accept the option to remove obsolete packages.
2. Capture the list of packages that are in state 'rc' afterwards.
3. Do an equivalent upgrade with the -proposed ubuntu-release-upgrader, including removal of obsolete packages.
4. Confirm that the upgrade completes successfully.
5. Capture the list of packages that are in state 'rc' afterwards.
6. Confirm that there are fewer packages in state 'rc' in the second upgrade than the first.
7. Repeat all of the above with an upgrade from artful.
[Regression potential]
As a consequence of this, we will also be running a lot more postrm scripts with the 'purge' option on users desktops, so any bugs in those maintainer scripts will now be apparent as part of a release upgrade where before they were latent.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1775660/+subscriptions
More information about the foundations-bugs
mailing list