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

Re: git-svn "cannot lock ref" error during fetch

From
JPJames Peach <jamespeach@mac.com>
Date
Jun 7, 2007, 15:37 UTC
Message-ID
<6C4E89FC-CE40-4A76-A297-E0AB7A1F2F75@mac.com>
In-Reply-To
<20070607063158.GA2809@muzzle>
On Jun 6, 2007, at 11:31 PM, Eric Wong wrote:
Show 28 quoted lines
> 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"?
unfortunately, there's more than one tag with this naming convention :(
>  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....

Aha! I don't really need 90% of the tags - is there a way I can tell the "git-svn fetch" not to bother with particular tags?

Previous: Lars HjemliNext: Eric Wong
Message 4 of 6 in “git-svn "cannot lock ref" error during fetch”
  1. James PeachJun 6, 2007
  2. Eric WongJun 7, 2007
  3. Lars HjemliJun 7, 2007
  4. James PeachJun 7, 2007
  5. Eric WongJun 9, 2007
  6. James PeachJun 13, 2007

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.