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

Which protocol should I use? (was Re: unable to use dates for svn commands (no date format accepted for some reason?))

From: Ryan Schmidt <subversion-2005_at_ryandesign.com>
Date: 2005-11-17 15:42:46 CET

On Nov 17, 2005, at 14:52, Paul Payton wrote:

>> Your shell is interpreting the curly braces; Subversion is not even
>> seeing them. Enclose them in single quotes, or put backslashes
>> before
>> them, to prevent the shell from seeing them and pass them
>> directly on
>> to Subversion.
>> svn copy -r '{2005-11-15}' <SRC> <DST>

> your suggestion worked ... I thought it might be something stupid
> with my shell ... but had no idea what it was or how svn was
> sensitve to it
> another question ... I have the svn repository for our team out on
> a nfs file server; our team is in one location and we are not
> worried about any security. Do I need svnserver, apache, or
> anything else since nfs is taking care of it for me? I would like
> to avoid any further complexity if possible

Let's keep it on the list to help others who might have the same
issues. In the future, it would also be better to start a new thread
when you have a new question, rather than replying to an unrelated
issue, since people may never see the new question if they find the
subject line uninteresting.

The curly brackets are special characters to the shell, so it's
interpreting the characters and stripping them out before even
sending the arguments to Subversion. The same applies to any other
shell program. So this isn't Subversion-specific. Any time you want
to pass curly brackets—or any other special characters like *, $, and
so forth—to a process, you have to escape them according to the
shell's rules—for example by using single quotes or backslashes.

I personally recommend using something—anything—other than file:///
access to a repository for a group larger than one person. If you
give users file:///-level access to the repository, they can simply
use the file system to delete the entire repository. I'd want to
prevent that because I can't guarantee that my users won't
accidentally (or intentionally) do that. By using any of the other
protocols, you restrict the user to just using the repository, which
IMHO is better.

Make sure you're using an FSFS repository; BDB repositories will not
work properly on NFS. You can discover which type of repository you
have by examining the fs-type file in the repository's db directory.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 17 15:46:28 2005

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.