I've searched the mailing list archives, and found one or two mentions
of this problem, but no response was given (that I saw).
I've found that if I have checked out a working copy to a directory
(alpha), and symlinked said directory (bravo), any svn commands run
against the symlink (such as `svn info bravo`) regard it as
unversioned. All commands operating on the files or subdirectories
(such as `svn info bravo/file.txt`) work fine.
As best I can tell, it's treating the symlink like a file rather than
a directory, and falling back to operating on the parent directory.
I'm just wondering if this is intended functionality? If it's not,
perhaps I could file a bug report for it. I'm running SVN 1.4 under
Mac OS 10.4.11, if that matters.
$ cd /Users/ekaufman/test
$ mkdir ./alpha
$ svn checkout svn://localhost/test ./alpha
A alpha/file.txt
Checked out revision 1.
$ ln -s ./alpha ./bravo
$ svn info ./bravo/
svn: '/Users/ekaufman/test' is not a working copy
svn: Can't open file '/Users/ekaufman/test/.svn/entries': No such file
or directory
$svn info ./bravo/file.txt
Path: /Users/ekaufman/test/bravo/a1.txt
Name: a1.txt
URL: svn://localhost/test/a1.txt
Repository Root: svn://localhost/test
Revision: 1
Node Kind: file
Schedule: normal
Last Changed Author: ekaufman
Last Changed Rev: 1
Thanks!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-01-04 05:12:32 CET