On Thu 05 Sep 2024 07:51:24 PM +02, Santiago Vila <sanv...@debian.org> wrote:
Hello. Before declaring this unreproducible, some things to take in account:* I tried several times. It always fail. This is not random. * It also fails here: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/nauty.html
I agree now. :) My mistake was that I was working on packaging the new upstream release (2.8.9) and wasn't having this problem. When I tried building the version currently in unstable (2.8.8), the build failed right away with the bug you reported. So the good news is that upstream has already fixed the bug and it will be in Debian soon! The 2.8.9 package is currently in the NEW queue due to a library package name change. It will appear in experimental first so I can request a transition slot.
* I included this paragraph in my bug report:If you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible.
Indeed you did!
but for some reason it has been ignored.
There was no good reason -- I just didn't read the bug report carefully.
So please try again. My theory is that your chroot is outdated and you are most probably still using autoconf 2.71. If you compare your build log with the one I provided, you can check that. It's autoconf 2.72 and later what triggers this error, and there are other packages affected in a very similar way: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080110 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080146 My offer for a VM to reproduce this still holds (but I think this is not the kind of weird bug requiring help to be reproduced, only an updated chroot of unstable). I'm removing the moreinfo and unreproducible tags, as I believe they do not really apply here.
You're absolutely correct! Thank you for your careful explanation and patience. :) Doug
signature.asc
Description: PGP signature
