Source: libapache-dbi-perl
Version: 1.12-1
Severity: wishlist
Tags: patch
User: reproducible-builds@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org

Hi,

While working on the "reproducible builds" effort [1], we have noticed
that libapache-dbi-perl could not be built reproducibly.

The attached patch sets the embedded date in the man pages generated by
podman to the latest debian/changelog entry timestamp instead of local
date. Once applied, libapache-dbi-perl can be built reproducibly in our
current experimental framework.

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


Regards,
-- 
Dhole
diff -Nru libapache-dbi-perl-1.12/debian/changelog 
libapache-dbi-perl-1.12/debian/changelog
--- libapache-dbi-perl-1.12/debian/changelog    2013-06-12 18:17:37.000000000 
+0200
+++ libapache-dbi-perl-1.12/debian/changelog    2015-09-10 00:24:04.000000000 
+0200
@@ -1,3 +1,11 @@
+libapache-dbi-perl (1.12-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Replace timestamp in man pages to latest debian/changelog entry timestamp
+    to make the package build reproducibly.
+
+ -- Eduard Sanou <dh...@openmailbox.org>  Thu, 10 Sep 2015 00:23:31 +0200
+
 libapache-dbi-perl (1.12-1) unstable; urgency=low
 
   [ Salvatore Bonaccorso ]
diff -Nru libapache-dbi-perl-1.12/debian/rules 
libapache-dbi-perl-1.12/debian/rules
--- libapache-dbi-perl-1.12/debian/rules        2013-06-12 18:02:44.000000000 
+0200
+++ libapache-dbi-perl-1.12/debian/rules        2015-09-10 00:33:54.000000000 
+0200
@@ -1,3 +1,7 @@
 #!/usr/bin/make -f
+
+SOURCE_DATE_EPOCH = $(shell date -d "$$(dpkg-parsechangelog -SDate)" +%s)
+export POD_MAN_DATE = $(shell date -u +"%Y-%m-%d" 
--date="@$(SOURCE_DATE_EPOCH)")
+
 %:
        dh $@

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
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