"svn info" does not work with symlink to different working copy

[Michael Kaufmann <mi...@gmx.ch>]

Hi all,

I am using Subverison 1.7.8. On my disk are two Subversion working copies (from different repositories), and one working copy contains a symlink to the other:

/modules/test/dir/file.dat
/sources/test/modules -> ../../modules/test/


Unfortunately "svn info" does not work with an absolute path name in this scenario:

~$ svn info /sources/test/modules/dir
svn: warning: W155010: The node '/sources/test/modules/dir' was not found.

svn: E200009: Could not display info for all targets because some targets don't exist


But it works when changing the directory before running "svn info":
~$ cd /sources/test/modules
/sources/test/modules$ svn info dir
[... valid "svn info" output ...]


I have not found anything about this behavior in the bug tracker.
Is this "by design" or is it a Subversion bug?

Regards,
Michael

Re: "svn info" does not work with symlink to different working copy

[Michael Kaufmann <mi...@gmx.ch>]

> > I have not found anything about this behavior in the bug tracker.
> > Is this "by design" or is it a Subversion bug?
> 
> I'm pretty sure there's an issue filed for this already.  I'd have
> expected a search for "symlink" to turn it up.

This issue is the "closest match" that I have found: "Symbolic links are sometimes traversed"
( http://subversion.tigris.org/issues/show_bug.cgi?id=3116 )

Do you think that this is the same problem? If not... shall I file a new bug report?


> The whole topic of 'symlink to working copy' (and whether the symlink
> itself is versioned of not) is... fun.  Maybe it's better in 1.8 than in
> 1.7?  I didn't follow development in that area closely.

The symlink is itself versioned. I have built Subversion 1.8.0-dev and checked whether it fixes the problem, but the error message is exactly the same as in 1.7.8.

Re: "svn info" does not work with symlink to different working copy

[Daniel Shahaf <d....@daniel.shahaf.name>]

Michael Kaufmann wrote on Thu, Jan 31, 2013 at 14:06:08 +0100:
> Hi all,
> 
> I am using Subverison 1.7.8. On my disk are two Subversion working copies (from different repositories), and one working copy contains a symlink to the other:
> 
> I have not found anything about this behavior in the bug tracker.
> Is this "by design" or is it a Subversion bug?

I'm pretty sure there's an issue filed for this already.  I'd have
expected a search for "symlink" to turn it up.

The whole topic of 'symlink to working copy' (and whether the symlink
itself is versioned of not) is... fun.  Maybe it's better in 1.8 than in
1.7?  I didn't follow development in that area closely.