Add support for building Tegra images in Jammy

Initial support for building Ubuntu Server live ISO images is ready for review; images boot to GRUB and start the kernel (albeit SD/USB is currently broken in the kernels in jammy)

Added a devel version of the livecd-rootfs changes (almost identical, difference in the components being set); I didn't actually test this branch though

This bug was fixed in the package livecd-rootfs - 2.832

---------------
livecd-rootfs (2.832) lunar; urgency=medium

  * Clean up some remaining references to /dev/mapper.

 -- Steve Langasek <email address hidden> Mon, 17 Apr 2023 18:50:18 -0700

I see Steve merged the livecd-rootfs changes for mantic without a changelog entry, which got released to the archive. I added a changelog entry for the jammy changes.

Hello Loïc, 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.23 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.

All autopkgtests for the newly accepted livecd-rootfs (2.765.23) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

livecd-rootfs/2.765.23 (arm64, s390x)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#livecd-rootfs

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

The livecd-rootfs regression reported here are not actual regressions. s390x passed after a retry and arm64 seems to be caused by networking errors re: the snapstore. Let's proceed with the verification and then release as-is.

Just wanted to confirm I successfully rolled images using livecd-rootfs from proposed for arm64+tegra yesterday!

Hello Loïc, 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.24 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.

Hi Loic,

Sorry, we had to publish another upload on top of the one that was in -proposed. As a result, the testing needs to be performed again. Could you please quickly test the above upload again from -proposed?

P.S. this was superseded by 2.765.24 because of a critical bug. Apologies for the back and forth.

Hi,

I tested livecd-rootfs 2.765.24 by running a test livefs build on Launchpad:
bin/start-livefs-build --livefs=~lool/+livefs/ubuntu/jammy/test --arch=arm64 --metadata subarch='"tegra"' --pocket Proposed

(NB: this is not only taking livecd-rootfs from -proposed but all other packages too)

This succeeded: https://launchpad.net/~lool/+livefs/ubuntu/jammy/test/+build/485936

Many thanks, Loic!

This bug was fixed in the package livecd-rootfs - 2.765.24

---------------
livecd-rootfs (2.765.24) jammy; urgency=medium

  [ Jess Jang ]
  * fix: bind correct apparmor feature for validating snap seed.
    (LP: #2024639)

  [ John Chittum ]
  * fix: 6.2 kernel missing feature. (LP: #2031943)

livecd-rootfs (2.765.23) jammy; urgency=medium

  [ Loïc Minier ]
  * Initial support for NVIDIA Tegra (LP: #2015644).

livecd-rootfs (2.765.22) jammy; urgency=medium

  * Drop use of --removable flag to grub-install from
    live-build/buildd/hooks/02-disk-image-uefi.binary, to match the cloud
    images (7c760864fdcb278ca37396f06f5e3f297428d63d). This fixes
    bootloader updates in the buildd images, but also fixes compatibility
    with using devtmpfs for losetup.

livecd-rootfs (2.765.21) jammy; urgency=medium

  [ jchittum ]
  * add multiple kernel apparmor feature sets for snap preseeding
    (LP: #2015596).

 -- Utkarsh Gupta <email address hidden> Sat, 19 Aug 2023 03:24:34 +0530

The verification of the Stable Release Update for livecd-rootfs has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.