Hi,
Nobody answered yet, so I'll answer on the only one package I know
about: setuptools-git-versioning
I've been annoyed several times by package who don't return version
info through importlib.metadata;
enough to check the problem more deeply and fix what I could (by
adding python3-setuptools-scm most of the time)
The cases boil down to this:
apt-file search --filter-suites unstable,experimental --
'-0.0.0.' | grep -e egg-info -e dist-info | cut -d: -f1 | sort -u >
liste
Many of those will document an optional dependency on
setuptools-git-versioning and do fine without.
Some are patched out, see
https://codesearch.debian.net/search?q=setuptools-git-versioning&literal=1
- toolz
- the patch is needed becaue upstream depends on
setuptools-git-versioning, which is not available in Debian.
https://sources.debian.org/src/python-logistro/2.0.1+dfsg1-2/tests/test_version.py?hl=13#L13
So it seems a nice addition; but I'm not sure it would so much useful
as-is for regular packages.
We would most likely need glue similar to the "export
SETUPTOOLS_SCM_PRETEND_VERSION"
thing done by dh-python
Greetings
Alexandre
PS: theres is also this lintian request worth checking:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034588
Le ven. 29 mai 2026 à 15:03, Michele Cane <[email protected]> a écrit :
> setuptools-git-versioning:
> https://salsa.debian.org/heiserhorn/setuptools-git-versioning
>
> The following packages have been identified as direct or indirect
> dependencies of Rayforge (the list may not yet be exhaustive):
> Python:
> setuptools-git-versioning
