Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2 not libkmod2-udeb

There's a systemd upload for Bionic with this version number already.

I guess that is a larger change that may be intended for post-release,
while this change is needed for release, so d-i builds w/ new kernels.

So, keeping the same number for now, in case this needs to trump that.

Currently building the packages on PPA to verify all three
parts (kmod, systemd, d-i) work correctly with the changes.

Very nice catch @mfo,

I'm sorry to have introduced this issue and I'm glad you found it.

Thanks for sharing. I'm +1 on both uploads to fix the issue.

Apparenlty the systemd package in the upload queue will be reviewed.

For my test packages, @ddstreet told me that a pure no-change rebuild
of systemd would FTBFS on arm64 due to bug #1886197.

So I added that patch to this systemd "almost no-change rebuild" patch.

With the test packages for kmod and systemd in this PPA [1]
I can confirm that udev-udeb now Depends: on libkmod2-udeb.

From the build log:

 Package: udev-udeb
 ...
 Depends: libblkid1-udeb (>= 2.31), libc6-udeb (>= 2.27), libkmod2-udeb, util-linux-udeb

Just uploaded kmod to Bionic.

[1] https://launchpad.net/~mfo/+archive/ubuntu/lp1889297/

Finally, with the kmod change, plus the systemd rebuild,
now d-i builds successfully on all archs in the PPA [1].

[1] https://launchpad.net/~mfo/+archive/ubuntu/lp1889297/

Hello Mauricio, or anyone else affected,

Accepted kmod into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/kmod/24-1ubuntu3.5 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. 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.

Verification done on bionic-proposed.

The shlibs file of libkmod2 contains the udeb line:

    $ pull-lp-debs libkmod2 bionic
    $ dpkg-deb --control libkmod2_24-1ubuntu3.5_amd64.deb dir
    $ cat dir/shlibs
    libkmod 2 libkmod2
    udeb: libkmod 2 libkmod2-udeb

Then building systemd in a PPA with proposed enabled
does result in udev-udeb depending on libkmod2-udeb:

    Build log:
    ...
    Get:51 http://ftpmaster.internal/ubuntu bionic-proposed/main amd64 libkmod2 amd64 24-1ubuntu3.5 [40.2 kB]
    ...
     Package: udev-udeb
     ...
     Depends: libblkid1-udeb (>= 2.31), libc6-udeb (>= 2.27), libkmod2-udeb, util-linux-udeb
    ...

All autopkgtests for the newly accepted kmod (24-1ubuntu3.5) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/237-3ubuntu10.41 (i386)

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/bionic/update_excuses.html#kmod

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

Thank you!

The failing autopkgtest is in the 'upstream' tests
(search for 'TEST RUN: Job-related tests' twice.)

It's very probably unrelated: apparently the testsuite.service
ended unexpectedly, due to a SIGCHLD because the sleep.service
(the child iiuic) got a SIGTERM unexpectedly too, and finished.
According to the systemd journal in the artifacts.

Just trigerred a re-run since that has no relation with kmod.

That cleared up the autopkgtest regression.

systemd [bionic/i386]
Version Triggers Date Duration Requester Result
237-3ubuntu10.41 kmod/24-1ubuntu3.5 2020-07-29 23:55:56 UTC 1h 03m 06s mfo pass ...

The systemd upload has been accepted into bionic-proposed,
and udev-udeb depends on likmod2-udeb. All good.

 Package: udev-udeb
 Source: systemd
 Version: 237-3ubuntu10.42
 ...
 Depends: libblkid1-udeb (>= 2.31), libc6-udeb (>= 2.27), libkmod2-udeb, util-linux-udeb

The existing d-i upload to bump the master/HWE kernels (version 20101020ubuntu543.16)
should pick it up, and now build just fine for 18.04.5.

cheers!

Hi @mhodson,

Could you please clarify your change 'no longer affects: kmod'?

This bug is actually/fixed in the kmod source package. Thanks!

This bug was fixed in the package kmod - 24-1ubuntu3.5

---------------
kmod (24-1ubuntu3.5) bionic; urgency=medium

  * Re-introduce --add-udeb=libkmod2-udeb to dh_makeshlibs.
    Fixes d-i FTBFS due to udev-udeb depending on libkmod2
    instead of libkmod2-udeb. (LP: #1889297)

 -- Mauricio Faria de Oliveira <email address hidden> Tue, 28 Jul 2020 11:46:39 -0300

The verification of the Stable Release Update for kmod 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.

Marking systemd as Fix Released as a new version/build that incorporates this kmod fix has been released (version 237-3ubuntu10.42)