Re: [systemd-devel] Testing specific systemd (udev) commit on Fedora 34
On 7/12/21 9:20 AM, Ian Pilcher wrote: 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. I managed to figure this out. Not sure why I missed it before, but setting '-Doomd=false' in CONFIGURE_OPTS allows the RPM to build. -- In Soviet Russia, Google searches you! ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Testing specific systemd (udev) commit on Fedora 34
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! ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
