On Tue, Sep 16, 2025 at 02:22:20PM +0100, Ian Jackson wrote:
Package: git-debpush
Version: 13.14
Severity: minor
In t2u job 991, git-debpush selected a tag `v2.1.13` for upstream.
But that was a bare tag ref - that is, refs/tags/v2.1.13 points
directly to a commit, not a tag object.
This is an unusual thing for a maintainer to do.
Is this really all that unusual? It may be undesirable for one reason
or another, but in my world I very frequently see examples of both
lightweight and annotated tags being used to mark releases.
Random example which is not at all special, just the first place I
happened to look, and I found an example on the first try:
$ git clone https://github.com/PyO3/maturin
$ git -C maturin cat-file -t v1.11.5
commit
--
Colin Watson (he/him) [[email protected]]
