* Stefano Rivera: " Re: pybuild and setuptools_scm" (Tue, 16 Jul 2024 03:06:53 +0000):
Hi Stefano, thanks for looking into it. > > I had a similar problem when setuptools_scm kicked in during the build > > process and produced versions different from the orig tarball. Packaging is > > in git and tarballs are imported from PyPI. > > > > I disabled the automatic versioning with > > > > https://salsa.debian.org/tryton-team/python-csb43/-/commit/e8788e09818948231a48cc1472a5f54444b65fcc > > > > Could you confirm this is the right approach or is there a more elegant > > way? > > That approach doesn't look great. > > Instead of that patch, just Build-Depend on python3-setuptools-cm, so > that it can do its magic. In my testing it works just fine on your > package. I have no clue why this is working for you. I removed the patch, tried your proposal and the build just fails because setuptools-scm writes again a dev version to src/csb43/_version.py: https://salsa.debian.org/tryton-team/python-csb43/-/jobs/5988081 dpkg-source: info: local changes detected, the modified files are: source_dir/src/csb43/_version.py But SETUPTOOLS_SCM_PRETEND_VERSION like proposed by Thomas did the trick. https://salsa.debian.org/tryton-team/python-csb43/-/pipelines/703025 May be pybuild doesn't handle correctly a version string like 0.10.0+dfsg-1? > Oh, you're also missing pytest, so the package tests are failing. Thanks! Mathias -- Mathias Behrle PGP/GnuPG key availabable from any keyserver, ID: 0xD6D09BE48405BBF6 AC29 7E5C 46B9 D0B6 1C71 7681 D6D0 9BE4 8405 BBF6
