[Touch-packages] [Bug 2016285] Re: Redundant creation of oem user in rpi desktop images
This bug was fixed in the package livecd-rootfs - 2.828 --- livecd-rootfs (2.828) lunar; urgency=medium * 099-ubuntu-image-customization.chroot: Remove redundant creation of oem user and oem-config-prepare (LP: #2016285) -- Dave Jones Fri, 14 Apr 2023 09:48:31 +0100 ** Changed in: livecd-rootfs (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2016285 Title: Redundant creation of oem user in rpi desktop images Status in livecd-rootfs package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: There are two (semi-related) issues which are currently preventing the creation of Ubuntu desktop images for the Raspberry Pi: The first is that livecd-rootfs is erroneously trying to create the oem user (and run oem-config-prepare) twice in live- build/ubuntu/hooks/099-ubuntu-image-customization.chroot. The second is that the ubuntu-raspi-settings-desktop package is attempt to create the oem user and run oem-config-prepare in its postinst. This is the wrong place to accomplish this as there's no guarantee that oem-config-prepare is installed at the time that ubuntu-raspi-settings-desktop is installed. It cannot be a dependency because oem-config is uninstalled after first boot. It's likely that the *correct* place to do this configuration is in neither of these places, but in oem-config's postinst (along with some check that it's being installed in an image that's never been booted, e.g. check for the existence of some sentinel created on first boot ... maybe /var/log/boot.log or something). Still, that fix can wait until it's not release week! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2016285/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2016285] Re: Redundant creation of oem user in rpi desktop images
This bug was fixed in the package ubuntu-settings - 23.04.5 --- ubuntu-settings (23.04.5) lunar; urgency=medium * ubuntu-raspi-settings-desktop: Don't attempt to prepare oem-config in postinst; there's no guarantee oem-config is installed yet and it cannot be a dependency as it's uninstalled after first boot (LP: #2016285) * ubuntu-raspi-settings-desktop: Don't attempt to expand an already expanded rootfs (LP: #2016286) -- Dave Jones Fri, 14 Apr 2023 11:13:13 +0100 ** Changed in: ubuntu-settings (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2016285 Title: Redundant creation of oem user in rpi desktop images Status in livecd-rootfs package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: There are two (semi-related) issues which are currently preventing the creation of Ubuntu desktop images for the Raspberry Pi: The first is that livecd-rootfs is erroneously trying to create the oem user (and run oem-config-prepare) twice in live- build/ubuntu/hooks/099-ubuntu-image-customization.chroot. The second is that the ubuntu-raspi-settings-desktop package is attempt to create the oem user and run oem-config-prepare in its postinst. This is the wrong place to accomplish this as there's no guarantee that oem-config-prepare is installed at the time that ubuntu-raspi-settings-desktop is installed. It cannot be a dependency because oem-config is uninstalled after first boot. It's likely that the *correct* place to do this configuration is in neither of these places, but in oem-config's postinst (along with some check that it's being installed in an image that's never been booted, e.g. check for the existence of some sentinel created on first boot ... maybe /var/log/boot.log or something). Still, that fix can wait until it's not release week! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2016285/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2016285] Re: Redundant creation of oem user in rpi desktop images
Setting to critical as this currently prevents the creation of the ubuntu rpi desktop images. ** Changed in: livecd-rootfs (Ubuntu) Importance: Undecided => Critical ** Changed in: ubuntu-settings (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2016285 Title: Redundant creation of oem user in rpi desktop images Status in livecd-rootfs package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: New Bug description: There are two (semi-related) issues which are currently preventing the creation of Ubuntu desktop images for the Raspberry Pi: The first is that livecd-rootfs is erroneously trying to create the oem user (and run oem-config-prepare) twice in live- build/ubuntu/hooks/099-ubuntu-image-customization.chroot. The second is that the ubuntu-raspi-settings-desktop package is attempt to create the oem user and run oem-config-prepare in its postinst. This is the wrong place to accomplish this as there's no guarantee that oem-config-prepare is installed at the time that ubuntu-raspi-settings-desktop is installed. It cannot be a dependency because oem-config is uninstalled after first boot. It's likely that the *correct* place to do this configuration is in neither of these places, but in oem-config's postinst (along with some check that it's being installed in an image that's never been booted, e.g. check for the existence of some sentinel created on first boot ... maybe /var/log/boot.log or something). Still, that fix can wait until it's not release week! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2016285/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2016285] Re: Redundant creation of oem user in rpi desktop images
** Merge proposal linked: https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/441072 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2016285 Title: Redundant creation of oem user in rpi desktop images Status in livecd-rootfs package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: New Bug description: There are two (semi-related) issues which are currently preventing the creation of Ubuntu desktop images for the Raspberry Pi: The first is that livecd-rootfs is erroneously trying to create the oem user (and run oem-config-prepare) twice in live- build/ubuntu/hooks/099-ubuntu-image-customization.chroot. The second is that the ubuntu-raspi-settings-desktop package is attempt to create the oem user and run oem-config-prepare in its postinst. This is the wrong place to accomplish this as there's no guarantee that oem-config-prepare is installed at the time that ubuntu-raspi-settings-desktop is installed. It cannot be a dependency because oem-config is uninstalled after first boot. It's likely that the *correct* place to do this configuration is in neither of these places, but in oem-config's postinst (along with some check that it's being installed in an image that's never been booted, e.g. check for the existence of some sentinel created on first boot ... maybe /var/log/boot.log or something). Still, that fix can wait until it's not release week! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2016285/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
