You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by "Wyss Clemens (Helbling Technik)" <cl...@helbling.ch> on 2008/01/09 19:48:54 UTC
FW: "svn merge" on https(sspi authenticated) repo does not work...
As suggested by Stefan(see below), I report this bug to this mailingslist:
looks like "svn merge" does not work on an https(sspi authenticated) repository.
When I try to revert:
D:\projects\testrepo>"c:\Program Files\TortoiseSVN\bin\svn.exe" merge -r2:1 https://scmserver/svn_sspi/testrepo/test.txt D:\projects\testrepo\test.txt
I get:
svn: PROPFIND request failed on '/svn_sspi/testrepo/test.txt'
svn: Server sent unexpected return value (401 Authorization Required) in response to PROPFIND request for '/svn_sspi/testrepo/test.txt'
All other svn operations seem to work on the sspi repo.
Thanks for your help
Clemens
-----Original Message-----
From: Stefan Küng [mailto:tortoisesvn@gmail.com]
Sent: Mittwoch, 9. Januar 2008 19:10
To: dev@tortoisesvn.tigris.org
Subject: Re: "Revert to this revision" (on https(i.e. WebDAV over ssl) repo) does not work...
Wyss Clemens (Helbling Technik) wrote:
> I am using nightly build TSVN(11836).
> When I try to revert to a specific revision on my https-repo(sspi
> authenticated) I get:
>
>> Merging revisions HEAD-1 of
> https://scmserver/svn_sspi/testrepo/test.txt
>> into D:\projects\testrepo\test.txt, respecting ancestry PROPFIND
>> request failed on '/svn_sspi/testrepo/test.txt'
>> Server sent unexpected return value (401 Authorization Required) in
> response to
>> PROPFIND request for '/svn_sspi/testrepo/test.txt'
>
> All other STVN operations work as expected.
>
> "Revert to this revision" works on my parallel http(basic auth) repo,
> though. Hence it must have to do with the ssl/sspi
> communication/authentication.
Please install the latest nightly build, then get the corresponding svn.exe from the nightly build folder
(http://nightlybuilds.tortoisesvn.net/latest/win32/svn.exe) and copy it in the c:\program files\TortoiseSVN\bin folder.
Open a console window, cd to your working copy, then enter
c:\program files\TortoiseSVN\bin\svn.exe merge -rHEADREV-1 https://scmserver/svn_sspi/testrepo/test.txt D:\projects\testrepo\test.txt
with HEADREV being the current HEAD revision.
If you get the same error, please report this to the svn dev list (dev at subversion tigris org), best including your test repository and of course a detailed description of what you were doing.
> BTW: can we now use sspi without ssl?
No, as mentioned before: neon has this deactivated.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
RE: FW: "svn merge" on https(sspi authenticated) repo does not work...
Posted by "Wyss Clemens (Helbling Technik)" <cl...@helbling.ch>.
can anybody else reproduce this sspi mis-behavior?
Yesterday, one of my team-members reported an "equal"(ie 401) problem/error. He tried to commit a folder with files after having added the
folder/files(see svn_commit.png and svn_commit_1.4.99.png). The problem could only be resolved by relocating the wc to the basic auth repo.
My apache log(error_log) reveils the following:
merge issue:
[Wed Jan 09 20:31:57 2008] [error] [client 192.168.68.2] The requested report is unknown. [501, #200007]
[Wed Jan 09 20:31:58 2008] [error] [client 192.168.68.2] (OS 87)The parameter is incorrect. : authentication failure for "/svn_sspi/testrepo/test.txt": user unknown, reason: cannot generate context
...
[Sat Jan 12 09:16:10 2008] [error] [client 192.168.68.3] The requested report is unknown. [501, #200007]
[Sat Jan 12 09:16:10 2008] [error] [client 192.168.68.3] (OS 87)The parameter is incorrect. : authentication failure for "/svn_sspi/testrepo/test.txt": user unknown, reason: cannot generate context
[Sat Jan 12 09:16:13 2008] [error] [client 192.168.68.3] The requested report is unknown. [501, #200007]
[Sat Jan 12 09:16:13 2008] [error] [client 192.168.68.3] (OS 87)The parameter is incorrect. : authentication failure for "/svn_sspi/testrepo/test.txt": user unknown, reason: cannot generate context
recursive commit issue:
[Fri Jan 11 13:44:41 2008] [error] [client 192.168.132.164] (OS 87)The parameter is incorrect. : authentication failure for "/svn_sspi/kaba_ratp/!svn/wrk/d3cfbb5e-eff9-cf4f-bfd5-b5429075dcaa/trunk/Source/PTEServerApplication/RSDeviceSettings.h": user unknown, reason: cannot generate context
[Fri Jan 11 13:44:42 2008] [error] [client 192.168.132.164] (OS 87)The parameter is incorrect. : authentication failure for "/svn_sspi/kaba_ratp/!svn/act/d3cfbb5e-eff9-cf4f-bfd5-b5429075dcaa": user unknown, reason: cannot generate context
[Fri Jan 11 14:59:56 2008] [error] [client 192.168.132.164] (OS 87)The parameter is incorrect. : authentication failure for "/svn_sspi/kaba_ratp/!svn/wrk/da7d43a9-915b-704c-a45b-3bc8c04a0472/trunk/Source/PTEServerApplication/res/Fault_FAT.bmp": user unknown, reason: cannot generate context
[Fri Jan 11 14:59:57 2008] [error] [client 192.168.132.164] (OS 87)The parameter is incorrect. : authentication failure for "/svn_sspi/kaba_ratp/!svn/act/da7d43a9-915b-704c-a45b-3bc8c04a0472": user unknown, reason: cannot generate context
> -----Original Message-----
> From: Wyss Clemens (Helbling Technik)
> [mailto:clemens.wyss@helbling.ch]
> Sent: Wednesday, January 09, 2008 8:49 PM
> To: dev@subversion.tigris.org
> Subject: FW: "svn merge" on https(sspi authenticated) repo
> does not work...
>
> As suggested by Stefan(see below), I report this bug to this
> mailingslist:
> looks like "svn merge" does not work on an https(sspi
> authenticated) repository.
> When I try to revert:
>
> D:\projects\testrepo>"c:\Program
> Files\TortoiseSVN\bin\svn.exe" merge -r2:1
> https://scmserver/svn_sspi/testrepo/test.txt
> D:\projects\testrepo\test.txt
>
> I get:
>
> svn: PROPFIND request failed on '/svn_sspi/testrepo/test.txt'
> svn: Server sent unexpected return value (401 Authorization
> Required) in response to PROPFIND request for
> '/svn_sspi/testrepo/test.txt'
>
> All other svn operations seem to work on the sspi repo.
>
> Thanks for your help
> Clemens
>
> -----Original Message-----
> From: Stefan Küng [mailto:tortoisesvn@gmail.com]
> Sent: Mittwoch, 9. Januar 2008 19:10
> To: dev@tortoisesvn.tigris.org
> Subject: Re: "Revert to this revision" (on https(i.e. WebDAV
> over ssl) repo) does not work...
>
> Wyss Clemens (Helbling Technik) wrote:
> > I am using nightly build TSVN(11836).
> > When I try to revert to a specific revision on my https-repo(sspi
> > authenticated) I get:
> >
> >> Merging revisions HEAD-1 of
> > https://scmserver/svn_sspi/testrepo/test.txt
> >> into D:\projects\testrepo\test.txt, respecting ancestry PROPFIND
> >> request failed on '/svn_sspi/testrepo/test.txt'
> >> Server sent unexpected return value (401 Authorization Required) in
> > response to
> >> PROPFIND request for '/svn_sspi/testrepo/test.txt'
> >
> > All other STVN operations work as expected.
> >
> > "Revert to this revision" works on my parallel http(basic
> auth) repo,
> > though. Hence it must have to do with the ssl/sspi
> > communication/authentication.
>
> Please install the latest nightly build, then get the
> corresponding svn.exe from the nightly build folder
> (http://nightlybuilds.tortoisesvn.net/latest/win32/svn.exe)
> and copy it in the c:\program files\TortoiseSVN\bin folder.
>
> Open a console window, cd to your working copy, then enter
>
> c:\program files\TortoiseSVN\bin\svn.exe merge -rHEADREV-1
> https://scmserver/svn_sspi/testrepo/test.txt
> D:\projects\testrepo\test.txt
>
> with HEADREV being the current HEAD revision.
>
> If you get the same error, please report this to the svn dev
> list (dev at subversion tigris org), best including your test
> repository and of course a detailed description of what you
> were doing.
>
> > BTW: can we now use sspi without ssl?
>
> No, as mentioned before: neon has this deactivated.
>
> Stefan
>
> --
> ___
> oo // \\ "De Chelonian Mobile"
> (_,\/ \_/ \ TortoiseSVN
> \ \_/_\_/> The coolest Interface to (Sub)Version Control
> /_/ \_\ http://tortoisesvn.net
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
> For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>