** Changed in: livecd-rootfs (Ubuntu Focal)
Assignee: (unassigned) => Łukasz Zemczak (sil2100)
** Changed in: ubuntu-meta (Ubuntu)
Assignee: (unassigned) => Łukasz Zemczak (sil2100)
** Changed in: ubuntu-meta (Ubuntu Focal)
Assignee: (unassigned) => Łukasz Zemczak (sil2100)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1912498
Title:
Preinstall some new essential raspi packages in the official raspi
images
Status in livecd-rootfs package in Ubuntu:
Opinion
Status in ubuntu-meta package in Ubuntu:
Opinion
Status in livecd-rootfs source package in Focal:
In Progress
Status in ubuntu-meta source package in Focal:
In Progress
Bug description:
[Impact]
For 20.04.2, also as part of support for some new Pi variants (CM4,
Pi400), we want to preinstall some new essential packages in our raspi
images such as rpi-eeprom, raspberrypi-userland etc.
This can be done in two possible ways. One is the 'old way', with a
single change to livecd-rootfs adding the new packages. But what we'd
like to propose this time is actually a more proper way, i.e.
introducing device-specific raspi seeds and a raspi meta-package that
would pull in all the needed dependencies. This way is better for the
future, as if we decide we want to add new packages to existing raspi
installations, we can do it easily by modifying the seeds and
rebuilding meta. Currently we have no way like this.
So the current approach includes changes in the following components:
* The ubuntu and platform seeds (git branches)
* ubuntu-meta package (adding ubuntu-server-raspi)
* livecd-rootfs package (installing the raspi-server task)
[Test Case]
After accepting all the package into -proposed (and making sure the git seed
changes are merged), run a raspi arm64 and armhf build. Check if the image
boots. Confirm that the new images have the following seeded: rpi-eeprom,
libraspberrypi-bin, flash-kernel, pi-bluetooth.
Compare manifests between a normal, previous raspi image build and the one
using seeds - check if nothing has been 'dropped'.
Also, check if no other image builds have been affected and still
build correctly, compare image manifests.
[Where problems could occur]
In its current form, as the update touches some livecd-rootfs
auto/config paths, it's possible that a malformed cut-paste broke some
edge case scenario, so it's good if other non-raspi builds are also
checked for correctness. Seed changes are less likely to break
anything, but manifests should be checked in case something got
dropped by accident.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1912498/+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
