Yes you're right. In my panic I thought directly that it had something
to do with the server. Other repositories worked correctly on this
client. Indeed even this particular repository worked with this client
some revisions ago.
Luckily for me, the problem with the failure "Can't recode String", is
discussed in the list just now. So I saw what went wrong.
The problem with recover is as you have suggested a problem with the
permissions.
Thanks to you and those who discussed the String recoding problem.
Michael
Max Bowsher wrote:
> Michael Mühlebach wrote:
>
>> Hello
>>
>> I have a serious problem where I do not see where it came from. I tried
>> to make a checkout which did not finish. (Sorry, but I do not know
>> exactly the response, because now a checkout do not even start)
>> So the checkout seemed ok until it exited in the middle with a failure
>> like "Can't recode String" or something similar.
>
>
> That's a client side failure, nothing to do with server-side.
>
>> I tried then to verify the repository with svnadmin on the server with
>> the following result:
>> ----
>> $ svnadmin verify /var/lib/subversion/anduin/repos/fh
>> svn: Berkeley DB error while opening environment for filesystem
>> /var/lib/subversion/anduin/repos/fh/db:
>> DB_RUNRECOVERY: Fatal error, run database recovery
>
>
> That *might* be nothing more than a permissions problem. Does the user
> you are running that command as have *write* access to the "db"
> repository subdir, and all files within?
>
> Max.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Nov 22 14:33:49 2004