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

[Keith Beattie <ks...@gmail.com>]

Hello,

This appears to be a reincarnation of
http://subversion.tigris.org/issues/show_bug.cgi?id=2117

$ svn info /path/to/symlink-to-wc
svn: '/path/to' is not a working copy
svn: Can't open file '/path/to/.svn/entries': No such file or directory

This happens not just with 'info' but also 'ls', 'pg' and perhaps
others but interestingly not 'st'.

I see this in 1.4.2, 1.4.3 and 1.4.6

Should I post this to dev, file a bug or perhaps try re-opening 2117?

Cheers,
ksb

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

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

[Keith Beattie <ks...@gmail.com>]

On Jan 18, 2008 5:43 AM, Erik Huelsmann <eh...@gmail.com> 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
>
> "what's the info on 'the path the symlink points to'", but you're
> asking "what's the info of '/path/to/symlink' within its working copy
> '/path/to'".
>
> Other than brokenness of 'st', I can't think of a reason to file a bug.

Well, in order for svn to answer the question you've correctly
understood that I'm trying to ask:
  "What's the info/ls/pg/etc on 'the path the symlink points to'"
knowing full well that the symlink itself is not in a WC and not under
version control.

Just because svn versions an object doesn't mean any such object
handed to it *must* be versioned for svn to properly work through it.
That seems unnecessarily limiting to me.

On Jan 18, 2008 7:03 AM, Vincent Lefevre <vi...@vinc17.org> wrote:
...
>
> I'd say that when there is a slash, the symlink should be resolved
> by svn.
>

What about just having svn check to see if it is a versioned object
and if so, report on it as such.  If it isn't, then work on what it
points to?

I could be wrong but It seems to me that svn notices that it is a
symlink and then (falsely in my case) assumes it is in a WC.

Regards,
ksb

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

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

[Vincent Lefevre <vi...@vinc17.org>]

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 <vi...@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@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

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

[Erik Huelsmann <eh...@gmail.com>]

On 1/18/08, Keith Beattie <ks...@gmail.com> wrote:
> Hello,
>
> This appears to be a reincarnation of
> http://subversion.tigris.org/issues/show_bug.cgi?id=2117
>
> $ svn info /path/to/symlink-to-wc
> svn: '/path/to' is not a working copy
> svn: Can't open file '/path/to/.svn/entries': No such file or directory
>
> This happens not just with 'info' but also 'ls', 'pg' and perhaps
> others but interestingly not 'st'.
>
> I see this in 1.4.2, 1.4.3 and 1.4.6
>
> Should I post this to dev, file a bug or perhaps try re-opening 2117?

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

"what's the info on 'the path the symlink points to'", but you're
asking "what's the info of '/path/to/symlink' within its working copy
'/path/to'".

Other than brokenness of 'st', I can't think of a reason to file a bug.

HTH,

Erik.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org