From: Junio C Hamano <junkio@cox.net>
Date: Sat, 25 Nov 2006 20:08:14 GMT
Subject: Re: Wierd tag errors from current 'next'
Message-ID: <7vu00n1e8h.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <456845E0.1050001@shadowen.org>

Andy Whitcroft <apw@shadowen.org> writes:

> I just was fetching some updates from a repository which I sync from CVS
> into my development repository.  I got the following wierd errors about
> a tag during the fetch, it seemed to fix itself by the end ... hmmmm.
>
> apw@pinky$ git fetch
> error: refs/tags/v0_72_3 does not point to a valid object!
> error: refs/tags/v0_72_3 does not point to a valid object!
> remote: Generating pack...
> remote: Done counting 42 objects.
> remote: Result has 28 objects.
> remote: Deltifying 28 objects.
> remote:  100% (28/28) done
> remote: Total 28, written 28 (delta 20), reused 20 (delta 12)
> Unpacking 28 objects
>  100% (28/28) done

That sounds as if we are checking the refs/tags/v0_72_3 before
we get the object itself.  "does not point to a valid object!"
message comes from do_one_ref() in refs.c which means your
repository had $GIT_DIR/refs/tags/v0_72_3 before that object was
retrieved.

Which is _bad_.  Could you reproduce and bisect it?