You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Markus Fischer <ma...@fischer.name> on 2006/04/24 09:12:27 UTC

Symlink changed to file, "has unexpectedly changed special status"

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

a file has been changed from a symlink to a real file and now I get this
message:

svn: Entry 'file' has unexpectedly changed special status

I've searched with google but the only think I found was to delete the
file and re-add it:

> http://svn.haxx.se/users/archive-2006-01/0797.shtml
> You must "svn rm" the file, and then "svn add" the symlink. 

However in my case there are many files touched this way because I'm
versioning distribution packages from debian. I couldn't use asvn
because it had problems with /dev and /proc and ignore didn't work the
script.

So my question .. is there an easier way for me to "upgrade" symlinks to
files without going through all of them? Any reason why svn can't handle
this change on its own? Or any way to disable to useage if svn:special
and just treat symlink files like regular files? If so, what would
happen in the case a symlink is broken?

thanks for help,
- - Markus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFETJZ71nS0RcInK9ARAjX6AKCCvRiMK68i+xyAMb/pWjLO6gH5qQCgkjPq
+ihP9CPZxMB6uCFoThCpC+A=
=hncO
-----END PGP SIGNATURE-----

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