Your message dated Wed, 24 Sep 2014 21:21:48 +0000
with message-id <[email protected]>
and subject line Bug#762397: fixed in libgpg-error 1.16-2
has caused the Debian Bug report #762397,
regarding libgpg-error: please do not capture the current time during the build 
process
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
762397: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762397
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libgpg-error
Version: 1.16-1
Severity: wishlist
Tags: patch
User: [email protected]
Usertag: timestamps

Hi!

As part of the “reproducible builds” effort [1], it was detected that
libgpg-error could not be built reproducibly.

The build process capture the time of the build. This piece of
information is not really helpful to anyone and prevents the build
process from being deterministic.

The attached patch will instead use the time of the latest
debian/changelog entry. Once applied, libgpg-error can be built
reproducibly! :)

 [1]: https://wiki.debian.org/ReproducibleBuilds

-- 
Lunar                                .''`. 
[email protected]                    : :Ⓐ  :  # apt-get install anarchism
                                    `. `'` 
                                      `-   
diff -Nru libgpg-error-1.16/debian/changelog libgpg-error-1.16/debian/changelog
--- libgpg-error-1.16/debian/changelog	2014-09-18 16:57:20.000000000 +0200
+++ libgpg-error-1.16/debian/changelog	2014-09-21 22:37:47.000000000 +0200
@@ -1,3 +1,10 @@
+libgpg-error (1.16-1.0~reproducible1) UNRELEASED; urgency=low
+
+  * Use latest entry of debian/changelog as build timestamp in order
+    to get reproducible builds.
+
+ -- Jérémy Bobbio <[email protected]>  Sun, 21 Sep 2014 20:37:15 +0000
+
 libgpg-error (1.16-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru libgpg-error-1.16/debian/patches/series libgpg-error-1.16/debian/patches/series
--- libgpg-error-1.16/debian/patches/series	1970-01-01 01:00:00.000000000 +0100
+++ libgpg-error-1.16/debian/patches/series	2014-09-21 22:36:52.000000000 +0200
@@ -0,0 +1 @@
+use-debian-changelog-date-as-timestamp.diff
diff -Nru libgpg-error-1.16/debian/patches/use-debian-changelog-date-as-timestamp.diff libgpg-error-1.16/debian/patches/use-debian-changelog-date-as-timestamp.diff
--- libgpg-error-1.16/debian/patches/use-debian-changelog-date-as-timestamp.diff	1970-01-01 01:00:00.000000000 +0100
+++ libgpg-error-1.16/debian/patches/use-debian-changelog-date-as-timestamp.diff	2014-09-21 22:36:29.000000000 +0200
@@ -0,0 +1,17 @@
+Description: Use latest entry of debian/changelog as build timestamp
+ In order to make the build reproducible, we use the time of the latest
+ entry in debian/changelog as the build timestamp.
+Author: Jérémy Bobbio <[email protected]>
+Last-Update: 2014-09-21
+
+--- libgpg-error-1.16.orig/configure.ac
++++ libgpg-error-1.16/configure.ac
+@@ -484,7 +484,7 @@ changequote([,])dnl
+ BUILD_FILEVERSION="${BUILD_FILEVERSION}0,mym4_revision_dec"
+ AC_SUBST(BUILD_FILEVERSION)
+ 
+-BUILD_TIMESTAMP=`date -u +%Y-%m-%dT%H:%M+0000 2>/dev/null || date`
++BUILD_TIMESTAMP=`date --date="$(dpkg-parsechangelog -SDate)" -u +%Y-%m-%dT%H:%M+0000 2>/dev/null || date`
+ AC_SUBST(BUILD_TIMESTAMP)
+ AC_DEFINE_UNQUOTED(BUILD_TIMESTAMP, "$BUILD_TIMESTAMP",
+                    [The time this package was configured for a build])

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message ---
Source: libgpg-error
Source-Version: 1.16-2

We believe that the bug you reported is fixed in the latest version of
libgpg-error, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor <[email protected]> (supplier of updated libgpg-error 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 22 Sep 2014 15:52:35 -0400
Source: libgpg-error
Binary: libgpg-error-dev libgpg-error0 libgpg-error0-udeb
Architecture: source
Version: 1.16-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GnuPG Maintainers <[email protected]>
Changed-By: Daniel Kahn Gillmor <[email protected]>
Description:
 libgpg-error-dev - library for common error values and messages in GnuPG 
components
 libgpg-error0 - library for common error values and messages in GnuPG 
components
 libgpg-error0-udeb - library for common error values and messages in GnuPG 
components (udeb)
Closes: 762322 762397
Changes:
 libgpg-error (1.16-2) unstable; urgency=medium
 .
   * added headers for powerpc64el and sparc64 (Closes: #762322)
   * fix build timestamp for reproducibility (Closes: #762397)
Checksums-Sha1:
 6bd5bb47e3c633cbcc2ab7a2648ad44ba34525e7 2344 libgpg-error_1.16-2.dsc
 09a57bef2f457b5986cf7cccfae122473676e749 10772 
libgpg-error_1.16-2.debian.tar.xz
Checksums-Sha256:
 1cd5eb8341236b487ff9220ac86bb95eb2d793ada4e5233ce8a08b9ed6b77a50 2344 
libgpg-error_1.16-2.dsc
 fda947924c812068ff82cf35a359f9ee85b67c6c091273fd463c4d6a62d66031 10772 
libgpg-error_1.16-2.debian.tar.xz
Files:
 fdf8769511cb5c52aa91f63429929677 2344 libs standard libgpg-error_1.16-2.dsc
 37260d88634183c32bc053537e8ae977 10772 libs standard 
libgpg-error_1.16-2.debian.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQJ8BAEBCgBmBQJUIyuuXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFQjk2OTEyODdBN0FEREUzNzU3RDkxMUVB
NTI0MDFCMTFCRkRGQTVDAAoJEKUkAbEb/fpc/rEP/iOmZ/9NehrpjdZt5JcBhUKt
4tALL+gKsdsQKCBY4MyxHMTi8Zm5yAsF/5LSSWX5zH1xj7yp+jDLYZ95ZVKVskOo
N0PZiaqU58hTaKT+GrWbupjlbNlk/G7jhX1j8LfhwUf884aZrwky+OYnInVxbtbg
pAML9CA+HM/jOkCwm7NNujxVNYpCjHWrXYrWoLPoI6uMjQZvvMDLX5Tj+ymgbZpL
dmerqqm+l8JUj7tzgi66sKwUAyphNI7s05LpTcDbg/bKqXAXovNiZLEFd/jGLlbu
uRqCkrCCEqvWw4cZ9A7RratUl01Fu1t5V3E8kjJD7s3fjtEbtpbuoX0M6yVO+LST
UoU1jHOqwJNIZ29ecwK6ZfZK724jA51kcyV5zKTRDI056Nd4J8XQ+bcM0Yz2W/2k
XKfuXsp15/KpdqwsG8y9D42bnT/V+TU9uZ4X3Tb4gfeid7QbB8gK/LmtDRrEwR0r
Y4AigynfXsp5yK9dZO4x9mImJgwRCinyA4Q4svM0POu8zeAzsL37ehbX+7kFEBVX
gf3eV3J/GqT/QwZo7p5K1YbbS89bOkejrs+eJHFSNoo1QGS+pTfchQqwME7dJAMj
rPd9CL/SgPnsWTHtL5UD7KnY2clovTA2ZyduI8Q927Js9holTKQQl0M8B1APlsB/
s95EKZpCOP6ZYPMDoSpo
=T+o3
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to