Thank you very much. It seems like a hit & miss indeed.
2/3 of packages can be added by adding python3-setuptools-scm... the other need more work I do like digging in random packages, I can do this at a slow rate, still this experience with "furo" help me triage the other packages (python3-can was different, I fixed it midway while doing a demo of something else) Greetings Le jeu. 6 nov. 2025, 10:34, Georges Khaznadar <[email protected]> a écrit : > Thank you for the bug report, Alexandre. > > Unfortunately, depending on python3-setuptooms-scm does not fix this > issue. > > I suspect that this issue is caused by the package build outside a > Git-controlled tree, and the lack of Git tag to get dynamically a valid > version number > (see > https://packaging.python.org/en/latest/discussions/single-source-version/#single-source-version > ) > > I fixed this bug by modifying debian/rules in order to tweak the file > pyproject.toml before the actual build and restore it upon cleaning the > build environment. The dynamic version stance is replaced by a static > one, with a version number extracted from debian/changelog. > > Best regards, Georges. > > Alexandre Detiste a écrit : > > Package: furo > > Version: 2025.09.25+dfsg-1 > > Severity: normal > > > > Dear Maintainer, > > > > The version metadata of this package is not correctly registered in > Debian. > > > > This may create problems if someone is usign 'pip install <something> > --break-my-system' > > (I know, but sometimes it's needed to fix things in a hurry) > > or if something else tries to read "furo"'s version and get a 0.0.0 > > > > A typical fix is to add a python3-setuptools-scm build dependency, > > but I did not checked here... yet > > > > Have a nice day > > > > Alexandre >
