Bug#932302: marked as done (calendar: please make the build reproducible)
Your message dated Wed, 17 Jul 2019 16:07:40 +0000
with message-id <E1hnmSy-000GEH-23@fasolo.debian.org>
and subject line Bug#932302: fixed in calendar 2.04-3
has caused the Debian Bug report #932302,
regarding calendar: 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.)
--
932302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932302
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: calendar
Version: 2.04-2
Severity: wishlist
Tags: patch
User: reproducible-builds@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bugs@lists.alioth.debian.org
Hi,
Whilst working on the Reproducible Builds effort [0] we noticed
that calendar could not be built reproducibly.
Whilst you do accommodate SOURCE_DATE_EPOCH [1], unfortunately your
call to date(1) is currently missing the switch to make it timezone
agnostic, thus it can vary depending on "where" you build it from.
Patch attached.
[0] https://reproducible-builds.org/
[1] https://reproducible-builds.org/docs/source-date-epoch/
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` lamby@debian.org / chris-lamb.co.uk
`-
--- a/debian/rules 2019-07-17 09:50:20.599066174 -0300
--- b/debian/rules 2019-07-17 10:01:13.302028995 -0300
@@ -17,7 +17,7 @@
./configure
override_dh_auto_build:
- make BUILD_DATE="$(shell date -R -d @$(SOURCE_DATE_EPOCH))"
+ make BUILD_DATE="$(shell date -u -R -d @$(SOURCE_DATE_EPOCH))"
override_dh_auto_install:
mkdir -p $(OCAMLFIND_DESTDIR)
--- End Message ---
--- Begin Message ---
Source: calendar
Source-Version: 2.04-3
We believe that the bug you reported is fixed in the latest version of
calendar, 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 932302@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Stéphane Glondu <glondu@debian.org> (supplier of updated calendar 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: Wed, 17 Jul 2019 17:24:45 +0200
Source: calendar
Architecture: source
Version: 2.04-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers <debian-ocaml-maint@lists.debian.org>
Changed-By: Stéphane Glondu <glondu@debian.org>
Closes: 932302
Changes:
calendar (2.04-3) unstable; urgency=medium
.
* Fix call to date to make the build reproducible (Closes: #932302)
Checksums-Sha1:
c22aa5f71d228487d04b8b6787a0f9554895737e 1920 calendar_2.04-3.dsc
988866478ee4d6bd0b96dc181264af4d1855d3cf 5888 calendar_2.04-3.debian.tar.xz
Checksums-Sha256:
e52b75a8b0e87fe39b7fd988c575aefbceb61ecb9738a592c57379bae78b5790 1920 calendar_2.04-3.dsc
9123232eae82fbc08062978950730df6d85165fe323c254a9d4914b4035a067f 5888 calendar_2.04-3.debian.tar.xz
Files:
8c6090d00355276deb4b199cdc82de7a 1920 ocaml optional calendar_2.04-3.dsc
0b57c968fac7872d6e0723dbb56db869 5888 ocaml optional calendar_2.04-3.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCgAdFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAl0vPiYACgkQIbju8bGJ
MIFAawf/Qvh6KzdfL5gPJTnjDFKlUBC9uT+xUOPvPVtUlcrTDJjZ8WApFF3uMbVm
ajaHKq7deBX8AAaOvb8arzZaX8jgXO/FhiA44b96E+NQL0vHiozm3xktzMLhX3k0
Yxfife3YZGjZPZIHvSXA9kFvKad6KLbVnkqbFHxqUjoO1q+6oIWNn7dVNCkWQ66i
LIT/fQLWuyqnI4e0jxBTayeZDIJcMQeKv6LgAmEusfg6O4zQvCi1QfOS8dCrwCmS
f053i0WCKqC9x/CIufFKPR+mulfQMc00ieAHxqwcMkyTz/adKQgzuufhPVfhhdMV
jB55YK6DpSYJxk6BDjqhrxjdG1xcyA==
=ehyC
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: