From: Eric Wong <normalperson@yhbt.net>
To: Ollie Wild <aaw@google.com>
Cc: git@vger.kernel.org
Subject: Re: git-svn fetch failure: index.lock file exists
Date: Sat, 17 Nov 2007 13:15:49 -0800 [thread overview]
Message-ID: <20071117211549.GC31598@mayonaise> (raw)
In-Reply-To: <65dd6fd50711151607x50639232w6d79322129c3d82@mail.gmail.com>
Ollie Wild <aaw@google.com> wrote:
> Hi,
>
> I've been using git-svn for a while now to work on gcc. Last night, I did a
>
> git svn fetch
>
> and got the following failure:
>
> Found possible branch point: svn+ssh://aaw@gcc.gnu.org/svn/gcc/trunk =>
> svn+ssh://aaw@gcc.gnu.org/svn/gcc/tags/libbid-last-merge, 128810
> Found branch parent: (tags/libbid-last-merge)
> 789aa951bbc6a49f791bf5109136335fc33222c5
> fatal: unable to create
> '.git/svn/tags/libbid-last-merge/index.lock': File exists
> read-tree 789aa951bbc6a49f791bf5109136335fc33222c5:
> command returned error: 128
>
> Naively, it looks to me like I've just got a stale lock file from a
> previous run. However, I have no idea what the correct recovery
> strategy is. Can I just delete the lock file? Do I need to do some
> sort of data validation?
>
> I'm using git version 1.5.2.5 with subversion version 1.4.5 (r25188).
Did you interrupt git-svn in a previous run? But you should be able to
just remove it; git-svn should verify that the index is in a consistent
state before it attempts to fetch again.
--
Eric Wong
next prev parent reply other threads:[~2007-11-17 21:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 0:07 git-svn fetch failure: index.lock file exists Ollie Wild
2007-11-17 21:15 ` Eric Wong [this message]
2007-11-26 7:59 ` Ollie Wild
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=20071117211549.GC31598@mayonaise \
--to=normalperson@yhbt.net \
--cc=aaw@google.com \
--cc=git@vger.kernel.org \
/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).