Max Bowsher wrote:
> Try this:
>
> Make a *copy* of your repository. Using this copy:
>
> Delete the __db.00* files from the db subdirectory of the repository.
>
> Run "svnadmin verify" on the repository.
>
> If it works, great, if not, post the exact error message.
>
rather good news (although very bizarre too!):
> svnadmin recover /Users/pejvan/Safe/subversion-repository
> Please wait; recovering the repository may take some time...
> svn: DB_RUNRECOVERY: Fatal error, run database recovery
and then:
> svnadmin verify /Users/pejvan/Safe/subversion-repository
> * Verified revision 0.
[...]
> * Verified revision 34.
then I'm able to checkout the anything (or anything I tried).
But I'm unable to commit and trying to commit makes again this :
> svn commit -m "cleaned up code for release"
> Sending main.m
> Sending vidal-menu.xcode/pejvan.pbxuser
> Sending vidalMenuObject.m
> Transmitting file data ..Abort
> svn log
> svn: Unable to open an ra_local session to URL
> svn: Unable to open repository 'file:///Users/pejvan/Safe/subversion-repository/vidal-menu/trunk'
> svn: Berkeley DB error while opening environment for filesystem /Users/pejvan/Safe/subversion-repository/db:
> DB_RUNRECOVERY: Fatal error, run database recovery
> svn status
> L .
> M main.m
> L French.lproj
> L French.lproj/MainMenu.nib
> L vidal-menu.xcode
> M vidal-menu.xcode/pejvan.pbxuser
> M vidalMenuObject.m
> L English.lproj
> L English.lproj/MainMenu.nib
> svn log -r HEAD
> svn: Unable to open an ra_local session to URL
> svn: Unable to open repository 'file:///Users/pejvan/Safe/subversion-repository/vidal-menu/trunk'
> svn: Berkeley DB error while opening environment for filesystem /Users/pejvan/Safe/subversion-repository/db:
> DB_RUNRECOVERY: Fatal error, run database recovery
Seems something is broken here.
thanks a lot Max, Ben, Garrett for your help. You are very helpful and
kind to help me get out of this mess :-)
What's to do next ?
Pejvan
--
Pejvan BEIGUI pejvan@online.fr
Cet email comporte une signature electronique au format OpenPGP/MIME.
Pour votre propre sécurité, tout email semblant provenir de cette
adresse mais ne comportant pas de signature ou une signature
non-valide sera réputé falsifié.
Received on Fri Jul 16 18:24:45 2004