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 , 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
> Perhaps they'd be open to the same approach for libgcrypt if it were
FYI this had already happened on libgcrypt master branch when this bug
was submitted, Werner has already done this.
`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