Wow, fast reply.
Forgot to mention that I already turned off the firewall and virus
protection during testing.
The behavior is the same.
-=Bob
On Jul 31, 10:38 am, Stefan Küng <tortoise..._at_gmail.com> wrote:
> Bob Pinchbeck wrote:
> > BUG REPORT - Committing new files to (write-through proxy) slave repo fails.
>
> > Action Taken:
> > Added new files to a TortoiseSVN folder, then attempted to add/commit them to a (write-through proxy) slave repository.
>
> > Expected Result:
> > New (added) files should commit to the master repository (via the write-through proxy) without incident.
>
> > Actual Result:
> > Add succeeds, but commit fails (it should also be noted that SVN command-line [svn add/svn ci] succeeds)
>
> > Tortoise SVN error message when committing...
> > Bob\Documents\testslave\trunk\test6.txt
> > Commit failed (details follow):
> > Server sent unexpected return value (400 Bad Request) in response to PROPFIND\
> > request for '/svn/code/!svn/wrk/1d7c9604-3424-f143-99b4-8bda16835647/trunk/test6.txt'
>
> > SVN command-line success message when committing (the same file, with the same user)...
> > C:\bob\Documents\testslave\trunk>svn ci test6.txt --message test6
> > Adding test6.txt
> > Transmitting file data .
> > Committed revision 12.
>
> > After SVN command-line succeeds, the committed file is then available on both master and slave, as expected.
>
> > TortoiseSVN message when updating from master...
> > Update
> > C:\bob\Documents\testmaster\trunk\test6.txt
> > At revision: 12
>
> > Master Server Setup:
> > VisualSVN Server 1.5.1 (Apache 2.2.9) with Subversion authentication via HTTPS (port 8443).
> > Windows XP Professional (32 bit) Service Pack 3
> > URI:https://master:8443/svn/code
>
> > Slave (Write-Through Proxy) Server Setup:
> > VisualSVN Server 1.5.1 (Apache 2.2.9) with Subversion authentication via HTTPS (port 8443).
> > Windows XP Professional (32 bit) Service Pack 3
> > URI:https://slave:8443/svn/code
>
> > Client Setup:
> > TortoiseSVN 1.5.1.13563
> > Windows XP Professional (32 bit) Service Pack 3
> > Also attempted with nightly build (as of 7/30/2008) and received same failure.
>
> > VisualSVN Setup:
> > Software installed in C:\svn (on both master and slave)
> > Repositories installed in c:\svn\repos (on both master and slave)
> > Single repository on master and slave with same name ('code')
> > VisualSVN does not include mod_proxy.so and mod_proxy_http.so, so these were copied from a prior Win32 install of Apache 2.2.9 to the c:\svn\bin\ folder (on slave)
> > The master and slave both have appropriate hook scripts in place, as evidenced by the success of the SVN command-line.
>
> * turn off your virus scanner / desktop firewall
>
> Stefan
>
> --
> ___
> oo // \\ "De Chelonian Mobile"
> (_,\/ \_/ \ TortoiseSVN
> \ \_/_\_/> The coolest Interface to (Sub)Version Control
> /_/ \_\ http://tortoisesvn.net
>
> signature.asc
> 1KDownload- Hide quoted text -
>
> - Show quoted text -
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-07-31 18:02:44 CEST