[systemd-devel] Testing specific systemd (udev) commit on Fedora 34

Ian Pilcher arequipeno at gmail.com
Mon Jul 12 14:20:17 UTC 2021


I have hit what appears to be a race condition in udev that causes very
slow booting on systems with a "large" number of disks or block devices.

I have an idea about which commit triggered the issue, so I'd like to
build the previous commit (a59b0a9f768f6e27b25f4f1bab6de08842e78d74) as
a test RPM.

Unfortunately, trying to rebuild the F34 SRPM with that commit is giving 
me an error:

  meson.build:1421:16: ERROR: Problem encountered: oomd is not available 
in release mode (yet)

A quick scan through the SPEC file doesn't show an obvious way to not
build systemd-oomd.

I next attempted to build the F33 SRPM for F34, i.e.

  mock -r fedora-33-x86_64 systemd-246.13-1.fc33.src.rpm

That fails with:

  ninja: build stopped: subcommand failed.
  Found runner: ['/usr/bin/ninja']

Can anyone think of an approach that will allow me to build this
particular commit for Fedora 34?  (It doesn't necessarily have to be an
RPM; I just need to be able to build and install it.)

Thanks!

-- 
========================================================================
                  In Soviet Russia, Google searches you!
========================================================================



More information about the systemd-devel mailing list