From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 23776@debbugs.gnu.org
Subject: bug#23776: Perl's .pod files include timestamps, making Perl package builds non-deterministic
Date: Sun, 19 Jun 2016 13:31:54 -0400 [thread overview]
Message-ID: <20160619173154.GA26953@jasmine> (raw)
In-Reply-To: <20160616153927.GB2245@jasmine>
On Thu, Jun 16, 2016 at 11:39:27AM -0400, Leo Famulari wrote:
> On Thu, Jun 16, 2016 at 01:33:46PM +0200, Ludovic Courtès wrote:
> > The problem is described in <git://git.debian.org/git/reproducible/notes.git>:
> >
> > --8<---------------cut here---------------start------------->8---
> > timestamps_in_documentation_generated_by_podman:
> > description: |
> > The module Pod::Man includes timestamps in its embedded manpages:
> > http://sources.debian.net/src/perl/latest/cpan/podlators/lib/Pod/Man.pm/?hl=1700#L977
> > They should be based on the mtime of the original file.
> > url: https://wiki.debian.org/ReproducibleBuilds/TimestampsInManpagesGeneratedByPodMan
>
> According to the information on this page, we should set POD_MAN_DATE
> while building. Should we make the perl-build-system export this
> variable? Set to SOURCE_DATE_EPOCH?
I noticed that Pod::Man is supposed to respect SOURCE_DATE_EPOCH, as of
the upstream module version 4.03 (released 2015-12-06). Does anyone know
how to check the version of the module bundled into perl?
[0]
https://metacpan.org/pod/Pod::Man#date
[1]
https://www.eyrie.org/~eagle/software/podlators/news.html
next prev parent reply other threads:[~2016-06-19 17:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 11:33 bug#23776: Perl's .pod files include timestamps, making Perl package builds non-deterministic Ludovic Courtès
2016-06-16 15:39 ` Leo Famulari
2016-06-17 8:11 ` Ludovic Courtès
2016-06-17 18:50 ` Leo Famulari
2016-06-18 20:35 ` Ludovic Courtès
2016-06-19 17:31 ` Leo Famulari [this message]
2016-06-25 18:23 ` Leo Famulari
2016-07-30 9:28 ` Ludovic Courtès
2017-01-11 22:27 ` Ludovic Courtès
2017-01-12 17:24 ` Marius Bakke
2017-01-13 8:02 ` Ludovic Courtès
2017-10-31 15:17 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160619173154.GA26953@jasmine \
--to=leo@famulari.name \
--cc=23776@debbugs.gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.