Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1270929 > unrolled thread

Bug#1121065: pychopper: please make the build reproducible

Started by"Chris Lamb" <lamby@debian.org>
First post2025-11-20 15:50 +0100
Last post2025-11-20 15:50 +0100
Articles 1 — 1 participant

Back to article view | Back to linux.debian.bugs.dist


Contents

  Bug#1121065: pychopper: please make the build reproducible "Chris Lamb" <lamby@debian.org> - 2025-11-20 15:50 +0100

#1270929 — Bug#1121065: pychopper: please make the build reproducible

From"Chris Lamb" <lamby@debian.org>
Date2025-11-20 15:50 +0100
SubjectBug#1121065: pychopper: please make the build reproducible
Message-ID<LTe8V-eoLy-1@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Source: pychopper
Version: 2.7.10-1
Severity: wishlist
Tags: patch
User: reproducible-builds@lists.alioth.debian.org
Usertags: nocheck
X-Debbugs-Cc: reproducible-bugs@lists.alioth.debian.org

Hi,

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

This was because it ships a different binary package depending
on whether the tests are run or not. This was caused by two things:

1. The testsuite did not sufficiently clean up after itself, leaving
the pychopper/tests/ directory around, which was then installed into
the binary package... but only if the tests were run.

2. The calls to chmod +x the scripts were only performed if the tests
were run, meaning that these were _not_ executable in the .deb
if nocheck was specified (and potentially resulting in a broken
package — I don't know how used these scripts are).

Patch attached that addresses both issues.

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


Regards,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org / chris-lamb.co.uk
       `-

[toc] | [standalone]


Back to top | Article view | linux.debian.bugs.dist


csiph-web