On Apr 11, 2009, at 05:15, webpost_at_tigris.org wrote:
> (Windows XP SVN 1.6 with latest Tortoise)
>
> As well as other problems such as BDB parts of my repository now
> not accessible - even using the svn: method - I cannot now even
> create a new repository. The message reads "...may sure the folder
> is empty and not write protected"
>
> Well the folder is empty and not write protected.
>
> IMHO SVN 1.6.0 is broken somewhere as I have never had so many
> problems with a new release.
>
> As SVN 1.6 upgraded my files automatically, I cannot easily go back
> to 1.5 now either.
If your question is specific to TortoiseSVN, please ask on the
TortoiseSVN mailing list. Otherwise, please try using the "svn" and
"svnadmin" command line utilities that are part of Subversion proper,
and show us exactly what commands you typed and exactly what output
they produced. I am almost certain you are not getting a message that
says "may sure".
I am not having any problem creating repositories or using Subversion
in any other way on Mac OS X, and I haven't heard such complaints
from anyone else on the list either, so I suspect something is
special about your system, and this is not a general problem in
Subversion.
Subversion does upgrade working copies automatically for new versions
of Subversion, but does not upgrade repositories automatically. So if
you want to go back to Subversion 1.5, you only have to remove any
working copies that were automatically upgraded and check them out
from the repository again.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1655116
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-11 22:34:55 CEST