Re: Clarifying "invalid tag signature file" error message from git filter-branch (and others)

From: Brandon Casey <casey@nrlssc.navy.mil>
Date: Dec 12, 2008, 16:21 UTC
Message-ID: <ivc7ylNVmqD2RhGdI10MyG1ySwq00RZSzeh_UXbU05mhkw5od1QN8Q@cipher.nrlssc.navy.mil>
In-Reply-To: <c5df85930812111559p287ea6afk54a9759302288d5e@mail.gmail.com>

James Youngman wrote:

Show 22 quoted lines

> On Thu, Dec 11, 2008 at 11:13 PM, Brandon Casey <casey@nrlssc.navy.mil> wrote:
> 
>>> Before conversion:
>>> $ git cat-file tag FINDUTILS-4_1-10
>>> object ce25eb352de8dc53a9a7805ba9efc1c9215d28c2
>>> type commit
>>> tag FINDUTILS-4_1-10
>>> tagger Kevin Dalley
>> The tagger field is missing an email address, a timestamp, and a timezone. It
>> should look something like:
>>
>>  tagger Kevin Dalley <kevin.dalley@somewhere.com> 1229036026 -0800
>>
>> git-mktag prevents improperly formatted tags from being created by checking
>> that these fields exist and are well formed.
>>
>> If you know the correct values for the missing fields, then you could
> 
> Yes for the email address.      But as for the timestamp, it's not in
> the tag file; that only contains the sha1.
> There is a timestamp in the object being tagged, is that the timestamp
> you are talking about?

Yes and no. I meant that if you knew the "real" timestamp, possibly by extracting it from the original repository, then you can use that. Otherwise yes, as a workaround, use the timestamp in the object being tagged.

Show 6 quoted lines

> $ git show --pretty=raw  ce25eb352de8dc53a9a7805ba9efc1c9215d28c2
> commit ce25eb352de8dc53a9a7805ba9efc1c9215d28c2
> tree 752cca144d39bc55d05fbe304752b274ba22641c
> parent 9a998755249b0c8c47e8657cff712fa506aa30fc
> author Kevin Dalley <kevin@seti.org> 830638152 +0000
> committer Kevin Dalley <kevin@seti.org> 830638152 +0000

The committer information should be used, though in this repository it will probably always be the same as the author.

-brandon