git versioning tags not explained

• I have searched the issues of this repo and believe that this is not a duplicate.

Issue

Can somebody explain the difference between:

uberdbutils (0.0.22 git branch master)

and

uberdbutils (0.0.22 git rev master)

Especially as it produces a conflict that makes it impossible to upgrade a package:

Because uber-schema (2.1.1) depends on uberdbutils (0.0.22 git rev master) and no versions of uber-schema match >2.1.1,<3.0.0, uber-schema (>=2.1.1,<3.0.0) requires uberdbutils (0.0.22 git rev master). So, because grants-pipeline depends on both uberdbutils (0.0.22 git branch master) and uber-schema (^2.1.1), version solving failed. The package blocks for uberdbutils btw in poetry.lock in grants-pipeline & uber-schema are exactly the same.

So this is driving my crazy, uberdbutils is referenced by uber-schema & grants-pipeline in pyproject.toml & poetry.lock exactly the same, but poetry calls it 0.0.22 git rev master here and 0.0.22 git branch master there???

(And no, there have been no commits to uberdbutils has not been updated in 18 months.

[rambo]

After some more investigation it seems it makes all the difference if we point to the dep with {git = "[e-mail]:orgname/reponame.git", tag="0.3.2"} or {git = "ssh://[e-mail]/orgname/reponame.git", tag="0.3.2"}, mixing forms will cause this issue, using the first from everywhere will prevent it and I have not tested using the second form everywhere since I would have to update to other packages too for that.

[yacc143]

Btw, please note, poetry had no problem to find the initial version of the packages involved, it just refuses to upgrade them because of the common git repo dependency. Weep.