Re: git-svn fetch failure: index.lock file exists

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

 



Ollie Wild <aaw@xxxxxxxxxx> 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@xxxxxxxxxxx/svn/gcc/trunk =>
>       svn+ssh://aaw@xxxxxxxxxxx/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
-
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]

  Powered by Linux