From: Alan Larkin <nobrow@eircom.net>
To: git@vger.kernel.org
Subject: Re: setting up a git repo on apache
Date: Thu, 10 Aug 2006 10:43:06 +0100 [thread overview]
Message-ID: <44DAFFAA.9040507@eircom.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0608091831320.1800@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin wrote:
> Hi,
>
> On Wed, 9 Aug 2006, Alan Larkin wrote:
>
>> $ git push http://localhost:/webdav/git/myproj master
>> Error: no DAV locking support on remote repo
>
> What do the access_log and the error_log say about this?
>
> It could also be that you have a "Require valid-user" somewhere in there
> by mistake.
>
> Further, you might want to check if it works _with_ authentication (I
> never tried without, and I am not sure if it should be allowed to begin
> with).
>
> There is a recent thread by Junio, Rutger and me, which might help you:
>
> http://thread.gmane.org/gmane.comp.version-control.git/24816/focus=24861
>
> Hth,
> Dscho
>
>
>
For the record, I followed the steps in the above linked thread as
closely as possible but the problem persists. It did however contain the
suggestion to use litmus to test the webdav and thats proving curious
insofar as several tests are failing, but in a not entirely reproducible
way. I mean, on one test I might see
14. cond_put.............. FAIL (PUT conditional on lock and etag
failed: 412 Precondition Failed)
15. fail_cond_put......... pass
16. cond_put_with_not..... pass
17. cond_put_corrupt_token WARNING: PUT failed with 400 not 423
...................... pass (with 1 warning)
18. complex_cond_put...... FAIL (PUT with complex conditional failed:
412 Precondition Failed)
and if run again I might see
14. cond_put.............. pass
15. fail_cond_put......... pass
16. cond_put_with_not..... pass
17. cond_put_corrupt_token WARNING: PUT failed with 400 not 423
...................... pass (with 1 warning)
18. complex_cond_put...... FAIL (PUT with complex conditional failed:
412 Precondition Failed)
and on another a different combination.
But this has no real place here, so I shall off and try find the
solution elsewhere and post back if its relevant.
Thanks for the help.
next prev parent reply other threads:[~2006-08-10 9:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 15:58 setting up a git repo on apache Alan Larkin
2006-08-09 16:35 ` Johannes Schindelin
2006-08-09 17:01 ` Alan Larkin
2006-08-10 9:43 ` Alan Larkin [this message]
2006-08-09 16:43 ` Rutger Nijlunsing
2006-08-09 17:02 ` Alan Larkin
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=44DAFFAA.9040507@eircom.net \
--to=nobrow@eircom.net \
--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).