Help with a local configuration
vagrant at reproducible-builds.org
Tue Oct 20 01:40:53 UTC 2020
On 2020-10-19, Elías Alejandro wrote:
> Dear all,
> I hope you are well. I have a newbie question about how to configure
> my local box to reproduce bug and finally fix it. I was following
>  but I got a successful message without modifying the source .
> Maybe I need to add another configuration?
> dpkg-deb: building package 'gpick' in '../gpick_0.2.6~rc1-4_amd64.deb'.
> dpkg-deb: building package 'gpick-dbgsym' in
> dpkg-genbuildinfo --build=binary
> dpkg-genchanges --build=binary >../gpick_0.2.6~rc1-4_amd64.changes
> dpkg-genchanges: info: binary-only upload (no source code included)
> dpkg-source --after-build .
> dpkg-buildpackage: info: binary-only upload (no source included)
> Reproducible, even when varying as much as reprotest knows how to! :)
> Reproduction successful
> No differences in ./*.deb
> The last command took 1741.127 seconds.
> If you need any more information please let me know.
It would be helpful to say what command you actually ran. :)
>  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956591
>  https://wiki.debian.org/ReproducibleBuilds/Howto#Testing_procedure
I'll speculate that you were using (since that it is in the instructions
you were following):
$ sudo reprotest --vary=-build_path,domain_host.use_sudo=1 --auto-build XXX.dsc -- schroot unstable-amd64-sbuild
Since the issue in bug #956591 is build_path related, you shouldn't
disable the build path variation (e.g. --vary=-build_path).
From the gpick source directory and with the build-depends installed, a
simple test (without chroots, and disabling some variations that require
more complicated setup):
reprotest --auto-build --store-dir=$(mktemp -d) --min-cpus=10 --vary=-user_group,-domain_host,-fileordering auto -- null
It told me that there were issues when varying the build_path,
consistent with the reported bug.
So a minimal command that should reproduce the issue:
reprotest --vary=-all,+build_path auto -- null
If you look at:
You'll notice that it generally only has reproducibility issues in
"unstable". We don't vary the build path in the testing/bullseye or
stable/buster tests, so that makes sense.
Hope that helps get you to a useful place to debug the issue further!
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 227 bytes
Desc: not available
More information about the rb-general