Your message dated Wed, 18 Feb 2026 17:38:09 +0100
with message-id <[email protected]>
and subject line Re: Bug#1052044: Without git, pybuild does not include data
files into wheel
has caused the Debian Bug report #1052044,
regarding Without git, pybuild does not include data files into wheel
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1052044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052044
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python3-build
Version: 0.10.0-1
Severity: important
Dear maintainer,
I am trying to build the package "asdf-wcs-schema"
https://salsa.debian.org/debian-astro-team/asdf-wcs-schemas
which includes a lot of metadata, f.e.
resources/manifests/gwcs-1.0.0.yaml
With the normal build procedure, the build does not include the data
files see f.e.
https://salsa.debian.org/debian-astro-team/asdf-wcs-schemas/-/jobs/4706731
I traced this down to the "python3 -m build" call, which is
python3.11 -m build --skip-dependency-check --no-isolation --wheel
--outdir
/builds/debian-astro-team/asdf-wcs-schemas/debian/output/source_dir/.pybuild/cpython3_3.11
Running this command locally on a system with just the build deps
installed does (with the environment variable
SETUPTOOLS_SCM_PRETEND_VERSION=0.2.0) not include the data files.
However, when I install the "git" package, the data files are included.
The packages uses pyproject.toml, and the data files are specified as
----------------------------8<-------------------------------
[tool.setuptools]
packages = ["asdf_wcs_schemas", "asdf_wcs_schemas.resources"]
[tool.setuptools.package-data]
"asdf_wcs_schemas.resources" = ["resources/**/*.yaml"]
[tool.setuptools.package-dir]
'' = "src"
"asdf_wcs_schemas.resources" = "resources"
----------------------------8<-------------------------------
which looks reasonable to me.
I am not sure if python3-build is the relevant package for the bug;
however I could not find out more from the output. Please re-assign if
required.
--- End Message ---
--- Begin Message ---
Hi Stefano,
the problem is that PyPI is not really the authorative source but built
from the Github repository. I specifically started to change all d/watch
files to point to Github instead of PyPI. The SOURCES.txt is a generated
artefact and not a source file, so relying on it would violate Debian
Policy which requires to build from the sources (which is defined as
"the preferred file to be edited").
What I will do now (first in asdf-coordinates-schema) is to include the
following snippet in d/rules:
execute_after_dh_auto_configure:
if [ -f MANIFEST.in ]; then mv MANIFEST.in MANIFEST.orig; fi
find . \( -path './.git' -o -path './debian' \) -prune -o -not -type d -printf
"include %P\n" > MANIFEST.in
if [ -f MANIFEST.orig ]; then cat MANIFEST.orig >> MANIFEST.in; fi
execute_after_dh_auto_clean:
rm -f MANIFEST.in
if [ -f MANIFEST.orig ]; then mv MANIFEST.orig MANIFEST.in; fi
This will create a MANIFEST.in with the files in a similar way
"setuptools_scm" would do (they use "git ls-files").
If that works well, I will adopt this for other packages where I observe
this.
Cheers
Ole
--- End Message ---
