libgit2
Git tags for new versions are missing again
The latest release on RubyGems is 0.27.7, but the latest tag in this repository is 0.27.5. This is about the third time I’m reporting such issue, please automate this…
Please add this tag. It has been a month now!
I'm packaging this for Arch Linux and dependencies will fail... It is just lucky coincidence, that libgit2 has not been updated in our repositories, else this would break (e.g. #780 ).
@ethomson @carlosmn @vmg @schacon @arthurschreiber @brianmario I apologize up front for tagging you all, but I would really like to get some attention for this (seemingly longstanding and reoccuring) issue. I'm unsure, who is mainly maintaining this code base and doing the releases to rubygems.org (I cross-referenced your user names here and there).
Having a discrepancy in versioning between here and on rubygems.org is not good.
It is intransparent (and unreproducible) which commit since 0.28.0 is the 0.28.1 release on rubygems.org.
Quite a few of the released versions are missing as tags!
As I'm packaging rugged for a Linux distribution, I am building from source (using a release tarball from github). However, in its current state I can not build the version that is available on rubygems.org!
Please tag 0.28.1 appropriately and in the future first tag a version in this repository and only then release that tagged version as a gem to rubygems.org. Only this can ensure transparency and reproducibility, as well as version parity for distributions, building rugged from source (or anyone attempting that really).
@ethomson @carlosmn @vmg @schacon @arthurschreiber @brianmario Sorry to ping you again, but I'd really like to get an answer to this, as it is a serious problem (not only for myself).
And tag v0.28.3 has an incorrect version in the gemspec (imported from lib/rugged/version.rb). The incompetence of this gem’s maintainers is really outstanding. >_<
@carlosmn The tag for 1.1.1 is missing.
Can this recurring issue please be solved by e.g. creating the gem in CI and pushing it after a version was tagged (as proposed two years ago)? That would be most awesome and we could finally close this ticket.