Symlinks on windows and UNIX bug?

[Georg Viehöver <vi...@sigma-c.de>]

Hello,

I did the following with svn 1.1.3:
- on Unix, i created a sym-link: ln -s  scauth scauth_link. Scauth is a directory
- svn add scauth_link
- svn ci ...

This worked fine, and ci and co on UNIX work perfectly.

Then I created a workspace on WinXP, and did a svn co of the directory containing scauth_link.
Svn status now gives (i did not touch that file):
svn st
~      scauth_link

Which is not what I expected (since I did not change anything). Even worse, ci fails:
svn ci -m"test"
svn: Übertragen fehlgeschlagen (Details folgen):
svn: Der Spezialstatus von Eintrag 'D:/user/gv/tmp/svn_wrokspace/myproduct/scaut
h_link' hat sich unerwarteterweise geändert

(Translation from German: 
Svn: transfer failed (details follow):
Svn: The special state of entry "D:... Scauth_link" has changed unexpectedly.
)

Question: Bug or feature? From my point of view, svn should handle this situation gracefully (ie. Either ignore symlinks on checkout, or not assume a change in the type if I did not touch the file).

Georg

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

Re: Symlinks on windows and UNIX bug?

[Ben Collins-Sussman <su...@collab.net>]

On Mar 22, 2005, at 2:40 PM, Georg Viehöver wrote:

> Question: Bug or feature? From my point of view, svn should handle 
> this situation gracefully (ie. Either ignore symlinks on checkout, or 
> not assume a change in the type if I did not touch the file).
>

Already fixed in trunk, it will be out in 1.2.  Thanks for the report.


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