Source: pikepdf Version: 3.2.0+dfsg-2 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Hi, Whilst working on the Reproducible Builds effort [0] we noticed that pikepdf could not be built reproducibly. This is because the documentation has an embedded example that shows the repr(..) of an object which, as it happens, includes the current build date, rendering the package unreproducible. Patch attached that assigns this to a variable instead of including it in the output. It should not affect the usefulness of this example. [0] https://reproducible-builds.org/ Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
--- a/debian/patches/reproducible-build.patch 1970-01-01 01:00:00.000000000 +0100 --- b/debian/patches/reproducible-build.patch 2021-10-20 09:38:52.207731996 +0100 @@ -0,0 +1,15 @@ +Description: Make the build reproducible +Author: Chris Lamb <la...@debian.org> +Last-Update: 2021-10-20 + +--- pikepdf-3.2.0+dfsg.orig/docs/topics/attachments.rst ++++ pikepdf-3.2.0+dfsg/docs/topics/attachments.rst +@@ -30,7 +30,7 @@ Now we can retrive the data. + + In [1]: pdf.attachments['README.md'] + +- In [1]: pdf.attachments['README.md'].get_file() ++ In [1]: file = pdf.attachments['README.md'].get_file() + + In [1]: pdf.attachments['README.md'].get_file().read_bytes()[:50] + --- a/debian/patches/series 2021-10-20 09:34:16.035906332 +0100 --- b/debian/patches/series 2021-10-20 09:38:51.527730733 +0100 @@ -1,3 +1,4 @@ docs-build-use-DEB_VERSION_UPSTREAM.patch drop-installation-from-docs-contents.patch drop-save-pike.patch +reproducible-build.patch