[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#828790: marked as done (debiandoc-sgml-doc: please make the build reproducible)

Your message dated Sat, 16 Jan 2021 14:23:31 +0000
with message-id <E1l0mUF-000Fhh-Co@fasolo.debian.org>
and subject line Bug#828790: fixed in debiandoc-sgml-doc 1.1.26
has caused the Debian Bug report #828790,
regarding debiandoc-sgml-doc: please make the build reproducible
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 owner@bugs.debian.org
immediately.)


-- 
828790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828790
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: debiandoc-sgml-doc 
Version: 1.1.24+nm 
Severity: wishlist
Tags: patch
User: reproducible-builds@lists.alioth.debian.org
Usertags: locale
X-Debbugs-Cc: reproducible-builds@lists.alioth.debian.org

Hi,

While working on the "reproducible builds" effort [1], we have noticed that
debiandoc-sgml-doc could not be built reproducibly.

When generating the documentation files, a timestamp of the last changelog entry
is embedded in the local timezone.

The attached patch fixes this setting the timestamp to UTC. Once applied,
debiandoc-sgml-doc can be built reproducibly in our current experimental
framework.

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

Regards,
-- 
Dhole

diff -Nru debiandoc-sgml-doc-1.1.24/debian/changelog debiandoc-sgml-doc-1.1.24+nmu1/debian/changelog
--- debiandoc-sgml-doc-1.1.24/debian/changelog	2015-08-12 18:31:34.000000000 +0200
+++ debiandoc-sgml-doc-1.1.24+nmu1/debian/changelog	2016-06-27 21:34:23.000000000 +0200
@@ -1,3 +1,10 @@
+debiandoc-sgml-doc (1.1.24+nmu1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Set the embedded date to UTC to make it reproducible. 
+
+ -- Eduard Sanou <dhole@openmailbox.org>  Mon, 27 Jun 2016 21:34:14 +0200
+
 debiandoc-sgml-doc (1.1.24) unstable; urgency=medium
 
   * Reproducible build with the new debiandoc-sgml 1.2.31-1.
diff -Nru debiandoc-sgml-doc-1.1.24/debian/rules debiandoc-sgml-doc-1.1.24+nmu1/debian/rules
--- debiandoc-sgml-doc-1.1.24/debian/rules	2015-08-12 18:18:25.000000000 +0200
+++ debiandoc-sgml-doc-1.1.24+nmu1/debian/rules	2016-06-27 21:34:09.000000000 +0200
@@ -8,7 +8,7 @@
 #export DH_VERBOSE=1
 
 # Reproduceble build
-DEBIANDOC_DATE ?= $(shell date +'%Y-%m-%d' -d"`dpkg-parsechangelog -SDate`")
+DEBIANDOC_DATE ?= $(shell date --utc +'%Y-%m-%d' -d"`dpkg-parsechangelog -SDate`")
 export DEBIANDOC_DATE
 
 ## ----------------------------------------------------------------------

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Source: debiandoc-sgml-doc
Source-Version: 1.1.26
Done: Osamu Aoki <osamu@debian.org>

We believe that the bug you reported is fixed in the latest version of
debiandoc-sgml-doc, 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 828790@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Osamu Aoki <osamu@debian.org> (supplier of updated debiandoc-sgml-doc 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 ftpmaster@ftp-master.debian.org)


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

Format: 1.8
Date: Sat, 16 Jan 2021 22:24:31 +0900
Source: debiandoc-sgml-doc
Architecture: source
Version: 1.1.26
Distribution: unstable
Urgency: medium
Maintainer: Debian XML SGML Team <debian-sgml@lists.debian.org>
Changed-By: Osamu Aoki <osamu@debian.org>
Closes: 828790
Changes:
 debiandoc-sgml-doc (1.1.26) unstable; urgency=medium
 .
   * Set the embedded date to UTC to make it reproducible as suggested
     by Eduard Sanou <dhole@openmailbox.org>.  Closes: #828790
   * Bump policy to 4.5.1 and debhelper-compat to 13.
Checksums-Sha1:
 7ea66c791b17af7d31d3a608ea68cf97f30615fe 1710 debiandoc-sgml-doc_1.1.26.dsc
 9e590f9e1aa5905e56a12322ce61cfa06977463f 18856 debiandoc-sgml-doc_1.1.26.tar.xz
 969e0eb385656f61866d8ca9c94a9c68195754d9 5616 debiandoc-sgml-doc_1.1.26_source.buildinfo
Checksums-Sha256:
 9b9c5fbf5f66d2a3aea4178d358165d613c55218de667301e463ebbdb1a9c8ca 1710 debiandoc-sgml-doc_1.1.26.dsc
 59895f48b68ad1f0550a860101ece0619a37bd5ffa6d321e15cce9d0be3d5ed7 18856 debiandoc-sgml-doc_1.1.26.tar.xz
 e284a74fdc87f730f97986fb3669643ecc2e60bd44e6b826a9626be7e20a2ef6 5616 debiandoc-sgml-doc_1.1.26_source.buildinfo
Files:
 5ef4d83f92a46fbd040d5a468bc62435 1710 doc optional debiandoc-sgml-doc_1.1.26.dsc
 ca4a26f823823add37bbe43e2805a0cb 18856 doc optional debiandoc-sgml-doc_1.1.26.tar.xz
 2cd0e14cd68127e5913f919240f6e744 5616 doc optional debiandoc-sgml-doc_1.1.26_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEMTNyTWIHiBV56V1iHhNWiB3Y15EFAmAC7N0ACgkQHhNWiB3Y
15EESRAAlT0+YYxnfCr1CIWW5HEpB7hwHTjGwjL9iZhmrZ5xo4gWb5J4JtjPIZrZ
myJJLYRORz69H8MeAiZXQRm3VAnUCdzNd3PAb+YTUfkpfB/c3FOjadKDtQs63ytz
6aBvIrqQjQpPwHUznBp9obv7qN5gjw7CuWDPwe7YiDDI2XxdmTV4hdbjBb2H7Ker
EdyCoRahaRMWWw3Qsm0/fp382K+pu0vKwrHZ9nf3kLooi4QYWMajv0+xhpBiBXws
ooiN42d1Rca3qqbBe4DxQ0r1a88EQPlCmWEVUeJbmUIc9sXWEfG4YfmKZuFmyh7z
AvEU4tf9FOY3vAtd1x4CzfWrBlik3Qb1XEK49IdooaH4Vq6NQosxHYjGDkppMEIN
xHCPlh4zyMLJhp18Ful1eFQjpeIV4gYkqrZmB+qPOvPiprO9IRhiCFsjQg0VqVL8
RzN1vsG9FMpkFmmS+suPXqoOIlOgGRaLyuAKFC2Ai7zsvM7DeStFWhDJCRE9s14f
r32fhW233zwTA0v6yllvbn/1pVogbLTt9Tgtop2lWa7K0W+fFAbF8P946MT6JVvU
iGue40YW2iZag2u06+HN6MGldtMQs6X8xd/P+IYx08PlQqV8cDRpY2sOjqXBMYlu
JXtI3oTp9hVnehne4HFR9jC05pCT8DVIRR9+aF0E/BrvV+GAO+I=
=QUus
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: