On Sun, Aug 22, 2021 at 03:03:14PM +0200, Baptiste Beauplat wrote: > While trying to debug > https://salsa.debian.org/salsa-ci-team/pipeline/-/issues/191, I found > out that the kernel variation makes ldconfig abort with the following > message: "FATAL: Kernel too old"
> This behavour is partially documented in the manpage under: > > ``` > Kernel > ------ > > The "kernel" variation is currently not working for RPM based packages. > While building with this variation enabled, the tool > `/usr/lib/rpm/redhat/brp-ldconfig` > compains about `FATAL: kernel too old` and aborts the build. > ``` > > However all version of ldconfig (at least since 2017) require a kernel > 3.2, not just the RPM ldconfig. > > I think the documentation should be updated to warn users about ldconfig > not working in all cases. What would you say about this patch: |--- a/README.rst |+++ b/README.rst |@@ -378,9 +378,9 @@ mechanism to vary the system time. | Kernel | ------ | |-The "kernel" variation is currently not working for RPM based packages. While |-building with this variation enabled, the tool `/usr/lib/rpm/redhat/brp-ldconfig` |-compains about `FATAL: kernel too old` and aborts the build. |+The "kernel" variation is currently not working for RPM based packages and other |+build process requiring `ldconfig`. While building with this variation enabled, |+`ldconfig` complains about `FATAL: kernel too old` and aborts the build. | | Avoid sudo(1) password prompts | ============================== Besides potentially better identifying which versions of ldconfig are effectively broken, I don't think we could do much else. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature