[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: How to update the version that "git-version-gen" generates
From: |
G. Branden Robinson |
Subject: |
Re: How to update the version that "git-version-gen" generates |
Date: |
Wed, 27 Oct 2021 17:53:13 +1100 |
User-agent: |
NeoMutt/20180716 |
At 2021-10-26T15:49:03+0000, Bjarni Ingi Gislason wrote:
> My current version (from "git describe") is "1.22.4-3311-g37ef8583".
That's very strange to me. Are you working on a private branch and
rebasing/merging/cherry-picking from 'master'?
As far as I know, groff 1.22.4 never reached a commit count of over
three thousand before a subsequent tag was generated on master.
I work directly off of master most of the time[1]. Here's the .version
file from my working tree.
$ cat .version
1.23.0.rc1.1465-2b3e0
> There are two tmac-files that test for version "1.23" or later, so
> they abort the processing.
>
> I do not have a ".tarball-version" file. If I create it with content
> "1.24.rc1" the created versions are always the same as that.
As I understand it, that file is only created by the "dist" make(1)
target.
> The latest commit with a tag is
>
> commit c05b538c504106d55b81caa6400ea80797f03775 (tag: 1.23.0.rc1)
> Author: Bertrand Garrigues <...>
> Date: Wed Nov 11 01:58:55 2020 +0100
That's what I have as well (it's signed, too).
You might consider cloning a fresh copy of the repository in some other
directory and see what you get there.
Regards,
Branden
[1] apart from my unfortunate experience on dev-gropdf-boxes :|
signature.asc
Description: PGP signature