On Friday 13 May 2005 19:04, Ian Brandt wrote:
> 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. A
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
On Sunday 08 May 2005 19:09, Ian Brandt wrote:
> I realized I had added:
> >=dev-libs/apr-0.9.6
> >=dev-libs/apr-util-0.9.6
>
> to /etc/portage/package.keywords, and that is why apr-1.1.1 and
> apr-1.1.2 were installed, and not because they were required by
> apache-2.0.54. I changed >= to ~ on th
On Saturday 07 May 2005 20:44, Ian Brandt wrote:
> 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:
>
> [no
The latest:
I downloaded the subversion-1.1.4 source from tigris.org and did a
standard ./configure ; make ; make install. (It picked up my
installed db-4.1.25_p1-r4.) As long as I only use the binaries I
compiled svnadmin verify and svnlook work fine. If I use the Gentoo
subversion-1.1.4 bina
I realized I had added:
>=dev-libs/apr-0.9.6
>=dev-libs/apr-util-0.9.6
to /etc/portage/package.keywords, and that is why apr-1.1.1 and
apr-1.1.2 were installed, and not because they were required by
apache-2.0.54. I changed >= to ~ on those entries, unmerged them,
re-emerged apache-2.0.54 and s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ian Brandt wrote:
> # svnadmin verify /var/svn/repos/
> *** glibc detected *** double free or corruption (out): 0x08064768 ***
> Aborted
Are you sure you have the latest versions of everything? When the big apache
unmask happened, my subversion brok
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ian Brandt schrieb:
> Hi Konstantin,
>
> Thanks for the tips. I'm actually on that road already. It appears
> my /var/svn/repos/db has been corrupted:
>
> # svnadmin verify /var/svn/repos/
> *** glibc detected *** double free or corruption (out): 0
Hi Konstantin,
Thanks for the tips. I'm actually on that road already. It appears
my /var/svn/repos/db has been corrupted:
# svnadmin verify /var/svn/repos/
*** glibc detected *** double free or corruption (out): 0x08064768 ***
Aborted
# svnadmin recover /var/svn/repos/
Repository lock acquir
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:
> Fatal error, run database recovery
* check existence of /var/svn/repos
* check permissions on /var/s
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.
11 matches
Mail list logo
