[Bug 1872902] Autopkgtest regression report (ubuntu-release-upgrader/1:20.04.19)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted ubuntu-release-upgrader (1:20.04.19) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

update-manager/1:20.04.10 (armhf)
update-notifier/3.192.30 (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/focal/update_excuses.html#ubuntu-release-upgrader

[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/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