git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Wierd tag errors from current 'next'

From
Junio C Hamano <junkio@cox.net>
Date
Nov 25, 2006, 20:08 UTC
Message-ID
<7vu00n1e8h.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<456845E0.1050001@shadowen.org>
Andy Whitcroft <apw@shadowen.org> writes:
Show 15 quoted lines
> 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?
Previous: Andy Whitcroft
Message 2 of 2 in “Wierd tag errors from current 'next'”
  1. Andy WhitcroftNov 25, 2006
  2. Junio C HamanoNov 25, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.