On Sun, 2025-11-09 at 12:33 +0100, Andreas Beckmann wrote: > On 11/9/25 11:58, Adam D. Barratt wrote: > > piuparts is failing while trying to upgrade "dkms-replace-test- > > dkms": > > Can you point me to the full log? I didn't see it on ci.debian.net. > There all tests in stable with "dkms/3.2.2-1~deb13u1 src:dkms from > proposed-updates" looked fine.
Sure - https://piuparts.debian.org/trixie2next/fail/dkms-replace-test-dkms_3.2.2-1~deb13u1.log > > openssl not found, can't generate key and certificate. > > This also sounds a bit suspicious, since the script has > test -x /usr/bin/openssl || \ > apt-get install --no-install-recommends -yq openssl </dev/null > 2>&1 > (in case of older autodep8 versions that didn't generate this > dependency) > > I'll try to reproduce that, but if dkms-replace-test-dkms is the only > test failing, I think this failure can be ignored. Replacement of > modules is a fragile bit and a dkms corner case (and the test is a > very special hack since usually a dkms package would replace a module > from linux-image-* and not a different *-dkms package). Maybe it's > just an installation order variation. The identical package didn't > show anything abnormal in ci tests in sid and forky. Ack, thanks. > If the test failed on a different test environment than > ci.debian.net, is a different autodep8 version being used? I don't think piuparts is running the package's tests here, rather it's trying to install the p-u package in a chroot that already has the version from stable installed. The log for the failing invocation includes: 0m50.7s DEBUG: Starting command: ['chroot', '/srv/piuparts.debian.org/tmp/tmpklakudmn', 'apt-get', '-y', 'install', 'dkms-replace-test-dkms'] Regards, Adam
