Debian Bug report logs - #824266
mkdocs: Please support SOURCE_DATE_EPOCH specification for build time stamps

Toggle useless messages

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

From: Axel Beckert <abe@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: mkdocs: Please support SOURCE_DATE_EPOCH specification for build time stamps

Date: Sat, 14 May 2016 15:48:41 +0200

Package: mkdocs
Version: 0.15.3-3
Severity: wishlist
User: reproducible-builds@lists.alioth.debian.org
Usertags: timestamps toolchain
Control: affects -1 unburden-home-dir djangorestframework

Hi,

mkdocs integrates build time stamps into the documentation it is
generating. This makes at least unburden-home-dir no more reproducibly
building because it now uses mkdocs to generate HTML documentation at
build time.

See https://tests.reproducible-builds.org/rb-pkg/unstable/amd64/unburden-home-dir.html and
https://tests.reproducible-builds.org/dbd/unstable/amd64/unburden-home-dir_0.4.diffoscope.html

Other cases of this issue are the source package djangorestframework (see
https://tests.reproducible-builds.org/rb-pkg/testing/i386/djangorestframework.html and
https://tests.reproducible-builds.org/dbd/testing/i386/djangorestframework_3.3.2-2.diffoscope.html)
and of course the source package python-mkdocs itself, see
https://tests.reproducible-builds.org/rb-pkg/unstable/amd64/python-mkdocs.html and
https://tests.reproducible-builds.org/dbd/unstable/amd64/python-mkdocs_0.15.3-3.diffoscope.html

At https://reproducible-builds.org/specs/source-date-epoch/ you can find
a bound to be widely adopted specification for how to solve such kind of
issues generally: If the environment variable SOURCE_DATE_EPOCH exists
use the Unix time stamp (seconds since 1st of January 1970, 00:00:00
UTC) it contains to preseed all build time stamps with that time stamp
instead of the current time.

See https://wiki.debian.org/ReproducibleBuilds/TimestampsProposal#Examples
for some examples on how to implement support for SOURCE_DATE_EPOCH,
including an example for Python.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'), (111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'), (105, 'experimental-debug')
Architecture: amd64 (x86_64)

Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mkdocs depends on:
ii  fonts-font-awesome     4.6.1~dfsg-1
ii  mkdocs-bootstrap       0.1.1-2
ii  mkdocs-bootswatch      0.4.0-2
ii  python3-click          6.6-1
ii  python3-jinja2         2.8-1
ii  python3-livereload     2.4.0-1
ii  python3-markdown       2.6.6-1
ii  python3-pkg-resources  20.10.1-1
ii  python3-tornado        4.2.1-2
ii  python3-yaml           3.11-3+b1
pn  python3:any            <none>

mkdocs recommends no packages.

Versions of packages mkdocs suggests:
ii  ghp-import  0.4.1-1
ii  mkdocs-doc  0.15.3-3

-- no debconf information

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

From: Brian May <bam@debian.org>

To: Axel Beckert <abe@debian.org>, 824266@bugs.debian.org

Subject: Re: [Python-modules-team] Bug#824266: mkdocs: Please support SOURCE_DATE_EPOCH specification for build time stamps

Date: Sun, 15 May 2016 12:32:38 +1000

Axel Beckert <abe@debian.org> writes:

> mkdocs integrates build time stamps into the documentation it is
> generating. This makes at least unburden-home-dir no more reproducibly
> building because it now uses mkdocs to generate HTML documentation at
> build time.

Is this something that should be forwarded upstream?

https://github.com/mkdocs/mkdocs/issues
-- 
Brian May <bam@debian.org>

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

From: Axel Beckert <abe@debian.org>

To: Brian May <bam@debian.org>

Cc: 824266@bugs.debian.org, Reproducible builds folks <reproducible-builds@lists.alioth.debian.org>

Subject: Re: [Python-modules-team] Bug#824266: mkdocs: Please support SOURCE_DATE_EPOCH specification for build time stamps

Date: Sun, 15 May 2016 15:24:40 +0200

Hi Brian,

Brian May wrote:
> Axel Beckert <abe@debian.org> writes:
> > mkdocs integrates build time stamps into the documentation it is
> > generating. This makes at least unburden-home-dir no more reproducibly
> > building because it now uses mkdocs to generate HTML documentation at
> > build time.
> 
> Is this something that should be forwarded upstream?

The Reproducible Builds folks definitely would be happy if this could
be incorporated upstream, yes.

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

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

From: Brian May <bam@debian.org>

To: Axel Beckert <abe@debian.org>, 824266@bugs.debian.org

Subject: Re: [Python-modules-team] Bug#824266: mkdocs: Please support SOURCE_DATE_EPOCH specification for build time stamps

Date: Tue, 17 May 2016 09:16:36 +1000

Axel Beckert <abe@debian.org> writes:

> See https://wiki.debian.org/ReproducibleBuilds/TimestampsProposal#Examples
> for some examples on how to implement support for SOURCE_DATE_EPOCH,
> including an example for Python.

Response from the upstream author (please consider replying to the
upstream bug report, not here):

