[Niklaus Giger <ngiger@mus.ch>] Re: Problem running log: resolved: run db_recover on repos/db

This patch was for repos_admin.texi, but I'm not sure how it applies
in the new incarnation of the docs. I'm forwarding it here so people
more intimately familiar with the new docs can see if it still
applies, and if so where :-).

-K

attached mail follows:

Hi,

Thank you everybody for helping me out. Browsing the mail archive and digging
into "Another weird error message" found the solution.

I am also part of the stupid minority (or are we the silent majority?) who did
ran db_recover on /path/to/repos instead of /path/to/repos/db. Yes I know I
have read the manual carefully.

Also db_recover (at least on my Debian system) is available in several
versions like db_recover db3_recover and db4.0_recover.

Could you consider to apply the attached patch (or something similar)?

BTW, as it seems to be quite normal, that one has to recurr to this solution,
wouldn't it be a good idea (maybe post 1.0?) to integrate the call db_recover
into the svnadmin tool, e.g. by defining
svnadmin recover [URL]

Having solved this problem, I will continue to use Subversion and hope that it
will get mature soon. I would really like to push my collegues into a good
alternative to the Microsoft VisualSourceSafe.

Againg, thanks to everybody.

Best regards

-- 
Niklaus Giger
Wieshoschet 6
CH-8753 Mollis
Tel. ++41 55 612 20 54 (privat)
Tel. ++41 55 618 64 68 (Geschäft)

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

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