Hi Gianfranco (2026.02.12_20:31:57_+0000)
There are a number of affected packages in sid, but I think there is
more than one cause:
python3-agate
- 1.14.1-1 migrated to pybuild-plugin-pyproject
uses: tool.setuptools.packages.find with exclude
python3-aioraven
- NEW
python3-azure
- Appears between 2025-11-18 20:16:40 and 2025-12-02 17:37:24
- In azure-ai-agentserver-agentframework
which uses tool.setuptools.packages.find with exclude both before and after
python3-django-pipeline
- Appears between 2025-10-23 14:47:02 and 2026-01-18 14:58:54
uses: tool.setuptools.packages.find with exclude
python3-geoalchemy2
- Appears between 2024-10-17 05:43:36 and 2025-02-16 15:37:51
still using old setup.py workflow
python3-pyunitsystem
- Always present
uses: tool.setuptools.packages.find with where=.
python3-pyvlx
- Appears between 2026-01-27 01:02:57 and 2026-02-12 13:29:42
which migrates from setup.py to pyproject.toml
uses: tool.setuptools.packages.find with exclude
python3-readme-renderer
- Appears between 2025-09-26 09:12:44 and 2025-12-31 15:30:10
uses: tool.setuptools.packages.find with exclude
python3-sqlalchemy-i18n
- Appears between 2021-11-08 10:34:13 and 2024-11-14 06:43:22
python3-tqdm
- Appears between 2025-11-30 19:04:18 and 2026-02-02 05:13:59
uses: tool.setuptools.packages.find with exclude
python3-zwave-js-server-python
- Appears between 2025-08-09 06:52:07 and 2026-01-17 14:29:57
uses: tool.setuptools.packages.find with exclude
Some of these ahve been around for years, but many appear when we
started to support Python 3.13 and Python 3.14. I played around with
pyunitsystem and confirmed that it's the double-build that's triggering
this.
The most likely cause is https://github.com/pypa/setuptools/issues/2688
We have a built-in exclude for "build" in setuptools, but not "build.*"
I suspect the best solution here is for us to implement #1124699
Stefano
--
Stefano Rivera
http://tumbleweed.org.za/
+1 415 683 3272
