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

Bug #1925265 reported by Brian Murray
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Status tracked in Kinetic
Impish
Won't Fix
Undecided
Unassigned
Jammy
New
Undecided
Unassigned
Kinetic
Triaged
Undecided
Unassigned

Bug Description

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

bdmurray@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@bdmurray-desktop:~$ cat /var/log/installer/version
ubiquity 21.04.19

tags: added: raspi-image
tags: added: hirsute
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1925265

tags: added: iso-testing
tags: added: rls-ii-incoming
affects: ubuntu-meta (Ubuntu) → ubiquity (Ubuntu)
tags: added: fr-1319
tags: removed: rls-ii-incoming
tags: added: raspi-images
removed: raspi-image
Steve Langasek (vorlon)
Changed in ubiquity (Ubuntu Impish):
status: New → Won't Fix
Revision history for this message
Steve Langasek (vorlon) wrote :

This bug has been open now and listed in the release notes for 3 releases, including the latest LTS, which is far from ideal. Has anyone reproduced it with a current release? If this is a preinstalled image, why is this reported against ubiquity, which is the desktop installer?

I don't have a raspi to test on, but if I mount the jammy image and chroot into it (without booting) I see:

# apt autoremove --purge
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
#

Changed in ubiquity (Ubuntu Kinetic):
status: New → Incomplete
Revision history for this message
Steve Langasek (vorlon) wrote :

ok, figured this out a bit more. oem-config is installed (because you need a first-boot configurator), which is built from ubiquity source. oem-config-firstboot runs:
                apt-get -y purge ubiquity >>/var/log/oem-config.log 2>&1

But does not do an apt autoremove --purge afterwards. So the code needs changed to do this.

Changed in ubiquity (Ubuntu Kinetic):
status: Incomplete → Triaged
summary: - Fresh install of hirsute-preinstalled-desktop-arm64+raspi has packages
+ Fresh install of kinetic-preinstalled-desktop-arm64+raspi has packages
to autoremove
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers