On 2016-01-24 Daniel Kahn Gillmor <d...@fifthhorseman.net> wrote:
> On Sat 2016-01-23 16:52:09 -0500, Jérémy Bobbio wrote:
>> While working on the “reproducible builds” effort [1], we have noticed
>> that libgcrypt20 could not be built reproducibly.

>> The attached patch adds support for SOURCE_DATE_EPOCH to set the value
>> of BUILD_TIMESTAMP defined in the configure script. Once applied,
>> libgcrypt20 is nearly reproducible in our current experimental
>> framework—their might be remaining timestamps in the PDF documentation.

> Thanks for fixing this, Lunar.

> fwiw, libgcrypt upstream is the same folks as libgpg-error upstream.  In
> response to concerns about reproducible builds, libgpg-error 1.20
> switched to not embedding the build timestamp at all upstream by
> default.

> Perhaps they'd be open to the same approach for libgcrypt if it were
> proposed.
[...]

Hello,

FYI this had already happened on libgcrypt master branch when this bug
was submitted, Werner has already done this.
http://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git;a=commit;h=a785cc3db0c4e8eb8ebbf784b833a40d2c42ec3e

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

_______________________________________________
Reproducible-builds mailing list
Reproducible-builds@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds

Reply via email to