[+mailing list, so others can also chime in and have an answer/opinion]
On Mon, Apr 27, 2015 at 10:07 AM, Adam Steel [off-list ref] wrote:
Stefan,
So I switched git versions.
$ git --version
git version 2.3.1
I'm still getting the same regular rebase failures.
---
fatal: Unable to create
'/Users/asteel/Repositories/rails-teespring/.git/index.lock': File
exists.
If no other git process is currently running, this probably means a
git process crashed in this repository earlier. Make sure no other git
process is running and remove the file manually to continue.
---
Any ideas?
Adam
On Tue, Apr 21, 2015 at 12:34 PM, Stefan Beller [off-list ref] wrote:
quoted
[+mailing list]
On Tue, Apr 21, 2015 at 11:20 AM, Adam [off-list ref] wrote:
quoted
I'm using git version 2.3.2 (Apple Git-55).
We should loop in the maintainers of the Apple Git version, they'd know
what changed in git about two weeks ago.
I have no idea who that is though.
quoted
That explains why I can't find the index.lock file, since the error that was
thrown deleted it. I'm still not sure what to do about this, though.
Complain at the right people so it gets fixed. ;)
quoted
Thanks for responding.
Adam
On Mon, Apr 27, 2015 at 10:07 AM, Adam Steel [off-list ref] wrote:
quoted
Stefan,
So I switched git versions.
$ git --version
git version 2.3.1
I'm still getting the same regular rebase failures.
---
fatal: Unable to create
'/Users/asteel/Repositories/rails-teespring/.git/index.lock': File
exists.
Is the repository located on a mounted network share, or could other
users be accessing it via a network mount? We had a similar problem
recently on a new Jenkins VM instance which had only NFS-mounted
storage available. I don't remember if it was Git that was failing on
there, and I wasn't directly involved in solving the problem. But
while researching the issue I found ominous warnings about the dangers
of file-locking on remote shares [1]. Which is to say, I don't know
much, but I heard a rumor... :-)
Perhaps this is old news and already well covered in Git. But I am curious...
[1] http://0pointer.de/blog/projects/locking.html
Nope, this is local on an OSX system with only one user, no local
network. This happens about every third interactive rebase.
On Wed, Apr 29, 2015 at 9:14 AM, Phil Hord [off-list ref] wrote:
quoted
On Mon, Apr 27, 2015 at 10:07 AM, Adam Steel [off-list ref] wrote:
quoted
Stefan,
So I switched git versions.
$ git --version
git version 2.3.1
I'm still getting the same regular rebase failures.
---
fatal: Unable to create
'/Users/asteel/Repositories/rails-teespring/.git/index.lock': File
exists.
Is the repository located on a mounted network share, or could other
users be accessing it via a network mount? We had a similar problem
recently on a new Jenkins VM instance which had only NFS-mounted
storage available. I don't remember if it was Git that was failing on
there, and I wasn't directly involved in solving the problem. But
while researching the issue I found ominous warnings about the dangers
of file-locking on remote shares [1]. Which is to say, I don't know
much, but I heard a rumor... :-)
Perhaps this is old news and already well covered in Git. But I am curious...
[1] http://0pointer.de/blog/projects/locking.html