From: Bjarni Ingi Gislason <bjarniig@rhi.hi.is>
To: git@vger.kernel.org
Subject: "git describe --debug" does not show the latest tag for "groff"
Date: Wed, 27 Oct 2021 23:31:01 +0000 [thread overview]
Message-ID: <20211027233101.GA762862@rhi.hi.is> (raw)
What did you do before the bug happened? (Steps to reproduce your issue)
I do not know, it could have happened anytime after the latest tag
was committed (11th Nov. 2020).
What did you expect to happen? (Expected behavior)
Seeing the latest tag "1.23.0.rc1" in the version string of "groff"
(and in the output of "git describe --debug")
What happened instead? (Actual behavior)
"groff --version" shows for example "1.22.4.3317-8f8c8-dirty"
"git describe --debug" shows:
describe HEAD
No exact match on refs or tags, searching to describe
finished search at 2ac1f9ba5578cad27dc547d5be3c91753db436ea
annotated 3318 1.22.4
annotated 3319 1.22.4.rc5
annotated 3352 1.22.4.rc4
annotated 3464 1.22.4.rc3
annotated 3485 1.23.0.rc1
annotated 3572 1.22.4.rc2
annotated 3619 1.22.3.rc1
traversed 3833 commits
1.22.4-3318-g3a1e750d
What's different between what you expected and what actually happened?
The latest tag is not shown for the groff version.
Anything else you want to add:
The latest tag in "git log" is 1.23.0.rc1 in my branch.
It is 1.23.0.rc1 in branch master.
Search for "tag:" in "git log" in my branch shows:
commit c05b538c504106d55b81caa6400ea80797f03775 (tag: 1.23.0.rc1)
Author: Bertrand Garrigues <...>
Date: Wed Nov 11 01:58:55 2020 +0100
"git show-ref 1.23.0.rc1" in my branch shows:
faa3dff8d011e61721e763c71b6ccbf20a4675bc refs/tags/1.23.0.rc1
####
"git-version-gen" (gnulib) does not get the latest tag.
The call in configure.am is:
AC_INIT([GNU Troff],[m4_esyscmd(build-aux/git-version-gen --prefix ""
.tarball-version)],[http://savannah.gnu.org/bugs/?group=g$
The files ".git/packed-refs" and ".git/info/refs" are the same in both
branches.
#####
[System Info]
git version 2.33.0 (Debian/testing Version: 1:2.33.0-1)
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
uname: Linux 5.14.9-2 #1 SMP Sun Oct 10 01:53:44 UTC 2021 x86_64
compiler info: gnuc: 10.2
libc info: glibc: 2.32
$SHELL (typically, interactive shell): /bin/bash
[Enabled Hooks]
--
Bjarni I. Gislason
next reply other threads:[~2021-10-27 23:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 23:31 Bjarni Ingi Gislason [this message]
2021-10-28 8:26 ` "git describe --debug" does not show the latest tag for "groff" Ævar Arnfjörð Bjarmason
2021-10-30 23:15 ` Bjarni Ingi Gislason
2021-10-31 0:12 ` Chris Torek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211027233101.GA762862@rhi.hi.is \
--to=bjarniig@rhi.hi.is \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).