Source: bsh
Version: 2.0b4-18
Severity: wishlist
Tags: patch
User: [email protected]
Usertags: timestamps
X-Debbugs-Cc: [email protected]

Hi!

While working on the “reproducible builds” effort [1], we have noticed
that bsh could not be built reproducibly.

The attached patch clamps the timestamps to the changelog timestamp when
creating the source archive. Once applied, bsh can be built reproducibly
in our current experimental framework. Best regards.

Jathan

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

-- 
Por favor evita enviarme adjuntos en formato de word o powerpoint, si
quieres saber porque lee esto:
http://www.gnu.org/philosophy/no-word-attachments.es.html
¡Cámbiate a GNU/Linux! http://getgnulinux.org/es
diff -Nru bsh-2.0b4/debian/changelog bsh-2.0b4/debian/changelog
--- bsh-2.0b4/debian/changelog  2016-05-30 12:14:02.000000000 -0500
+++ bsh-2.0b4/debian/changelog  2017-10-01 22:01:37.000000000 -0500
@@ -1,3 +1,10 @@
+bsh (2.0b4-18.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix timestamps_in_tarball reproducible build issue.
+
+ -- Jonathan Bustillos <[email protected]>  Sun, 01 Oct 2017 
22:01:37 -0500
+
 bsh (2.0b4-18) unstable; urgency=medium
 
   * Team upload.
diff -Nru bsh-2.0b4/debian/rules bsh-2.0b4/debian/rules
--- bsh-2.0b4/debian/rules      2016-05-30 12:06:22.000000000 -0500
+++ bsh-2.0b4/debian/rules      2017-10-01 22:00:30.000000000 -0500
@@ -1,6 +1,7 @@
 #!/usr/bin/make -f
 # debian/rules file for bsh (uses cdbs)
 
+SOURCE_DATE_EPOCH       ?= $(shell dpkg-parsechangelog -STimestamp)
 include /usr/share/cdbs/1/rules/debhelper.mk
 include /usr/share/cdbs/1/class/ant.mk
 
@@ -29,6 +30,7 @@
 install/bsh-src:: binary-install/bsh-doc
        mkdir -p debian/bsh-src/usr/src/bsh-src
        tar --exclude debian --exclude classes --exclude dist --exclude api \
+         --clamp-mtime --mtime="$(SOURCE_DATE_EPOCH)" \
                -zcf debian/bsh-src/usr/src/bsh-src/bsh.tar.gz *
 
 binary-fixup/bsh-doc::

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to