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


Groups > linux.debian.maint.python > #13636

packaging help request: paths for build_py and build_scripts phases

Path csiph.com!newsfeed.xs4all.nl!newsfeed8.news.xs4all.nl!bofh.it!news.nic.it!robomod
From Jonathan Dowland <jmtd@debian.org>
Newsgroups linux.debian.maint.python
Subject packaging help request: paths for build_py and build_scripts phases
Date Mon, 18 Oct 2021 12:10:01 +0200
Message-ID <D9xKF-1cl-5@gated-at.bofh.it> (permalink)
X-Original-To debian-python@lists.debian.org
X-Mailbox-Line From debian-python-request@lists.debian.org Mon Oct 18 10:04:28 2021
Old-Return-Path <jon@dow.land>
X-Amavis-Spam-Status No, score=-7.551 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, BODY_8BITS=1.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FOURLA=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, LDO_WHITELIST=-5, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
X-Policyd-Weight using cached result; rate: -4.6
Mail-Followup-To jmtd@debian.org, debian-python@lists.debian.org
MIME-Version 1.0
Content-Type text/plain; charset=utf-8; format=flowed
Content-Disposition inline
Content-Transfer-Encoding 8bit
X-Mailing-List <debian-python@lists.debian.org> archive/latest/19432
List-ID <debian-python.lists.debian.org>
List-URL <https://lists.debian.org/debian-python/>
List-Archive https://lists.debian.org/msgid-search/20211018100412.4tlznklyu24kxh3k@coil
Approved robomod@news.nic.it
Lines 55
Organization linux.* mail to news gateway
Sender robomod@news.nic.it
X-Original-Date Mon, 18 Oct 2021 11:04:12 +0100
X-Original-Message-ID <20211018100412.4tlznklyu24kxh3k@coil>
Xref csiph.com linux.debian.maint.python:13636

Show key headers only | View raw


Hello,

I am attempting to package the latest upstream version of "trash-cli"¹,
which differs quite a lot from the current package on the build side of
things.
https://github.com/andreafrancia/trash-cli

The problem occurs during the post-build test phase. The tests cannot
find the scripts they are trying to test. The build appears to be a
standard python setuptools/distutils thing and the packaging is a
standard dh --with python3 --buildsystem=pybuild. The Build runs

     /usr/bin/python3 setup.py build 

Which outputs the following (elided)

> running build_py
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/trashcli
> copying trashcli/fstab.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9/build/trashcli
...

So for the build_py phase, the destination for copied files is rooted
under <<PKGBUILDDIR>>. The next build phase handles scripts:

> running build_scripts
> creating build
> creating build/scripts-3.9
> copying and adjusting trash -> build/scripts-3.9
...

Here, the scripts are copied to a path *not* rooted in <<PKGBUILDDIR>>.
So far as I can tell, both phases are normal parts of the
setuptools/distutils build lifecycle, and I haven't spotted anything
obviously non-standard about the way that is specified.

Where is it that the build_py phase's path are specified or overridden
such that they are correctly rooted under <<PKGBUILDDIR>>, and why isn't
the same true of the build_scripts phase?

I've pushed my WIP packaging to a temporary branch.
https://salsa.debian.org/debian/trash-cli/-/tree/jmtd-update-0.21.7.24
A BTS bug requesting the new version with some back-and-forth trying to
figure this out is
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988597

Thank you in advance for any tips you can offer!


Best wishes,

-- 

👱🏻	Jonathan Dowland
✎	 jmtd@debian.org
🔗	https://jmtd.net

Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar | Unroll thread


Thread

packaging help request: paths for build_py and build_scripts phases Jonathan Dowland <jmtd@debian.org> - 2021-10-18 12:10 +0200
  Re: packaging help request: paths for build_py and build_scripts  phases Timo Röhling <roehling@debian.org> - 2021-10-18 18:20 +0200

csiph-web