[Bug 1872902] Re: Upgrade to Focal now removes chrony

[Brian Murray]

Testing on an Ubuntu 18.04 LTS system with ubuntu-desktop and chrony
installed.

bdmurray at clean-bionic-amd64:/tmp/u-r-u-proposed$ apt-cache policy chrony
chrony:
  Installed: 3.5-6ubuntu6
  Candidate: 3.5-6ubuntu6
  Version table:
 *** 3.5-6ubuntu6 500
        500 http://192.168.10.7/ubuntu focal/main amd64 Packages
        100 /var/lib/dpkg/status
bdmurray at clean-bionic-amd64:/tmp/u-r-u-proposed$ apt-cache policy systemd-timesyncd
systemd-timesyncd:
  Installed: (none)
  Candidate: 245.4-4ubuntu3
  Version table:
     245.4-4ubuntu3 500
        500 http://192.168.10.7/ubuntu focal/main amd64 Packages
bdmurray at clean-bionic-amd64:/tmp/u-r-u-proposed$ head /var/log/dist-upgrade/main.log 
2020-05-06 12:26:14,373 INFO Using config files '['./DistUpgrade.cfg.bionic']'
2020-05-06 12:26:14,373 INFO uname information: 'Linux clean-bionic-amd64 4.15.0-99-generic #100-Ubuntu SMP Wed Apr 22 20:32:56 UTC 2020 x86_64'
2020-05-06 12:26:14,733 INFO apt version: '1.6.12'
2020-05-06 12:26:14,733 INFO python version: '3.6.9 (default, Apr 18 2020, 01:56:04) 
[GCC 8.4.0]'
2020-05-06 12:26:14,737 INFO release-upgrader version '20.04.19' started
2020-05-06 12:26:14,740 INFO locale: 'en_US' 'UTF-8'
2020-05-06 12:26:14,805 DEBUG Using 'DistUpgradeViewText' view
2020-05-06 12:26:14,843 DEBUG enable dpkg --force-overwrite
2020-05-06 12:26:14,870 DEBUG creating statefile: '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'

I had the same results with tasksel as I did with the lxc container
upgrade.

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