[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

'PROPFIND' question about TSVN/SVN

From: Gregory Graham <ggraham_at_americanchartered.com>
Date: 2006-07-27 16:45:43 CEST

Hi,

 

  I've been a happy user of TSVN/SVN on the Windows platform since
January 2006, using TSVN 1.2.6 (built against SVN 1.2.3) on client
developer machines pointing at repositories on a machine with SVN 1.2.3
installed using Apache 2.0 listening on a port number other than 80. My
repository structure is usually

    name

    name/current

    name/releases

    name/releases/r1

    name/releases/r2

       ... etc

A very simple environment: a few developers work against name/current
branch and a bug fixer typically works against one of the
name/releases/r* branches. Every few weeks, I freeze current, merge bug
fixes back from releases back into current, and make a new release.
During this process I am pretty liberal with making tags so I can roll
back if needed.

 

  A strange thing happens when I make the tags: I check out the latest
name/releases/r* from the Apache server into a local working copy and
make a tag in it. Then I check out the current branch from the Apache
server to a local working copy, but when I try to make a tag in it I get

    Error: PROPFIND request failed on '/SVN/name'

    Error: PROPFIND of '/SVN/name': 301 Moved Permanently
(http://apacheserver:portnum)

However, if I log on to the apache server directly and check out the
current branch using a file:// URL (ie- bypassing Apache) then I can
make a tag.

 

  I feel like I'm missing something important here: what does "PROPFIND
request failed" mean, and why does it happen while making a tag
sometimes and not other times with the Apache server? Was it a poor
choice of folder structure?

 

  Thanks! I sincerely hope it is not too deep a question...

 

              -Greg Graham

 

 

 

 

 

 
Received on Thu Jul 27 16:46:07 2006

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.