Paul de Vrieze wrote:
> Quite likely you changed db versions along the run. While this
> theoretically should work. The best course of action is to dump the
> repository. Make sure you have a consistent use of db, and load the
> repository. Alternatively you could try to use fs_fs
Eventually I wa
binaries to verify I start getting errors with either
install. I had tar'ed up repos after doing a 'db4.1_recover -v -h
/var/svn/repos/'. If I revert to that I can use the binaries I
installed again without error.
~Ian
Danny van Dyk wrote:
> Ian Brandt schrieb:
>
>>&g
dmin recover /var/svn/repos/
Repository lock acquired.
Please wait; recovering the repository may take some time...
*** glibc detected *** double free or corruption (out): 0x080667c8 ***
Aborted
~Ian
Aaron Walker wrote:
> Ian Brandt wrote:
>
>
>>># svnadmin verify /var/svn/r
amp;msgNo=29787
Regards,
Ian
Konstantin V. Arkhipov wrote:
> On Saturday 07 May 2005 22:44, Ian Brandt wrote:
>
>>[error] (20014)Error string not specified yet: Berkeley DB error while
>>opening environment for filesystem /var/svn/repos/db:\nDB_RUNRECOVERY:
>>F
I suppose this is effectively to Paul:
Have you had a chance to try Subversion with Apache 2.0.54? I'm
getting the following error after emerging apache-2.0.54 (along with
apr-1.1.1 and apr-1.1.2), and re-emerging subversion-1.1.4:
[notice] Apache/2.0.54 (Gentoo/Linux) mod_ssl/2.0.54 OpenSSL/0.
