[Bug 1872902] Re: Upgrade to Focal now removes chrony
Łukasz Zemczak
1872902 at bugs.launchpad.net
Wed May 6 15:32:32 UTC 2020
Hello Christian, or anyone else affected,
Accepted ubuntu-release-upgrader into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-release-upgrader/1:20.04.19 in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
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: ubuntu-release-upgrader (Ubuntu Focal)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-focal
--
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/1872902
Title:
Upgrade to Focal now removes chrony
Status in Release Notes for Ubuntu:
New
Status in apt package in Ubuntu:
Invalid
Status in chrony package in Ubuntu:
Invalid
Status in germinate package in Ubuntu:
New
Status in ntp package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
Fix Released
Status in apt source package in Focal:
Invalid
Status in chrony source package in Focal:
Invalid
Status in germinate source package in Focal:
New
Status in ntp source package in Focal:
Invalid
Status in systemd source package in Focal:
Invalid
Status in ubuntu-release-upgrader source package in Focal:
Fix Committed
Bug description:
Due to changes in systemd for bug 1849156 this issue now happens.
On an upgrade for people that had chrony installed on a do-release upgrade it now will:
Calculating the changes
MarkInstall systemd-timesyncd:amd64 < none -> 245.4-4ubuntu1 @un uN Ib > FU=1
Removing: chrony
MarkDelete chrony:amd64 < 3.2-4ubuntu4.2 -> 3.5-6ubuntu3 @ii umU Ib > FU=0
That isn't what users want, those who had chrony installed would want
to get chrony upgraded and systemd-timesyncd (which now is a separate
pacakge) not installed.
Test Case
---------
1) On a system running Ubuntu 19.10 or Ubuntu 18.04 LTS install the package chrony
2) Run do-release-upgrade with the appropriate switches
3) Observe that chrony is marked for deletion
With the version of dist-upgrader from -proposed (accessed with the -p
switch) chrony is no longer marked for deletion.
Regression Potential
--------------------
Given that Dimitri's change is now ignoring the tasks minimal and standard (which are handled by _keepBaseMetaPkgsInstalled) we should still be cautious and test desktop upgrades and ensure that packages in those tasks are not marked for removal.
Regression Test
---------------
1) Run do-release-upgrade on an Ubuntu 19.10 or Ubuntu 18.04 LTS system
2) Record the list of packages marked for removal
Compare the list of packages marked for removal with the release-
upgrader from -proposed from Focal.
Original Description
--------------------
I'd ask you to revise the dependencies that got changes in systemd 245.4-2ubuntu1 so that on an upgrade from e.g. Bionic chrony stays installed as that was an opt-in chances are quite high people would want to keep it that way.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1872902/+subscriptions
More information about the foundations-bugs
mailing list