[Bug 1983521] Re: [SRU] Manually blacklist DKMS modules for Ubuntu Studio builds

[Brian Murray]

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.10 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.

** Changed in: livecd-rootfs (Ubuntu Jammy)
       Status: Fix Released => Fix Committed

** Tags added: verification-needed verification-needed-jammy

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1983521

Title:
  [SRU] Manually blacklist DKMS modules for Ubuntu Studio builds

Status in livecd-rootfs package in Ubuntu:
  Invalid
Status in livecd-rootfs source package in Jammy:
  Fix Committed
Status in livecd-rootfs source package in Kinetic:
  Invalid

Bug description:
  [Impact and Rationale]

  Ubuntu Studio 22.04 is currently uninstallable on systems with Secure
  Boot enabled. This is due to the inclusion of two packages,
  v4l2loopback-dkms and v4l2loopback-utils. See Ubuntu bug 1983136 and
  https://git.launchpad.net/~ubuntustudio-dev/ubuntu-
  seeds/+git/ubuntustudio/commit/?id=dd556f0bc548b17f3126732500a1a3c194c9b3d8
  for more detailed information.

  In livecd-rootfs, if a package is removed from a seed post-release,
  newer ISOs still include that package because it was part of the task
  at release-time. For Ubuntu Studio 22.04.1, we need to remove those
  packages during the creation of the squashfs so they are not included
  by default. This bug does not affect 22.10+.

  This is done with an install hook, rather than simply blacklisting the
  package from being installed. The change is modeled after this recent
  commit by Steve Langasek: https://git.launchpad.net/livecd-
  rootfs/commit/?id=941cd3c64aab7b2ada33399d9b08b8a785d3d957

  This is being split into a separate bug to fast-track the change. Only
  a respin of Ubuntu Studio should be required.

  [Test Case]

  I have tested these changes locally prior to uploading them, by
  running the following commands in the live-build directory:

  $ export PROJECT="ubuntustudio-dvd" && export ARCH="amd64" && export SUITE="jammy"
  $ env PROJECT=$PROJECT SUBPROJECT=$SUBPROJECT ARCH=$ARCH SUITE=$SUITE lb config
  $ sudo env PROJECT=$PROJECT SUBPROJECT=$SUBPROJECT ARCH=$ARCH lb build
  $ sudo env PROJECT=$PROJECT SUBPROJECT=$SUBPROJECT ARCH=$ARCH lb binary
  $ mkdir -pv ~/ubuntu/iso && sudo mount -t iso9660 -o loop /PATH/TO/STUDIO/JAMMY/DAILY.iso ~/ubuntu/iso
  $ mkdir -pv ~/ubuntu/iso_custom && tar cf - ~/ubuntu/iso | (cd ~/ubuntu/iso_custom; tar xfp -)

  After the ISO is completely done, you should be able to boot it on a
  Secure Boot system once again. Just a basic boot and install smoke
  test on that particular hardware type.

  [Where problems could occur]

  If Bash or apt itself is SRUed, or if the project name for Ubuntu
  Studio changes in livecd-rootfs, problems may occur with unexpected
  behavior. Otherwise, the package may find another way to sneak itself
  onto the ISO in the future.

  The code block format can be seen all over that part of the file, so
  it's not much of a hack. In fact, this code block is safer, because it
  ensures that the hook is marked as executable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1983521/+subscriptions