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ó: > > It seems that this is due to setuptools-scm which provide the list of the > > data during the dpkg-buildpackage. > > 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-conflicts.
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 yourself: https://setuptools.pypa.io/en/latest/userguide/datafiles.html (or, of course, switching away from setuptools, but any build system you choose 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 files) G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@debian.org pe...@morpheusly.com PGP key: https://www.ringlet.net/roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13
signature.asc
Description: PGP signature
