buildd/h/02-disk-image-uefi.binary fails on jammy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
livecd-rootfs (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Committed
|
Undecided
|
Unassigned |
Bug Description
[ impact ]
* In replacing kpartx with losetup, earlier this year, grub-install
(grub-probe) started failing for bootable uefi buildd images on jammy.
This failure started around 2024-01-14.
* uefi buildd images don't build on jammy. Later suites have a different code
path (in grub-core/
* udev was getting installed in later hooks. Adding it earlier isn't
altering the resulting artifact.
[ test plan ]
* live-build with --series=jammy --project ubuntu-base --subproject buildd --image-format ext4 --image-target all
* uefi image should build and be bootable from qemu
[ where problems could occur ]
* affected hook is specific to buildd
* considering udev is now installed in an earlier buildd hook, it could
technically interfere with later build steps. Recent additions of flock
address some of the udev races but this could surface more.
Related branches
- Gauthier Jolly (community): Approve
- Utkarsh Gupta: Approve
- Michael Hudson-Doyle: Approve
-
Diff: 38 lines (+10/-3)2 files modifieddebian/changelog (+7/-0)
live-build/buildd/hooks/02-disk-image-uefi.binary (+3/-3)
- Canonical Foundations Team: Pending requested
-
Diff: 1974 lines (+1042/-17) (has conflicts)76 files modifieddebian/changelog (+314/-3)
debian/control (+3/-0)
live-build/apparmor/5.19/capability (+1/-0)
live-build/apparmor/5.19/caps/mask (+1/-0)
live-build/apparmor/5.19/dbus/mask (+1/-0)
live-build/apparmor/5.19/domain/attach_conditions/xattr (+1/-0)
live-build/apparmor/5.19/domain/change_hat (+1/-0)
live-build/apparmor/5.19/domain/change_hatv (+1/-0)
live-build/apparmor/5.19/domain/change_onexec (+1/-0)
live-build/apparmor/5.19/domain/change_profile (+1/-0)
live-build/apparmor/5.19/domain/computed_longest_left (+1/-0)
live-build/apparmor/5.19/domain/fix_binfmt_elf_mmap (+1/-0)
live-build/apparmor/5.19/domain/post_nnp_subset (+1/-0)
live-build/apparmor/5.19/domain/stack (+1/-0)
live-build/apparmor/5.19/domain/version (+1/-0)
live-build/apparmor/5.19/file/mask (+1/-0)
live-build/apparmor/5.19/ipc/posix_mqueue (+1/-0)
live-build/apparmor/5.19/mount/mask (+1/-0)
live-build/apparmor/5.19/namespaces/pivot_root (+1/-0)
live-build/apparmor/5.19/namespaces/profile (+1/-0)
live-build/apparmor/5.19/network/af_mask (+1/-0)
live-build/apparmor/5.19/network/af_unix (+1/-0)
live-build/apparmor/5.19/network_v8/af_mask (+1/-0)
live-build/apparmor/5.19/policy/set_load (+1/-0)
live-build/apparmor/5.19/policy/versions/v5 (+1/-0)
live-build/apparmor/5.19/policy/versions/v6 (+1/-0)
live-build/apparmor/5.19/policy/versions/v7 (+1/-0)
live-build/apparmor/5.19/policy/versions/v8 (+1/-0)
live-build/apparmor/5.19/ptrace/mask (+1/-0)
live-build/apparmor/5.19/query/label/data (+1/-0)
live-build/apparmor/5.19/query/label/multi_transaction (+1/-0)
live-build/apparmor/5.19/query/label/perms (+1/-0)
live-build/apparmor/5.19/rlimit/mask (+1/-0)
live-build/apparmor/5.19/signal/mask (+1/-0)
live-build/apparmor/6.2/capability (+1/-0)
live-build/apparmor/6.2/caps/mask (+1/-0)
live-build/apparmor/6.2/dbus/mask (+1/-0)
live-build/apparmor/6.2/domain/attach_conditions/xattr (+1/-0)
live-build/apparmor/6.2/domain/change_hat (+1/-0)
live-build/apparmor/6.2/domain/change_hatv (+1/-0)
live-build/apparmor/6.2/domain/change_onexec (+1/-0)
live-build/apparmor/6.2/domain/change_profile (+1/-0)
live-build/apparmor/6.2/domain/computed_longest_left (+1/-0)
live-build/apparmor/6.2/domain/fix_binfmt_elf_mmap (+1/-0)
live-build/apparmor/6.2/domain/post_nnp_subset (+1/-0)
live-build/apparmor/6.2/domain/stack (+1/-0)
live-build/apparmor/6.2/domain/version (+1/-0)
live-build/apparmor/6.2/file/mask (+1/-0)
live-build/apparmor/6.2/ipc/posix_mqueue (+1/-0)
live-build/apparmor/6.2/mount/mask (+1/-0)
live-build/apparmor/6.2/namespaces/pivot_root (+1/-0)
live-build/apparmor/6.2/namespaces/profile (+1/-0)
live-build/apparmor/6.2/network/af_mask (+1/-0)
live-build/apparmor/6.2/network/af_unix (+1/-0)
live-build/apparmor/6.2/network_v8/af_mask (+1/-0)
live-build/apparmor/6.2/policy/set_load (+1/-0)
live-build/apparmor/6.2/policy/versions/v5 (+1/-0)
live-build/apparmor/6.2/policy/versions/v6 (+1/-0)
live-build/apparmor/6.2/policy/versions/v7 (+1/-0)
live-build/apparmor/6.2/policy/versions/v8 (+1/-0)
live-build/apparmor/6.2/ptrace/mask (+1/-0)
live-build/apparmor/6.2/query/label/data (+1/-0)
live-build/apparmor/6.2/query/label/multi_transaction (+1/-0)
live-build/apparmor/6.2/query/label/perms (+1/-0)
live-build/apparmor/6.2/rlimit/mask (+1/-0)
live-build/apparmor/6.2/signal/mask (+1/-0)
live-build/auto/build (+13/-0)
live-build/auto/config (+198/-0)
live-build/buildd/hooks/02-disk-image-uefi.binary (+22/-14)
live-build/functions (+68/-0)
live-build/lb_binary_layered (+4/-0)
live-build/ubuntu-cpc/hooks.d/base/disk-image-uefi.binary (+313/-0)
live-build/ubuntu-cpc/hooks.d/base/riscv64/grub/cmdline.cfg (+4/-0)
live-build/ubuntu-cpc/hooks.d/chroot/999-cpc-fixes.chroot (+32/-0)
live-build/ubuntu-server/hooks/01-unminimize.chroot_early (+4/-0)
live-build/ubuntu-server/hooks/03-kernel-metapkg.chroot_early (+3/-0)
description: | updated |
Changed in livecd-rootfs (Ubuntu Jammy): | |
status: | New → Confirmed |
Changed in livecd-rootfs (Ubuntu): | |
status: | Confirmed → Fix Released |
Hello Simon, or anyone else affected,
Accepted livecd-rootfs into jammy-proposed. The package will build now and be available at https:/ /launchpad. net/ubuntu/ +source/ livecd- rootfs/ 2.765.44 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/ PerformingSRUVe rification . 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.