"FYI, the Python example is wrong. If `SOURCE_DATE_EPOCH` is supposed to
be a Unix timestamp (number of seconds since epoch), then
`time.gmtime()` is not the Python equivalent. However,
`calendar.timegm(datetime.datetime.utcnow().utctimetuple())` or
`calendar.timegm(time.gmtime())` is. It is annoyingly complicated to get
a Unix timestamp in Python. Although Python >= 3.3 makes it easier with
`datetime.datetime.utcnow().timestamp()`.  Not sure how the `datetime`
module went so long without the ability to return a timestamp."
-- 
Brian May <bam@debian.org>

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

From: Brian May <bam@debian.org>

To: 831648-close@bugs.debian.org

Subject: Bug#831648: fixed in python-mkdocs 0.15.3-5

Date: Thu, 28 Jul 2016 22:55:56 +0000

Source: python-mkdocs
Source-Version: 0.15.3-5

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

Debian distribution maintenance software
pp.
Brian May <bam@debian.org> (supplier of updated python-mkdocs 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: SHA256

Format: 1.8
Date: Fri, 29 Jul 2016 08:12:18 +1000
Source: python-mkdocs
Binary: mkdocs mkdocs-doc
Architecture: source all
Version: 0.15.3-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team <python-modules-team@lists.alioth.debian.org>
Changed-By: Brian May <bam@debian.org>
Description:
 mkdocs     - Static site generator geared towards building project documentati
 mkdocs-doc - Static site generator (documentation)
Closes: 831648
Changes:
 python-mkdocs (0.15.3-5) unstable; urgency=medium
 .
   * Support Reproducible builds. Closes: #831648.
Checksums-Sha1:
 63d91ed3f5286dcff541500217a09c6fd1fd9fbc 2287 python-mkdocs_0.15.3-5.dsc
 544760693a444da8f7b005ddc69b30e8ad69f3df 1805972 python-mkdocs_0.15.3.orig.tar.gz
 aed96ec93f7793c4262d2c3495bc446880b3b15f 149208 python-mkdocs_0.15.3-5.debian.tar.xz
 50fb32795366ddda57cbe3841526fcc2c5b1e25f 1106996 mkdocs-doc_0.15.3-5_all.deb
 4ebdf3d4327416184797741d9955178c0506d4a3 248442 mkdocs_0.15.3-5_all.deb
Checksums-Sha256:
 15e670eae8adf864f636882635cabe14da5fbe46336a7886c6bfa11029cfe7a3 2287 python-mkdocs_0.15.3-5.dsc
 a5442ae24fd9e6f9daeefaf354c960e5dac27ff388f63e1bb324ed8a1b7edaa9 1805972 python-mkdocs_0.15.3.orig.tar.gz
 2ec5b3ac08d517573e4d5ad27a0db689112e0281423ee9a2215c3d0a5c58950c 149208 python-mkdocs_0.15.3-5.debian.tar.xz
 4b2e0e08899f139eb9557e913c3526b12e7a61cbf3cd8f393714daf153bbc76c 1106996 mkdocs-doc_0.15.3-5_all.deb
 6bb50946d57efecceba2394be903bf982709294282554143183c9fe6503266b9 248442 mkdocs_0.15.3-5_all.deb
Files:
 6c3f4d872dfbff97863b654a19c0fda0 2287 text optional python-mkdocs_0.15.3-5.dsc
 8d7ef937983bd7b7757d696aeaa5866a 1805972 text optional python-mkdocs_0.15.3.orig.tar.gz
 a68713693f245da1cf7b2b86e493a3c0 149208 text optional python-mkdocs_0.15.3-5.debian.tar.xz
 73e1d530bb4d213c5297a65b7bd74144 1106996 doc optional mkdocs-doc_0.15.3-5_all.deb
 bad78ca4788b121e8e4eb0ec72c9d94d 248442 text optional mkdocs_0.15.3-5_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJXmocGAAoJEBeEV3+BH26skuYQALDqX5cljFHMTtJjizmQf9eH
dLk3AveIUeZ5rFZ+gN60nOCUROMmQmFzcawBTrRWVx8oMJAL4jPRFKoZl9DoMv7K
M34Q+gSnDgYkzfBCk7S6KKA25RoQd0bEfFkQ9tqiLArml2w+5IQO+/4OzUN2oE/a
gfeuHhHxWYEcChAzh0+fGoS3/X0zKLWDewKk3xprzAQJBbQsTXh5aIqRzalGoZzQ
xmBfvw+/+ou8GuZd4XwTmeADi8w3Dxz3Bg4f2G8qyMNzJNNZin6nZ7ynkdWfM3h3
CMPgy/ltND4xxV5teIaoabyOBU2N99nIkag9m4x67ld3jAtJIpRjLry91gbhZORn
3tbBohCPkXpPq8M+CfKrv2pcR6Q8XLfQI/RQMrDYtNhbl1cn08noK4zbMVhqfAuI
w50PDEC3EZsttq0gLpDgzGJB+ZEPvG7HlC7bxvmA/mx5MgKFAFrt9oxo3Hja7Wdz
YyD87fYCkDpgz1XLUb8tw+SqCwm3y65zKD7uxRaT5wumKDnp15IzVC+z33aD129A
ZlTj6uGp0dQyeBzquqyhuOrmyeWPMABz4IXG2gy0Dw/xG3nyV/558c7oKLLV37vl
QjmqdBPz1IqVvnwKh/gKfXqLt0z/RyFwPET16OgOvJAmqd+1E9oiqMiEogW543ER
2WNBb8oRZwfYOQ6zd4eZ
=ZwTU
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.