Debian Bug report logs - #932302
calendar: please make the build reproducible

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: "Chris Lamb" <lamby@debian.org>

To: submit@bugs.debian.org

Subject: calendar: please make the build reproducible

Date: Wed, 17 Jul 2019 10:03:04 -0300

[Message part 1 (text/plain, inline)]

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
       `-

[calendar.diff.txt (text/plain, attachment)]

Message #8 received at 932302-submitter@bugs.debian.org (full text, mbox, reply):

From: Stéphane Glondu <noreply@salsa.debian.org>

To: 932302-submitter@bugs.debian.org

Subject: Bug#932302 marked as pending in calendar

Date: Wed, 17 Jul 2019 15:28:11 +0000

Control: tag -1 pending

Hello,

Bug #932302 in calendar reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/ocaml-team/calendar/commit/f2b1ab52f780e1c6ca16c3edb5506904dc4a3392

------------------------------------------------------------------------
Fix call to date to make the build reproducible (Closes: #932302)
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/932302

Message #15 received at 932302-close@bugs.debian.org (full text, mbox, reply):

From: Stéphane Glondu <glondu@debian.org>

To: 932302-close@bugs.debian.org

Subject: Bug#932302: fixed in calendar 2.04-3

Date: Wed, 17 Jul 2019 16:07:40 +0000

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-----

Send a report that this bug log contains spam.