[SM-Commit] Can't push, lock file borkage.
jblosser-smgl at firinn.org
Sun Aug 6 22:09:32 EDT 2006
I'll look at it. I don't think PugMajere knows what he's talking about,
though. We aren't adding locks ourselves anywhere.
On Aug 07, Juuso Alasuutari [iuso at sourcemage.org] wrote:
> I was pushing a commit as usual, but aborted when it seemed to hang
> indefinitely. Now I get this error when trying to push:
> error: unable to create refs/heads/master.lock (File exists)
> ng refs/heads/master can't lock
> Apparently there's a lock file on the server that's blocking all pushes now.
> So in case you're making sounds like this...
> 02:48 <+dmlb2000> Bah! who locked test grimoire!!! grrr
> ...this short discussion I just had on #git might clarify things:
> 02:24 < iuso> did 'git push origin master' like usual, it hung. ctrl-c'd, now
> attempting to push and complains about an existing lock file,
> although i can't find any such file or other .lock files
> 02:49 < PugMajere> iuso: The lockfile may be on the server (in fact, it
> probably is)... I don't think a normal push uses a
> so maybe it's a site customization?
> 02:49 < PugMajere> Is that a shared repository you were pushing to?
> 02:49 < iuso> i don't know
> 02:50 < PugMajere> iuso: Did you create the repository? Do other people also
> push into it?
> 02:50 < iuso> it's in wide use yes
> 02:50 < iuso> the Source Mage test grimoire repo
> 02:50 < PugMajere> iuso: Ah, yes.
> 02:50 < PugMajere> I suspected as much.
> 02:51 < PugMajere> Normal git push does no locking on the remote repository,
> because, well, "normal" practice is that there isn't a
> shared repository.
> 02:51 < PugMajere> So there's something custom in the hooks that repository is
> setup with.
> 02:51 < iuso> alright
> 02:51 < PugMajere> If you have normal shell access to it, look in .git/hooks/
> and see what it's trying to do, and cleanup whatever mess
> your ctrl-c did.
> 02:51 < iuso> i guess i'll have to ask someone who has access to do something
> with the lock file
> 02:52 < PugMajere> They should also fix the script to prevent it from doing
> this again. :)
> What's strange is that I received an SM-Commit mail for the commit I was
> attempting to push (new spell mxml), but there hasn't been anything
> #sourcemage-commits. What's that about?
> Sorry for the mess.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 232 bytes
Desc: not available
Url : http://lists.ibiblio.org/pipermail/sm-commit/attachments/20060806/bc145da6/attachment.bin
More information about the SM-Commit