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.
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 those
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
-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 broke
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
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
