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

[Robie Basak]

Hello Brian, or anyone else affected,

Accepted ubiquity into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/ubiquity/22.04.20 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-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. 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: ubiquity (Ubuntu Jammy)
       Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-jammy

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