[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

svn add read-only-dir fails unrevertably

From: John Williams <williams_at_tni.com>
Date: 2004-11-03 20:48:02 CET


   mkdir bad
   chmod -r bad

Note: Obviously one would not do this on purpose, but unless you
recursively check that every directory is writable before adding it,
this can happen when you least expect it.

   svn add bad
svn: Can't open file 'bad/.svn/lock': No such file or directory
   svn status
~ bad
   svn revert bad
svn: 'bad' is not a working copy
   svn cleanup
svn: 'bad' is not a working copy directory

It fails to add the read-only directory.
The directory is left in the dreaded '~' state, apparently because it
has an entry in ./.svn/entries but bad/.svn does not exist.
svn revert cannot fix it.
svn cleanup fails to complete running.

(tested with svn-1.1.0 and svn-1.1.1)

Should I submit a bug for this? Seems like it should detect the failure
to create bad/.svn and avoid leaving the directory in the '~' state.

Is there any way to clean this up, besides editting ./.svn/entries by hand?

~ John Williams

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 3 21:52:09 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.