El 29/7/24 a las 15:45, Chris Lamb escribiĆ³:
My reproducibility testing framework on my local machine is crusty
enough that testing an arbitrary Git repo is actually quite difficult.
I should probably work on this sometime, but there hasn't been enough
call for me to fix that.
Could you simply go ahead with the upload of smartlist to unstable?
I'll then very happily look back at this bug and make a better
determination on all the questions to mention below.
Ok, I went ahead and did the upload, since it fixes a FTBFS bug
and don't want the autoremoval to happen.
So I change my request to just "please take a look when you can".
In fact, I tried to reproduce this myself yesterday in an arm64 machine
using an armhf chroot, but I did not manage to make the reprotest tool
to work, and I ended up removing the machine (ok, I agree this is vague
and should have asked for help somewhere quoting the exact error message...).
I have identified this commit in the upstream git which has a potential to fix the issue, because it affects lines of code which are close to the ones reported by diffoscope output.
https://github.com/BuGlessRB/procmail/commit/ea5c916fd540b57ba33920f479e6701abad1d88e
But I don't think I will be able to test this theory without some help
to reproduce the problem, everything I need is to know what
variable variation is the one making the build to be different.
Thanks.
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)