READ ME: working copy ickiness!

Hey everyone, read about the eol bugs we uncovered today in issue
#1085. Glad we decided to start using our own feature, ugh.

If you update your wc to HEAD right now, you'll get a zillion
propchanges. Almost every file in our tree will receive an
'svn:eol-style' property. Most are being set to 'native' style, and a
few are set to fixed 'CRLF'.

After the update, 'svn st' will report that you have a number of files
locally modified. This is untrue. What's really going on is that
certain text-bases weren't converted properly during the update.
Hence the bug.

*** The workaround, for now: ***

The simple solution is just to checkout a fresh working copy of
/trunk.

The repair solution:

Hand-delete the parent directories that contain the bogus text-bases:

   $ rm -rf build/win32 notes subversion/bindings/com

Then run 'svn up' to get the missing directories back:

   $ svn up

This fixes everything but one file, 'win-tests.py', which is at the
top level of your working copy. You can't really delete the parent,
unless you want to destroy your working copy.

Instead, just translate the file's text-base from DOS to Unix
line-endings:

   $ cat .svn/text-base/win-tests.py.svn-base | tr -d '\r' > tmpfile
   $ mv tmpfile .svn/text-base/win-tests.py.svn-base

Sorry for the annoyance, everyone.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 14 00:33:11 2003