git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: James Peach <jamespeach@mac.com>
Cc: git@vger.kernel.org
Subject: Re: git-svn "cannot lock ref" error during fetch
Date: Wed, 6 Jun 2007 23:31:58 -0700	[thread overview]
Message-ID: <20070607063158.GA2809@muzzle> (raw)
In-Reply-To: <50C9688F-9C62-43AC-A84D-D84561671BAC@mac.com>

James Peach <jamespeach@mac.com> wrote:
> Hi all,
> 
> I'm new to git, and I'm experimenting with using git-svn to interact  
> with a large SVN repository with lots of branches.
> 
> I initially did an init like this:
> 
> git-svn init -t tags -b branches -T trunk svn+ssh://server/svn/project
> 
> Then I did a git-svn fetch, which started pulling all the branches.  
> After a while, however, it hit a branch that it couldn't pull:
> 
> Found branch parent: (tags/project-92~9)  
> 767f1f1601a4deae459c99ea6c1d1b9ba8f57a65
> Following parent with do_update
> ...
> Successfully followed parent
> fatal: refs/remotes/tags/project-92~9: cannot lock the ref
> update-ref -m r13726 refs/remotes/tags/project-92~9  
> 950638ff72acc278156a0d55baafbabb43f2b772: command returned error: 128
> 
> Some amount of searching failed to turn up any hints on what this  
> error means or how I can work around it. I'd appreciate any advice ...

Is there a tag actually named "project-92~9"?  If so, it's
an invalid branch name for git.  I started working on a way
around it by mapping new names to it, but haven't gotten around to
finishing it....

-- 
Eric Wong

  reply	other threads:[~2007-06-07  6:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-06 17:17 git-svn "cannot lock ref" error during fetch James Peach
2007-06-07  6:31 ` Eric Wong [this message]
2007-06-07  6:54   ` Lars Hjemli
2007-06-07 15:37   ` James Peach
2007-06-09 20:06     ` Eric Wong
2007-06-13 23:07       ` James Peach

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070607063158.GA2809@muzzle \
    --to=normalperson@yhbt.net \
    --cc=git@vger.kernel.org \
    --cc=jamespeach@mac.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).