From: "aaron smith" <beingthexemplarylists@gmail.com>
To: git@vger.kernel.org
Subject: git push question.. error: Unable to lock remote branch refs/heads/master
Date: Wed, 31 Dec 2008 00:17:35 -0800 [thread overview]
Message-ID: <d7ac1a680812310017o4316b719qae5af166a95d9940@mail.gmail.com> (raw)
Hey All,
First, i've looked all over for a solution to this, and can't seem to
get it figured out. Here's my setup:
centeos
apache 2
webdav
git 1.6.1
I went through most of the git config over http text file instructions
(http://www.kernel.org/pub/software/scm/git/docs/howto/setup-git-server-over-http.txt),
just for the quick and dirty. Here's what I have in my http conf:
<VirtualHost *:80>
ServerName www.codeendeavor.com
DocumentRoot /var/www/vhosts/codeendeavor/
DavLockDB /var/logs/httpd/webdav/davlock
<Location "/guttershark.git/">
DAV on
</Location>
</VirtualHost>
So, I have a bare git repo here:
/var/www/vhosts/codeendeavor/guttershark.git/ (I used: mkdir
guttershark.git; cd guttershark.git; git --bare init). And I've turned
on webdav for that location.
I created the DavLockDB directory: mkdir /var/logs/httpd/webdav/davlock
And I've updated permissions on the git repo, and the webdav lock to
apache:apache. And when it still didn't work, I updated the
permissions on the git repo to 777, and on the davlock.
I'm not sure what would be going on. I searched through the servers'
empty git, and my local git repo for a lock file. But don't see
anything.
I don't have authentication on it yet so if you want to try and push
to it, feel free.
After all that. here is how I interact with it:
$git push origin master
Unable to lock remote branch refs/heads/master
error: failed to push some refs to 'http://codeendeavor.com/guttershark.git/'
Anyone have any idea?
Thanks a bunch!
next reply other threads:[~2008-12-31 8:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-31 8:17 aaron smith [this message]
2008-12-31 8:22 ` git push question.. error: Unable to lock remote branch refs/heads/master aaron smith
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=d7ac1a680812310017o4316b719qae5af166a95d9940@mail.gmail.com \
--to=beingthexemplarylists@gmail.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).