Commit dc05d25c authored by Chris Lamb's avatar Chris Lamb 💬 Committed by Ole Streicher

Please make the build reproducible

Closes: #901428

Hi,

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

This is because it installs random cache files under at, for
example:

  /usr/​lib/​python2.​7/​dist-​packages/​pyraf/​clcache.​v2/​peHMUQgAPVjvymGi0Huk+​w==

Patch attached.

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

Regards,

      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org / chris-lamb.co.uk
       `-
parent a9daaab8
......@@ -13,3 +13,7 @@ endif
override_dh_clean:
dh_clean
rm -rf lib/pyraf.egg-info/
override_dh_auto_install:
dh_auto_install
find debian -type d -name clcache.v2 -print0 | xargs -0r rm -rfv
  • I wonder if there is a solution that can go upstream. eg. something in MANIFEST or setup.py? However it looks like there is something there to include them which is odd.

  • The upstream design is a bit weird here: The cache is meant to take code transferred from CL (an old, domain specific language) to Python on the fly. This however never worked well, does not work at all with Python 3, so it is already disabled upstream. Problem is that pyraf is under minimal maintenance upstream, so they take only grave problems; there are a couple of other smaller problems. I am in some discussion with them to put the upstream development under community maintenance. However: It is all (important) legacy, so the focus is on keeping it running and available.

Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment