You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If one runs cachi2 --version in context of the distributed container image, the version string is incorrect and it's incorrect on 2 fronts:
There's no trace of the actual tag that the image was built from whatsoever
$ podman run -it quay.io/konflux-ci/cachi2:0.20.0 --version
***cachi2 0.0.post1+g86764ba.d20250204***
For locally built images with podman it's just the post-release string that shouldn't even be there because the image was built from a particular tagged commit, so there is no post-release/post-tag commit other than the one we're building from
$ podman run -it localhost/cachi2:0.18.0 --version
cachi2 0.18.0.post0+g06180db6.d20250205
The text was updated successfully, but these errors were encountered:
To add a bit more context and confusion as well, if one tries to install a given tag simply with pip locally without building a container image, everything works as expected:
At this point I don't know what's happening in the background with setuptools-scm that it misbehaves during container builds, but works fine with plain python builds/installs in local dev environments.
If one runs
cachi2 --version
in context of the distributed container image, the version string is incorrect and it's incorrect on 2 fronts:The text was updated successfully, but these errors were encountered: