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


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

Re: dpkg-buildpackage vs sbuild with python packaging

From Peter Pentchev <roam@ringlet.net>
Newsgroups linux.debian.maint.python
Subject Re: dpkg-buildpackage vs sbuild with python packaging
Date 2025-06-11 17:50 +0200
Message-ID <KWvS9-9QkP-11@gated-at.bofh.it> (permalink)
References <KWu9H-9P7V-1@gated-at.bofh.it> <KWuW5-9PHr-5@gated-at.bofh.it> <KWvyO-9Qc4-5@gated-at.bofh.it> <KWvyO-9Qc4-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


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

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  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

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


Thread

dpkg-buildpackage vs sbuild with python packaging PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2025-06-11 16:00 +0200
  Re: dpkg-buildpackage vs sbuild with python packaging Santiago Vila <sanvila@debian.org> - 2025-06-11 16:50 +0200
    Re: dpkg-buildpackage vs sbuild with python packaging PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2025-06-11 17:10 +0200
      Re: dpkg-buildpackage vs sbuild with python packaging Santiago Vila <sanvila@debian.org> - 2025-06-11 17:30 +0200
    Re: dpkg-buildpackage vs sbuild with python packaging Santiago Vila <sanvila@debian.org> - 2025-06-11 17:30 +0200
      Re: dpkg-buildpackage vs sbuild with python packaging Santiago Vila <sanvila@debian.org> - 2025-06-11 17:30 +0200
      Re: dpkg-buildpackage vs sbuild with python packaging Santiago Vila <sanvila@debian.org> - 2025-06-11 17:40 +0200
        Re: dpkg-buildpackage vs sbuild with python packaging PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2025-06-11 18:00 +0200
          Re: dpkg-buildpackage vs sbuild with python packaging Stefano Rivera <stefanor@debian.org> - 2025-06-11 18:30 +0200
      Re: dpkg-buildpackage vs sbuild with python packaging PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2025-06-11 17:50 +0200
      Re: dpkg-buildpackage vs sbuild with python packaging Peter Pentchev <roam@ringlet.net> - 2025-06-11 17:50 +0200
        Re: dpkg-buildpackage vs sbuild with python packaging Peter Pentchev <roam@ringlet.net> - 2025-06-11 18:00 +0200
        Re: dpkg-buildpackage vs sbuild with python packaging PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2025-06-11 18:10 +0200
    Re: dpkg-buildpackage vs sbuild with python packaging PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2025-06-11 17:30 +0200
      Re: dpkg-buildpackage vs sbuild with python packaging Stefano Rivera <stefanor@debian.org> - 2025-06-11 17:50 +0200
        Re: dpkg-buildpackage vs sbuild with python packaging PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2025-06-11 18:00 +0200
          Re: dpkg-buildpackage vs sbuild with python packaging thomas@goirand.fr - 2025-06-11 18:40 +0200
            Re: dpkg-buildpackage vs sbuild with python packaging Stefano Rivera <stefanor@debian.org> - 2025-06-11 18:40 +0200
              Re: dpkg-buildpackage vs sbuild with python packaging stefanor@debian.org - 2025-06-11 19:30 +0200
                Re: dpkg-buildpackage vs sbuild with python packaging stefanor@debian.org - 2025-06-12 11:30 +0200
                Re: dpkg-buildpackage vs sbuild with python packaging PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2025-06-12 11:50 +0200
                Re: dpkg-buildpackage vs sbuild with python packaging PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2025-06-12 11:40 +0200
              Re: dpkg-buildpackage vs sbuild with python packaging PICCA Frederic-Emmanuel <frederic-emmanuel.picca@synchrotron-soleil.fr> - 2025-06-11 19:40 +0200
              Re: dpkg-buildpackage vs sbuild with python packaging thomas@goirand.fr - 2025-06-11 20:50 +0200
        Re: dpkg-buildpackage vs sbuild with python packaging Peter Pentchev <roam@ringlet.net> - 2025-06-11 18:00 +0200

csiph-web