[Buildbot-commits] [Buildbot] #2002: fatal: Could not parse object ...

[Buildbot]

#2002: fatal: Could not parse object ...
----------------------+------------------------
Reporter:  dabrahams  |       Owner:
    Type:  defect     |      Status:  new
Priority:  major      |   Milestone:  undecided
 Version:  0.8.4p1    |  Resolution:
Keywords:  git        |
----------------------+------------------------

Comment (by dustin):

 OK, so it looks like it's possible that the rev being built is only
 reachable from a branch, and not from a tag, in which case fetch --tags
 doesn't fetch the relevant commit.  I see the comments on the
 stackoverflow thread, too.

 However, I think that the use of '+master' fixes this.  At least, it does
 for me.  In a repository that was somewhat behind upstream, I ran

 {{{
 dustin at euclid ~/code/amanda/t/amanda [master] $ git fetch --tags zmanda
 +master
 remote: Counting objects: 153, done.
 remote: Compressing objects: 100% (52/52), done.
 remote: Total 114 (delta 92), reused 80 (delta 62)
 Receiving objects: 100% (114/114), 32.75 KiB, done.
 Resolving deltas: 100% (92/92), completed with 35 local objects.
 From http://github.com/zmanda/amanda
  * branch            master     -> FETCH_HEAD
 dustin at euclid ~/code/amanda/t/amanda [master] $ git reset --hard dcf864
 HEAD is now at dcf8647 * perl/Amanda/Taper/Scribe.pm: Correcly make label
 with meta and barcode
 }}}
 where dcf864 is the current rev of master at zmanda/amanda, and was a
 commit that wasn't in my repo before that time.  That rev is also not
 referenced by any tags in my repo or zmanda/amanda.  So there's something
 about this problem that I'm still missing here - any idea how to explain
 what I'm seeing?

-- 
Ticket URL: <http://trac.buildbot.net/ticket/2002#comment:2>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation