Hi Julian, Julian Gilbey, on 2024-07-03: > Is there any chance that setting SETUPTOOLS_SCM_PRETEND_VERSION would > help?
Thanks for the hint, it sounded worth a try and I started a
build, including in d/rules:
include /usr/share/dpkg/pkg-info.mk
export SETUPTOOLS_SCM_PRETEND_VERSION = $(DEB_VERSION_UPSTREAM)
but early build steps tripped on 0+unknown anyway:
[…]
UPDATING build/lib/distributed/_version.py
set build/lib/distributed/_version.py to '0+unknown'
[…]
Version handling looks to originate from distributed/_version.py
which in turn is supposed to have been autogenerated somehow by
versionneer. Worst case scenario, I suppose it could be
possible to hardwire the package version at the following
location:
197 def git_versions_from_keywords(
198 keywords: dict[str, str],
199 tag_prefix: str,
200 verbose: bool,
201 ) -> dict[str, Any]:
[…]
262 return {
263 "version": "0+unknown",
264 "full-revisionid": keywords["full"].strip(),
265 "dirty": False,
266 "error": "no suitable tags",
267 "date": None,
268 }
but I'm not confident how this interferes with the other version
fields normally filled automatically after deriving the git tag.
Hope this gives some inspiration,
--
.''`. Étienne Mollier <[email protected]>
: :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da
`. `' sent from /dev/pts/3, please excuse my verbosity
`- on air: RPWL - Victim Of Desire
signature.asc
Description: PGP signature
