[Bug 1925265] Re: Fresh install of kinetic-preinstalled-desktop-arm64+raspi has packages to autoremove

[Launchpad Bug Tracker]

This bug was fixed in the package ubiquity - 22.04.20

---------------
ubiquity (22.04.20) jammy; urgency=medium

  [ Steve Langasek ]
  * Whenever removing packages, use apt-get autoremove --purge instead of
    apt-get purge so that no-longer-used dependencies are removed together
    with the package in question, and we do not leave behind any packages
    that will be reported as autoremovable later.  LP: #1925265.
  * bin/oem-config-remove-gtk uses aptdaemon to remove packages, not
    apt-get.  Set the flag to autoremove dependencies here as well.

  [ Nick Rosbrook ]
  * tests: modify test_city_entry to adapt to tzdata update (LP: #2022965)

  [ Shih-Yuan Lee (FourDollars) ]
  * Use dpkg-divert /sbin/start-stop-daemon unconditionally instead of just
    renaming it conditionally.  (LP: #1978931)

 -- Steve Langasek <steve.langasek at ubuntu.com>  Mon, 05 Jun 2023
14:36:01 -0700

** Changed in: ubiquity (Ubuntu Jammy)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1925265

Title:
  Fresh install of kinetic-preinstalled-desktop-arm64+raspi has packages
  to autoremove

Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubiquity source package in Impish:
  Won't Fix
Status in ubiquity source package in Jammy:
  Fix Released
Status in ubiquity source package in Kinetic:
  Won't Fix
Status in ubiquity source package in Lunar:
  Won't Fix

Bug description:
  [Impact]

  Immediately after installing hirsute-preinstalled-desktop-arm64+raspi
  on a Raspberry Pi I noticed that there were packages available for
  autoremoval.

  bdmurray at bdmurray-desktop:~$ sudo apt autoremove
  [sudo] password for bdmurray:
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages will be REMOVED:
    cryptsetup-bin dctrl-tools dmeventd dmraid dpkg-repack efibootmgr gir1.2-timezonemap-1.0 gir1.2-xkl-1.0 grub-common grub-efi-arm64
    grub-efi-arm64-bin grub-efi-arm64-signed grub2-common kpartx kpartx-boot libdebian-installer4 libdevmapper-event1.02.1
    libdmraid1.0.0.rc16 liblvm2cmd2.03 libtimezonemap-data libtimezonemap1 lvm2 os-prober python3-icu python3-pam rdate
    thin-provisioning-tools
  0 upgraded, 0 newly installed, 27 to remove and 0 not upgraded.
  After this operation, 45.5 MB disk space will be freed.
  Do you want to continue? [Y/n] n
  Abort.

  It seems to me the installation process should run an autoremove at
  the end.

  bdmurray at bdmurray-desktop:~$ cat /var/log/installer/version
  ubiquity 21.04.19

  [Test case]
  * Wait for a daily jammy preinstalled image to be built after ubiquity is accepted and built.
  * Install using the image.
  * Confirm that after installation, 'sudo apt autoremove' does not offer to remove any additional packages.

  [Where things could go wrong]
  Because we are now removing additional packages from the system that previously were left installed at the end of oem-config, it is possible that for some installations using oem-config - but *not* the raspi preinstalled images - that some of the packages being removed are needed to access the disk and that removal will break the boot.  The correct fix in such a case is to make sure the relevant packages are marked manually installed as part of the installation process; we already do this, but because of this bug with removals it could be that this isn't being done correctly in all cases which would only be discovered after fixing this bug.  We should handle that by making any necessary follow-up fixes to ubiquity.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1925265/+subscriptions