To be a little clearer:

There is an *empty* directory and in that directory we are cloning our 
repository when we get that message. No other processes are involved, the 
target directory ist created just before the cloning (two lines above in 
the build script) and then the "git clone" is executed.

I *really *have not idea what could be locking that file!

Interesting detail: The repository where that error happend ist perfectly 
OK afterwards, no files missing, all files in the correct version.

As a workaround i have setup our build engine to ignore a possible return 
code for that clone commands (not the best solution but because the 
repositories were OK, even after that error, i can live with it)

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
For more options, visit

Reply via email to