On 11/9/25 12:42, Adam D. Barratt wrote:
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
Already your initial report stated piuparts, but I only thought about autopkgtests ... these should be working OK, actually I didn't think about trying these packages in piuparts. The dkms-replace-test-dkms package is most likely not working in upgrade scenarios, it was never designed for that (or even tested in such a scenario) and this failure shows that it actually doesn't. Probably the same happens in sid/testing. The autopkgtests only cover installation and removal, not upgrades. In real instances of such module replacement one will not have two dkms modules stepping on each others feet but a dkms module and a shipped kernel module which will cause a bit less confusion on upgrades. So, yes, please ignore this failure. Maybe that test package (which is not supposed to be installed on any users system) should be blacklisted in piuparts for upgrade tests (failing by design).
Andreas