Path: csiph.com!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod From: Peter Pentchev Newsgroups: linux.debian.maint.python Subject: Re: dpkg-buildpackage vs sbuild with python packaging Date: Wed, 11 Jun 2025 17:50:01 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Wed Jun 11 15:49:01 2025 Old-Return-Path: X-Amavis-Spam-Status: No, score=-11.999 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, PGPSIGNATURE=-5, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate:hard: -4.6 X-Greylist: delayed 468 seconds by postgrey-1.36 at bendel; Wed, 11 Jun 2025 15:48:46 UTC MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="oLPmUEmEX0LQv7Ha" Content-Disposition: inline X-Mailing-List: archive/latest/23037 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/aEmjhiR6ihh3b_75@straylight.m.ringlet.net Approved: robomod@news.nic.it Lines: 69 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python X-Original-Date: Wed, 11 Jun 2025 18:40:54 +0300 X-Original-Message-ID: X-Original-References: <1779402678.132016719.1749649153102.JavaMail.zimbra@synchrotron-soleil.fr> <895197705.132125083.1749654653778.JavaMail.zimbra@synchrotron-soleil.fr> <10889998-45ef-4405-a231-bacd5fc27eeb@debian.org> Xref: csiph.com linux.debian.maint.python:16905 --oLPmUEmEX0LQv7Ha Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jun 11, 2025 at 05:25:41PM +0200, Santiago Vila wrote: > El 11/6/25 a las 17:10, PICCA Frederic-Emmanuel escribi=C3=B3: > > It seems that this is due to setuptools-scm which provide the list of t= he data during the dpkg-buildpackage. >=20 > That's it. You can now add setuptools-scm to build-conflicts if it makes = you happy. > It might help some people (for example, you in another parallel universe = who > still don't know this), but there is no policy requirement to add build-c= onflicts. So declaring a conflict on setuptools-scm may be a bit tricky, since it is also listed in the upstream's pyproject.toml file, although, of course, it may be patched out. If anything, a conflict should be declared against the "git" package :) However, it seems the upstream build actually depends on setuptools-scm now, they (you? :)) don't use any other way to tell the build system about the data files - the *.png images, the *.rst documentation, etc.. This... may be a problem if the package is not built out of a Git checkout with Git itself present... and Debian packages are usually expected to be built out of a plain extracted source archive, no `.git/`, no anything. I'd suggest making some changes upstream, like listing the data files yours= elf: https://setuptools.pypa.io/en/latest/userguide/datafiles.html (or, of course, switching away from setuptools, but any build system you ch= oose may still need to be configured to include the data files along with your Python module sources, although some of them do this by default for most f= iles) G'luck, Peter --=20 Peter Pentchev roam@ringlet.net roam@debian.org peter@morpheusly.com PGP key: https://www.ringlet.net/roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 --oLPmUEmEX0LQv7Ha Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEELuenpRf8EkzxFcNUZR7vsCUn3xMFAmhJo4IACgkQZR7vsCUn 3xOZtQ//XaTK6PduOy9ZDNv2tXpV8XGMfoUl1Ap4pN5kOjD7ab50qmuBZPmgYrrY yttlxr9T4fnMgpgCvJitM/GQliOE0xbLssqyCQvCEtbkppfzsQRHOldFZKsRDfmr UbfswmnhquGWyg4j/FGDh6SScNZlvji3RelB5Up7hMDjvE9K5RvoOQ0YQA0NdC8L RQ8YgNyhOc1vDJRjuh8Tqk8Gmoa6Xy6eSF8HobeWpsrWpsYqyjAQe7npjoh4S1Az I1wWD56FZuWwNJFepf2e5zpggssfkXyoXq4JRBMx+g2Tqihb+BCdckT06p/Xn7M/ dXEQdQv5gOV+WFt57lJmKIZzcG0Vznn1XXNRTWTbx8484vVYdKyRUI7MP3J+cdFJ XVYRF+tYybJQ6hRplAfsNsjQDJZ/lI/f0MMkxSwdEfGYqK/uDAhrsvAdO1ISKL+O aFW9Jk3UVfJw04kD/PQDs9IKTfCoSxdeFntszydnkT4TFzfvxpT+olwP0AovI/3G Px6caHOfwRCT3Ny0UPW1xxLWhVZgO8cm0ZV9UBiNpfHng26RHi7gUhlcRCsqA0t2 REHT+rTUW06Op+craZbWAjzQM64O00MmkDUOrh0PQzP8IH3zXR5Os9FS0KzpdVe1 q3TvWko3vcym28eacXMPa/br1ljoWITx+0oUgLx94S4W5dKWvWU= =VhXp -----END PGP SIGNATURE----- --oLPmUEmEX0LQv7Ha--