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

Re: Subversion bug thinks host is peg revision in: svn+ssh://svn@host/

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2006-08-29 23:08:45 CEST

On 8/29/06, John Rouillard <rouilj@renesys.com> wrote:
> Hello all:
> I am running the following command and get the weird output below:
> tigris> svn list svn+ssh://svn@tigris/
> svn: Syntax error parsing revision 'tigris'
> It looks to me like the parser thinks that @tigris is a peg revision
> specifier. If I change it to:
> tigris> svn list svn+ssh://svn@tigris/core
> I get the expected list. Variants of the URL:
> svn+ssh://svn@tigris/.
> svn+ssh://svn@tigris
> also yield the same "parsing revision" error message.
> This all came to light when I changed the forced command for the svn
> user on tigris from:
> /tools/subversion-1.3/bin/svnserve -t --tunnel-user=rouilj
> to:
> /tools/subversion-1.3/bin/svnserve -t -r ~svn/dev-repository \
> --tunnel-user=rouilj
> so that I could move the repository location without my users having
> to do a switch --relocate.
> The involved versions of the software on this fedora core 2 box
> (tigris) are:
> subversion-1.2.1-0.1.1.fc2.rf
> subversion-1.3-1
> neon-0.24.7-2.1
> apr-0.9.4-11
> In this case and the case below the subversion 1.3-1 were locally
> built and packaged. Now another box running Centos 4.3 with revisions:
> subversion-1.1.4-2.ent
> subversion-1.3-1
> neon-0.24.7-4
> apr-0.9.4-24.5
> doesn't have this problem, but another Centos 4.3 box with a newer apr:
> apr-0.9.4-24.5.c4.1
> does exhibit this problem. Could this issue be caused by code in the
> apr library?

It has nothing to do with APR. It's simply that peg revs didn't show
up until an older version of subversion.

> Has this problem been identified (I didn't see it online). Is it fixed
> (by some other changes maybe) in 1.4?
> I am looking at reverting the svnserve command line change and making
> it "-r ~svn", but that would mean my users will have to do svn
> switches and they will still need to know the physical location of the
> repository which is less than ideal.

This is issue http://subversion.tigris.org/issues/show_bug.cgi?id=2349,
which has a work around for the problem. Unfortunately nobody has
come up with a real fix. Patches to correct it would be most welcome


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 29 23:11:35 2006

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

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