The last git tag in https://gitweb.gentoo.org/proj/portage-utils.git/ is v0.65, but there are apparently releases up to 0.70 now. Please push the git tags to the repo as appropriate and matching to the releases. Hopefully just forgotten git push --tags.
I forgot --push-tags, the release scripts prevents from using a tag, so the tag is always in place, it's just that I never got git for not pushing it by default :)
1) v0.66..v0.69 tags are still missing 2) I don't understand what this v0.70 tag points at. It doesn't appears to be a commit on master branch (and that's the only remote branch...)
Looks like you haven't pushed the branch. I think --push-tags doesn't push the normal stuff to your tracked branch, just tags. Concern about missing tags for earlier releases remains after that master branch push is remedied.
Oh, those tags don't exist :) I made a leap-jump, because the amount of fixes/changes warrants that. I don't get much what gitweb is doing with the v0.70 tag page, but the commit it points to seems to exist (https://gitweb.gentoo.org/proj/portage-utils.git/commit/?h=v0.70&id=975186ebc35cc417c198ec922bcbc77226cdb05f)? I might not get what you want here. From here, it looks like I pushed everything there is, and the tag points to something: * commit 975186ebc35cc417c198ec922bcbc77226cdb05f (HEAD -> master, tag: v0.70, origin/master, origin/HEAD) | Author: Fabian Groffen <grobian@gentoo.org> | Date: Thu Apr 5 20:46:03 2018 +0200 | | make-tarball: use numeric uid/gid
Oh, I may actually have failed to push the last bunch of commits due to a gpg failure. % git push --signed error: gpg failed to sign the data fatal: failed to sign the push certificate This happens every once in a while, and I don't always spot it. It's pushed now, sorry.
I think everything is cleared up now.
