The following 2 modules current do not build against the recently updated apache2 ebuild. At the very least, /usr/sbin/apxs is missing execute bits -- but even when these are manually restored the build still fails. Reproducible: Always Steps to Reproduce: 1. emerge apache2 2. emerge mod_perl or mod_wsgi Actual Results: Ebuilds fail. Expected Results: Ebuilds should succeed.
something similar with mod_python, mod_geoip2 and i think even php 5.3.10-r2 (dont remember exactly and cant check since i reverted back to 2.2.22)
Please file a separate bug for www-apache/mod_wsgi.
I've tried to build mod_perl from svn trunk and from httpd24 branch and it's still depending on removed remote_ip and remote_addr.. See this thread for details http://mail-archives.apache.org/mod_mbox/perl-modperl/201203.mbox/%3CCAJiMZ97mkhKe9OQX9Rm9doFn9GDcRf8U3ASoHpJUVpo=-aa-MQ@mail.gmail.com%3E So maybe apache-2.4* should be masked a bit longer...
Created attachment 307641 [details] mod_perl-2.0.5-r1302463.ebuild
Created attachment 307643 [details, diff] mod_perl-2.0.5-r1302463.patch
Created attachment 307645 [details, diff] mod_perl-2.0.5-r1302463-dirty-hacks-to-build-it.patch
Created attachment 307647 [details, diff] mod_perl-2.0.5-r1302463-use-client_ip-client_add-instead-of-remote_ip-remote.patch
Created attachment 307649 [details, diff] mod_perl-2.0.5-r1302463-use-log.level-instead-of-loglevel.patch
Created attachment 307651 [details, diff] mod_perl-2.0.5-r1302463-bundled-Apache-Test.patch
Created attachment 307653 [details, diff] mod_perl-2.0.5-r1302463-ConstantsTable.pm-drop-OPT_INCNOEXEC.patch
I've built it successfully with couple of dirty hacks and apache-backuppc works for me.. so I'll attach my patches here if someone finds them usefull...
All patches except first one (mod_perl-2.0.5-r1302463.patch) still do apply to newly added mod_perl-2.0.7 and provide working mod_perl for apache-2.4 (still using it mostly for apache-backuppc)
Any updates on any mod_perl ebuild that will build with the latest apache ebuilds? I'm concerned about falling behind with apache versions, and I need mod_perl for my work. Thanks.
I've added mod_perl-2.0.8 to my overlay. I got it working with apache-2.4 based on the debian work and thanks to Gregor Herrmann <gregoa@debian.org>. http://git.overlays.gentoo.org/gitweb/?p=dev/jmbsvicetto.git;a=tree;f=www-apache/mod_perl;h=127de13d9bf9dae418e8d7ffce20e29b28b80383;hb=refs/heads/master
I don't use Apache on Gentoo anymore, so I don't need to track this bug. Can it be reassigned?
(In reply to Sean McGovern from comment #15) > I don't use Apache on Gentoo anymore, so I don't need to track this bug. Can > it be reassigned? You're the reporter, not the assignee. The reporter cannot be changed, sorry.
Nobody ever opened another bug for mod_wsgi; for what it's worth, that was fixed with a version bump in bug #510938.
There is no such version (mod_perl-2.0.5) in portage anymore. Vote for close.
I think this issue persists with 2.0.8 in the main portage tree. I've been using the ebuild from Jorge's overlay in comment 14 for some time now.
Seems like I was wrong. Even in ebuild still present: DEPEND="<www-servers/apache-2.4
(In reply to Jorge Manuel B. S. Vicetto from comment #14) > I've added mod_perl-2.0.8 to my overlay. I got it working with apache-2.4 > based on the debian work and thanks to Gregor Herrmann <gregoa@debian.org>. > > http://git.overlays.gentoo.org/gitweb/?p=dev/jmbsvicetto.git;a=tree;f=www- > apache/mod_perl;h=127de13d9bf9dae418e8d7ffce20e29b28b80383;hb=refs/heads/ > master Anything blocking this from being moved to the tree?
Tested with apache 2.4.10 and perl 5.20. --- mod_perl-2.0.8.ebuild 2014-11-09 23:01:19.000000000 +0100 +++ mod_perl-2.0.8-r1.ebuild 2014-11-12 09:09:24.227455575 +0100 @@ -81,6 +81,10 @@ rm -rf Apache-{Test,Reload,SizeLimit}/ lib/Bundle/ sed -i -e 's:^Apache-\(Reload\|SizeLimit\|Test\).*::' \ -e 's:^lib/Bundle/Apache2.pm::' MANIFEST || die + + # 410453 + epatch "${FILESDIR}/use-client_ip-client_add-instead-of-remote_ip-remote.patch" + epatch "${FILESDIR}/use-log.level-instead-of-loglevel.patch" } src_configure() { @@ -97,6 +101,7 @@ INSTALLDIRS=vendor \ MP_USE_DSO=1 \ MP_APXS=${APXS} \ + MP_APR_CONFIG=/usr/bin/apr-1-config \ ${myargs} || die }
(In reply to Tomas Mozes from comment #22) [...] -e 's:^lib/Bundle/Apache2.pm::' MANIFEST || die > + > + # 410453 > + epatch > "${FILESDIR}/use-client_ip-client_add-instead-of-remote_ip-remote.patch" > + epatch "${FILESDIR}/use-log.level-instead-of-loglevel.patch" > } Where are this patches coming from? Are the ones from this bug? (look to be for 2.0.5) I have seen most distributions are relying on Debian packages for this... and they have now a 2.0.9 snapshot
(In reply to Pacho Ramos from comment #23) > (In reply to Tomas Mozes from comment #22) > [...] -e 's:^lib/Bundle/Apache2.pm::' MANIFEST || die > > + > > + # 410453 > > + epatch > > "${FILESDIR}/use-client_ip-client_add-instead-of-remote_ip-remote.patch" > > + epatch "${FILESDIR}/use-log.level-instead-of-loglevel.patch" > > } > > Where are this patches coming from? Are the ones from this bug? (look to be > for 2.0.5) Yes
@idl0r, what option do you think is better? The Debian snapshot or applying that two patches?
+*mod_perl-2.0.8-r1 (08 May 2015) + + 08 May 2015; Pacho Ramos <pacho@gentoo.org> + +files/use-client_ip-client_add-instead-of-remote_ip-remote.patch, + +files/use-log.level-instead-of-loglevel.patch, +mod_perl-2.0.8-r1.ebuild, + -mod_perl-2.0.7-r1.ebuild: + Support apache 2.4 (#410453) +