Re: svn info /path/to/symlink-to-wc fails

On 2008-01-18 14:43:06 +0100, Erik Huelsmann wrote:
> No, why? [I suppose you were not going to report 'st' is broken?] What
> you're seeing is correct behaviour: symlinks themselves are versioned
> objects, so you're not asking Subversion

The error message is misleading.

vin:~> svn info symlink-to-wc
svn: '.' is not a working copy
svn: Can't open file '.svn/entries': No such file or directory
zsh: exit 1 svn info symlink-to-wc

So, I would assume that for any object in '.', I would get the same
error. But this is not the case if the object is a directory!

Also, is there any reason why the following commands have different
behaviors?

vin:~> svn info symlink-to-wc/doc
Path: symlink-to-wc/doc
URL: svn+ssh://home/home/lefevre/svn/doc
Repository Root: svn+ssh://home/home/lefevre/svn
[...]

vin:~> svn info symlink-to-wc/
svn: '.' is not a working copy
svn: Can't open file '.svn/entries': No such file or directory
zsh: exit 1 svn info symlink-to-wc/

vin:~> svn info symlink-to-wc/.
svn: '.' is not a working copy
svn: Can't open file '.svn/entries': No such file or directory
zsh: exit 1 svn info symlink-to-wc/.

Compare to file:

vin:~> file symlink-to-wc
symlink-to-wc: symbolic link to `wd'
vin:~> file symlink-to-wc/
symlink-to-wc/: directory
vin:~> file symlink-to-wc/.
symlink-to-wc/.: directory

I'd say that when there is a slash, the symlink should be resolved
by svn.

(All these tests done on Debian/unstable.)

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org