On 2016-07-10, Otto Kekäläinen wrote: > Diffs reveal that the issue is expressed in products that stem from > storage/tokudb/*. We are not able to poinpoint what it is exactly, and > we are not even able to reproduce the unreproducible build. > > Here's what we've done in a sid amd64 VM: > > =============== > sudo apt-get update > sudo apt-get install dh-exec libpcre3-dev git-buildpackage > mkdir orig > cd orig > gbp clone --pristine-tar git://git.debian.org/git/pkg-mysql/mariadb-10.0.git > cd .. > export DEB_BUILD_OPTIONS="nocheck" > cp -r orig xxx > cd xxx/mariadb-10.0 > gbp buildpackage > cd ../.. > mv xxx yyy > cp -r orig xxx > cd xxx/mariadb-10.0 > gbp buildpackage > ===============
There are numerous other things such as locale, date, timezone, username, and uid (just for a few examples) that are varied in the reproducible builds infrastructure that you would also need to change between builds: https://tests.reproducible-builds.org/debian/index_variations.html There is a new tool in development, reprotest, to help set up builds with variations: https://packages.debian.org/unstable/main/reprotest I'm not sure how far along it is or if it would be useful to you yet, perhaps others could chime in about that? live well, vagrant
signature.asc
Description: PGP signature
_______________________________________________ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
