Requsting help: reproducibility regressions in pwgen and e2fsprogs?
Mattia Rizzolo
mattia at debian.org
Thu Aug 10 09:30:19 UTC 2017
On Wed, Aug 09, 2017 at 11:36:55PM -0400, Theodore Ts'o wrote:
> Yet both seem to be broken, and with pwgen, it looks like it's being
> the debugging pathname has somehow leaked into the ELF / debugging
> information:
That's actually our fault, sorry if it leaked off to you. In unstable
we are experimenting with build path variation, and that causes
unreproducible results unless a patched gcc (coupled with a patched
dpkg) is in use. We aren't setting any block, so every time a new gcc
is uploaded to the regular archive it overwrites our version…
I've scheduled both pwgen and e2fsprogs for rebuild now, thye should
turn sunny soon.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/reproducible-builds/attachments/20170810/67eb3951/attachment.sig>
More information about the Reproducible-builds
mailing list