Bug#1120875: python-graphene: please make the build reproducible

Chris Lamb lamby at debian.org
Mon Nov 17 20:31:38 GMT 2025


Source: python-graphene
Version: 3.4.3-2
Severity: wishlist
Tags: patch
User: reproducible-builds at lists.alioth.debian.org
Usertags: nocheck
X-Debbugs-Cc: reproducible-bugs at lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed that
python-graphene could not be built reproducibly.

This is because it ships a different binary package depending on
whether the testsuite is run or not.

Specifically, if the testsuite is run, a number of directories under
the examples/ directory have their modification times bumped if the
tests are run. (I suspect this is due to the creation of .pyc files
or __pycache__ dirs, but I haven't confirmed that). This means that
the binary package ends up with different directory metadata for
these dirs.

A patch attached is that will set these modification times to the
value of SOURCE_DATE_EPOCH, regardless of whether the tests are run.

 [0] https://reproducible-builds.org/


Regards,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby at debian.org / chris-lamb.co.uk
       `-
-------------- next part --------------
--- a/debian/rules	2025-11-17 11:26:49.969351885 -0800
--- b/debian/rules	2025-11-17 11:35:19.372907047 -0800
@@ -31,3 +31,6 @@
 override_dh_fixperms:
 	dh_fixperms
 	find debian/python3-graphene -depth -name __pycache__ -execdir rm -rf {} +
+
+execute_before_dh_install:
+	touch -d@$(SOURCE_DATE_EPOCH) examples/*/ examples/*/tests/


More information about the Reproducible-bugs mailing list