subversion requires apache-2.0.4x to be built with support of the same version of berkdb it was built with (currently 4.0.14). Unless apache-2.0.4x is built with this requiresment authentication failures may occour trying to access remote repositories (cfr subversion INSTALL file for more details). Reproducible: Always Steps to Reproduce: 1. 2. 3.
Do you actually experience failure because of this. At the moment it is not possible to have apache2 compile with db4 yet. Also subversion uses its own versioned static db. So as far as apache is concerned, the subversion module is not linked with db.
wrong. apache compiles just fine with db-4.0.14.
Paul: what about using PDEPEND in subversion ebuild to force emerge of an db4-statically-compiled version of apache 2.0.45 ? Is this possible ? If so this would allow users which are not using subversion to stay with their current apache2 compiled against db3 and users of subversion to have it working the right way with apache. just an idea.... let me know.
I know apache2 compiles well with db4, but db4 is still masked currently waiting for all issues concerning an update to be resolved. With PDEPEND it is still not possible to require apache2 to be built with db4. What I can do is have the ebuild check on the actual existence of db4 on the system, and then have it use it instead of a static db4. For me actually the combination of db versions does not pose a problem using apache2 with authentication (I use htpasswd files). I think including a full apache2 in the ebuild as was done in the 0.10 ebuild is overkill.
Paul: i've seen this can be considered as a dup of #17309. Even if a real solution won't be available until db4 is unmasked, for now adding a check for db4 in the apache-2.0.45 ebuild could work fine (along with adding a message in the subversion ebuild which could warn the user to emerge db4 and the re-emerge apache or something like this). Any suggestion? What d'you think about this idea ?
As I understand it apache2 should just compile with db4 if it is installed. I will put a check in subversion so that it will not use the static db4 if db4 is installed. Be aware though that we might introduce versioned db symbols in db4 which would mean that all db dependend applications need to be recompiled.
ok, what about using a solution like the one you can find at http://cvs.gentoo.org/~alain ? it consists in a tweaked db-4.1.25 which gets installed in a non-standard path to not interfere with db-3.2.x, and tweaked apache2 and subversion ebuilds to use db4 from the non-standard path is this viable?
apache ebuild will not be touched for this nonsense. manage the versions of db on you system. same as i do.
>------- Additional Comment #8 From Donny Davies 2003-05-05 18:02 EST ------- >apache ebuild will not be touched for this nonsense. >manage the versions of db on you system. same as i do. okay: btw, i think it is not necessary to shut up people this way. i was only trying to develop some possible workarounds. i'm "going to manage the versions of db on my system" now, bye.
I changed subversion to use the system db4 if it is installed. I will not change apache2 as it should build with db4 if it is the system db. If you want to use db4 in apache2 and subversion then you basically need a db4 based system. Basically then unmerge db3, merge db4, and all programs that depend on db. Note that although the subversion documents mention differently, a db3 apache (standard) is able to cooperate with the db4 based subversion.
Paul: thanks for your help. i'll test the new subverison ebuild asap
tested subversion-0.21-r1 with db4 and all the deps rebuilded: okay for me. thanks again Paul: your -r1 build fixes the issue.
