Hi Michael, * Michael Biebl <[email protected]> [2026-08-26 18:40]:
Am 26.08.26 um 11:37 schrieb Jochen Sprickerhof:* Michael Biebl <[email protected]> [2026-08-26 11:34]:Tbh, I'm tempted to simply disable 'make check' when it is run as part of a reproducible build. Is there a reliable way to detect this from within debian/rules?No and there will not be. We try to reproduce the exact build environment, so I would be really interested why it fails only on some computers. Do you have any hint how to debug this?Ok. To not waste your or my time, I will disable this particular test as I did in the past [0]. I re-enabled it in [1].Since I haven't found a way to reproduce the issue, that's the best I can do atm.
Thanks though the new -4 again failed in a different test: https://reproduce.debian.net/amd64/api/v1/builds/284111/logI did some more testing and also was not able to reproduce this except for reproduce.d.n hosts. I even ran a VM on those hosts to test if it was host specific but it build just fine. I also tried increasing the inotify limits in the kernel on the rdn host but still found the same test failure. So my best guess is that some configuration on the rdn system breaks rsyslog but I have no idea which. The good thing is that there is a plan to move the rdn builds to tmpfs which would fix the problem. So I propose to ask for an excuse from the release team and let rsyslog fail on rdn for now. I will ask for this now and you can revert the patch.
Cheers Jochen
signature.asc
Description: PGP signature
