From: Paul Vincent Craven <hidden> Date: 2016-06-15 22:46:34
When I do a git-push from a repository I set up, I get:
craven@craven-desktop:~/docs$ git push
Unable to create branch path
http://username:password@server.simpson.edu/my_repo.git/info
Error: cannot lock existing info/refs
error: failed to push some refs to
'http://username:password@server.simpson.edu/my_repo.git/'
The web log shows:
10.1.21.232 - username [06/Apr/2009:21:24:04 -0500] "PROPFIND
/my_repo.git/ HTTP/1.1" 207 559 "-" "git/1.5.6.3"
10.1.21.232 - username [06/Apr/2009:21:24:04 -0500] "HEAD
/my_repo.git/info/refs HTTP/1.1" 200 - "-" "git/1.5.6.3"
10.1.21.232 - username [06/Apr/2009:21:24:04 -0500] "HEAD
/my_repo.git/objects/info/packs HTTP/1.1" 200 - "-" "git/1.5.6.3"
10.1.21.232 - username [06/Apr/2009:21:24:04 -0500] "MKCOL
/my_repo.git/info HTTP/1.1" 301 383 "-" "git/1.5.6.3"
10.1.21.232 - - [06/Apr/2009:21:24:04 -0500] "MKCOL /my_repo.git/info/
HTTP/1.1" 401 536 "-" "git/1.5.6.3"
Note that after the 301 redirect, I don't seem to have a username sent
anymore. I'm not sure this is the issue, but is seems like a
possibility.
I have the same issue on other computers that have cloned the repository.
The /my_repo.git/info/ directory does exist.
I thought I had this working the first day I set it up, but now it no
longer does. If someone could point me in the correct direction, I'd
appreciate it.
--
Paul Vincent Craven
From: Martin Storsjö <hidden> Date: 2016-06-15 22:46:34
Hi Paul,
On Mon, 6 Apr 2009, Paul Vincent Craven wrote:
Note that after the 301 redirect, I don't seem to have a username sent
anymore. I'm not sure this is the issue, but is seems like a
possibility.
I have the same issue on other computers that have cloned the repository.
The /my_repo.git/info/ directory does exist.
I thought I had this working the first day I set it up, but now it no
longer does. If someone could point me in the correct direction, I'd
appreciate it.
It's a long shot, but try see if you can upgrade to a newer version of
libcurl; I think I saw some issue like this when I was experimenting with
different http auth setups last week, that was solved by using newer
versions...
// Martin
From: Paul Vincent Craven <hidden> Date: 2016-06-15 22:46:34
On Tue, Apr 7, 2009 at 2:42 AM, Martin Storsjö [off-list ref] wrote:
It's a long shot, but try see if you can upgrade to a newer version of
libcurl; I think I saw some issue like this when I was experimenting with
different http auth setups last week, that was solved by using newer
versions...
No luck, but thanks for the suggestion. Updating to the March 3 build
of curl 7.19.4 yielded the same results.
--
Paul Vincent Craven
http://www.cravenfamily.com