Re: Wierd tag errors from current 'next'

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Andy Whitcroft <apw@xxxxxxxxxxxx> 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?

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]