http://www.apache.org/dist/httpd/Announcement2.2.html Reproducible: Always Steps to Reproduce: 1. 2. 3. http://www.apache.org/dist/httpd/CHANGES_2.2
Thanks for your report. As there's some changes to configuration and other important changes like LFS it's not quite as simple a bump as the usual 2.0.x bumps. As we need to figure out what changes is needed first there will probably be some delay before 2.2 hits portage.
w/o problem. This bug only for gentoo ebuilders. :-) Thanks for support!
*** Bug 114388 has been marked as a duplicate of this bug. ***
We are building a new web app for deployment in a few months, would like to build it on apache-2.2. Is there a development ebuild somewhere I can help test?
(In reply to comment #4) > We are building a new web app for deployment in a few months, would like to > build it on apache-2.2. Is there a development ebuild somewhere I can help > test? > Hi, Same request. I need Apache 2.2 too but am not able to create a working ebuild for it... Thank you dear ebuilders !
Same here, I would love to test a 2.2 ebuild :-)
Hello, Is there still no news about an ebuild of 2.2 ? I really need it because of his new proxy load balancer module... Could an ebuilder try to create an ebuild of it please ?
Is there any news about any ebuild for 2.2 yet. I would relly love to test 2.2 :)
It's coming... very soon. I have testing and working ebuilds for apr and apr-util that is needed by apache-2.2 in my private overlay. I also have finished refactoring the current apache ebuild to work with 2.2 in my overlay - though it is yet untested. I need to finish going through the provided upsteam default configuration tweaking it to match gentoo's configuration - this is about 20% done. After that, apache-2.2 should be ready to move into the live gentoo tree, albeit package.mask-ed for some more testing. Some new things that are implemented in the 2.2 ebuild (that if they work correctly will probably get back-ported to the 2.0 [and maybe even 1.3] line:) - configurable suexec [see bug 66397] - auto-generated APACHE2_OPTS based on USE-flags and configured modules in apache2-builtin-mods - auto-generated LoadModule lines based on configured modules in apache2-builtin-mods - Rewrote the AddDirectoryIndex patch that is causing segfualts in some situations (still needs to be tested for those segfaults, but they should be gone...) TODO: - implement all functions in apache2ctl in /etc/init.d/apache2 so we don't have 2 scripts doing very similar things, symlink apache2ctl to said init-script - finish tweaking configuration - figure out how the modules eclass needs to be modified - thoughts below - ??? I'm sure I'm forgetting something, I'm sure someone will remind me at some point or I'll remember About the eclass: In general, most apache-2.0 modules should work just fine with apache-2.2, after they've been recompiled. The exceptions are those that used deprecated functions in apr/apr-util 0.9.x, as those have been removed in apr/apr-util 1.2.x. So what we need is for the modules that current call need_apache2 or need_apache to tell use whether they work with apache-2.2 as well. Should blocking apache-2.2 by those modules be the exception or the rule? (we are forced to use blocking, because portage doesn't support ranged deps). This will be determined by our actual testing of modules I suppose. Apache-2.2 will not go into it's own slot - it's the same codebase as apache-2.0, just improved upon. Between today and this weekend I should get enough done to get the initial ebuilds out there for testing.
(In reply to comment #9) > It's coming... very soon. This sounds great Michael :)
ok, running a bit behind, as apache takes quite a while to compile in my user-mode-linux (I need to tweak some settings there I think...) I have just commited the following to gentoo cvs. Please add them to /etc/portage/package.unmask and /etc/portage/package.keywords and give them a whirl. I tested mod_macro with apache 2.2 (as it's a module I use quite a bit) and it works for me. Please test other modules with 2.2 and let me know which work and which don't work. There are some things that still need to be done before I unmask this: * re-implement apache2ctl in /etc/init.d/apache2 * fix the path to perl in example cgi-scripts (and possibly other places - this is a regression from 2.0, upstream was supposed to fix this) * complete suexec-config (very very basic script right now) * work on eclass for modules * create example configurations for all vhost types (name based, ip based, combination) If anyone has any other suggestions or come across any problems while testing 2.2, please post here. As far as upgrading: Many configuration directives have been split out from httpd.conf to thier own files in modules.d/. Most of these have very sane defaults in 2.0 and 2.2, so shouldn't have needed to be changed any, but if you have, beware of that. (Examples of such split out: mpm settings, autoindex settings, language/charset settings, mod_info/mod_status, mod_userdir) Be warned that this ebuild is highly experimental at this point - i.e. don't use it on production systems.
Packages to add to package.unmask and package.keywords (forgot to post it above): ~dev-libs/apr-1.2.2 ~dev-libs/apr-util-1.2.2 ~net-www/apache-2.2.0
> TODO: > - implement all functions in apache2ctl in /etc/init.d/apache2 so we don't have > 2 scripts doing very similar things, symlink apache2ctl to said init-script I disagree. The Gentoo init scripts use an output very different from apache{,2}ctl script. I think they should be kept as is, or init script might be improved, but apache{,2}ctl must keep current behavior. (I know this is not the best place to post this...)
Builds without problems here, thanks. Building with USE="-ipv6" however, leads to a known bug: http://mail-archives.apache.org/mod_mbox/logging-log4cxx-user/200507.mbox/%3C20050715125000.GA642@ahriman.roedu.net%3E
For me everything compiles fine and works fine as well. But I have a little concern about output shown while starting and stopping the server: * Starting apache2 ... [Thu Feb 16 18:48:17 2006] [warn] module actions_module is already loaded, skipping [Thu Feb 16 18:48:17 2006] [warn] module alias_module is already loaded, skipping [Thu Feb 16 18:48:17 2006] [warn] module auth_digest_module is already loaded, skipping [Thu Feb 16 18:48:17 2006] [warn] module autoindex_module is already loaded, skipping [Thu Feb 16 18:48:17 2006] [warn] module cache_module is already loaded, skipping [Thu Feb 16 18:48:17 2006] [warn] module cgi_module is already loaded, skipping [Thu Feb 16 18:48:17 2006] [warn] module cgid_module is already loaded, skipping [Thu Feb 16 18:48:17 2006] [warn] module dav_module is already loaded, skipping [Thu Feb 16 18:48:17 2006] [warn] module deflate_module is already loaded, skipping [Thu Feb 16 18:48:17 2006] [warn] module dir_module is already loaded, skipping [Thu Feb 16 18:48:17 2006] [warn] module env_module is already loaded, skipping [Thu Feb 16 18:48:17 2006] [warn] module expires_module is already loaded, skipping [Thu Feb 16 18:48:17 2006] [warn] module headers_module is already loaded, skipping [Thu Feb 16 18:48:17 2006] [warn] module include_module is already loaded, skipping [Thu Feb 16 18:48:17 2006] [warn] module info_module is already loaded, skipping [Thu Feb 16 18:48:17 2006] [warn] module log_config_module is already loaded, skipping [Thu Feb 16 18:48:17 2006] [warn] module logio_module is already loaded, skipping [Thu Feb 16 18:48:17 2006] [warn] module mime_module is already loaded, skipping [Thu Feb 16 18:48:17 2006] [warn] module negotiation_module is already loaded, skipping [Thu Feb 16 18:48:17 2006] [warn] module rewrite_module is already loaded, skipping [Thu Feb 16 18:48:17 2006] [warn] module setenvif_module is already loaded, skipping [Thu Feb 16 18:48:17 2006] [warn] module speling_module is already loaded, skipping [Thu Feb 16 18:48:17 2006] [warn] module status_module is already loaded, skipping [Thu Feb 16 18:48:17 2006] [warn] module userdir_module is already loaded, skipping [Thu Feb 16 18:48:17 2006] [warn] module usertrack_module is already loaded, skipping Maybe this warnings are due to errors in configuration but I couldn't find the cause of the problem.
(In reply to comment #15) > For me everything compiles fine and works fine as well. But I have a little > concern about output shown while starting and stopping the server: > Maybe this warnings are due to errors in configuration but I couldn't find the > cause of the problem. do you have USE=static-modules ? I don't think I accounted for this case in the automatic generation of the LoadModule lines (I will do so). If you do have USE=static-modules, then comment out the LoadModule lines in /etc/apache2/httpd.conf and see if that solves it.
(In reply to comment #16) > (In reply to comment #15) > > For me everything compiles fine and works fine as well. But I have a little > > concern about output shown while starting and stopping the server: > > Maybe this warnings are due to errors in configuration but I couldn't find the > > cause of the problem. > do you have USE=static-modules ? I don't think I accounted for this case in the > automatic generation of the LoadModule lines (I will do so). If you do have > USE=static-modules, then comment out the LoadModule lines in > /etc/apache2/httpd.conf and see if that solves it. (In reply to comment #16) > (In reply to comment #15) > > For me everything compiles fine and works fine as well. But I have a little > > concern about output shown while starting and stopping the server: > > Maybe this warnings are due to errors in configuration but I couldn't find the > > cause of the problem. > do you have USE=static-modules ? I don't think I accounted for this case in the > automatic generation of the LoadModule lines (I will do so). If you do have > USE=static-modules, then comment out the LoadModule lines in > /etc/apache2/httpd.conf and see if that solves it. I have the same problem and I'm pretty sure, that I do not have USE=static-modules set, but I'll check that again. Subversion and mod_perl do not compile while apache 2.2 is installed.
I've been struggling with a version incompatibility with the included libpcre-3.9 in the apache-2.0x series and was hoping to get support for external libpcre with 2.2. Any chance that we get libpcre as a configurable USE flag? The configure switch is --with-pcre I have added --with-pcre to the current 2.2.0.ebuild and re-built apache-2.2.0 with libpcre-6.3 without problems. -- mike
(In reply to comment #18) > I've been struggling with a version incompatibility with the included > libpcre-3.9 in the apache-2.0x series and was hoping to get support for > external libpcre with 2.2. > > Any chance that we get libpcre as a configurable USE flag? > The configure switch is --with-pcre > > I have added --with-pcre to the current 2.2.0.ebuild and re-built apache-2.2.0 > with libpcre-6.3 without problems. This is something that I will need to look into further. 2.2 bundles pcre 5.0 with it. I don't know why they didn't use the latest version - if I don't find any documented reason why and can't get an answer from upstream, I'll add a USE-flag.
<chipig> vericgar: it doesn't bundle a later version, because the later version wasn't available when we upgraded :) <vericgar> chipig: any known issues with the latest version? <chipig> vericgar: haven't heard any violent death stories about it :) new item for my TODO list: using external pcre.
There is a problem if apr is built without ipv6 support, the apache-2.2.0-r2 build failed with these messages: /usr/lib/libapr-1.so: undefined reference to `sock_is_ipv6' /usr/lib/libapr-1.so: undefined reference to `find_if_index' collect2: ld returned 1 exit status make[2]: *** [htpasswd] Error 1 make[2]: *** Waiting for unfinished jobs.... /usr/lib/libapr-1.so: undefined reference to `sock_is_ipv6' /usr/lib/libapr-1.so: undefined reference to `find_if_index' collect2: ld returned 1 exit status make[2]: *** [htdigest] Error 1 /usr/lib/libapr-1.so: undefined reference to `sock_is_ipv6' /usr/lib/libapr-1.so: undefined reference to `find_if_index' collect2: ld returned 1 exit status I added +ipv6 to apr as a workaround.
Upgrade to the recently released APR 1.2.6, and its fixed :)
Just to drop you a note: I've been testing Apache 2.2.0 + PHP 5.1.2 today with my test server, and everything seems to work fine. Also according to Apache Benchmark performance jumped quite a bit (from 1000 requests/sec to 1200-1400 requests/sec). I tested with dynamically loaded PHP 5 module and with statically built version (with static-modules USE flag). Thank you and keep up the good work!
Before you push apache 2.2 into portage tree please make sure mod_python 3.3 is available (currently 3.2.8 is available, 3.2.9 is upcoming and apache 2.2 support will be in 3.3 release).
Apache 2.2.2 is now in the tree. Changes in this version: (dev-libs/apr-1.2.7-r2, dev-libs/apr-util-1.2.7, net-www/apache-2.2.2) - now using the pcre available on the system - apr is now using the libtool from the system instead of the bundled one - mpm-peruser now compiles (bug 133191) - ipv6 USE-flag had no effect in apr (to work around upstream bugs) - suexec-config is complete Still to do: - test every module - test more fully upgrade paths - finish init script - example configurations - add apr_dbd_mysql to apr-util (bug 127781)
*** Bug 133036 has been marked as a duplicate of this bug. ***
I confirm 2.2.2 builds & works fine in my test box (running PHP 5, Nagios and some other random stuff). I use the traditional prefork-mpm at the moment.
Thank you for keeping Apache ebuilds up-to-date, Michael Stewart.
Created attachment 88640 [details, diff] Couple of typo fixes I took a quick look at the ebuild. I did not change any actual functionality, but fixed couple of typos - please apply the patch at will. :-)
(In reply to comment #29) > Created an attachment (id=88640) [edit] > Couple of typo fixes > > I took a quick look at the ebuild. I did not change any actual functionality, > but fixed couple of typos - please apply the patch at will. :-) > @@ -405 +405 @@ - ewarn "Please add the 'apache2' flag to your USE variable and (re)install" + ewarn "Please add the 'apache2' flag to your USE variables and (re)install" Here, Michael was right since there is only one "USE" environment variable ;-).
Any News about putting 2.2.2 into Portage as testing?
Apache 2.2.2 in Portage does not create /var/www/localhost! It says during installing, it can't copy webroot ...
(In reply to comment #32) > Apache 2.2.2 in Portage does not create /var/www/localhost! It says during > installing, it can't copy webroot ... > What is the exact message you are getting?
Hello! Ok, i tryed now Apache 2.2.3 in Portage ... same Error! Here: * Installing default webroot to //var/www/localhost cp: angegebenes Ziel //var/www/localhost ist kein Verzeichnis (This means, that //var/www/localhost is NOT an directory!) chown: Zugriff auf //var/www/localhost nicht m
Hello! Ok, i tryed now Apache 2.2.3 in Portage ... same Error! Here: * Installing default webroot to //var/www/localhost cp: angegebenes Ziel //var/www/localhost ist kein Verzeichnis (This means, that //var/www/localhost is NOT an directory!) chown: Zugriff auf //var/www/localhost nicht möglich: Datei oder Verzichnis nicht gefunden (This means, that //var/www/localhost NOT found!)
Created attachment 93254 [details] apache-2.2.3.ebuild (fixed installing webroot) Ok, I found the bug! The ebuild just does not create /var/www/localhost as directory! I just put, when installing the webroot, "mkdir -p ${ROOT}/var/www/localhost" into the ebuild. This is also in the Apache 2.0 ebuild! But missing in the 2.2.X ebuilds! Now it works!
Shouldn't we put this ebuild into portage? It fixes the installation of the webroot!
This ebuild is in portage, though it is hard masked, so you have to add an entry to package.unmask to use it. Also, 2.0.58 and above in the 2.0 line also have the same webroot fix.
Are you sure? When I install Apache 2.2.3 from offical Portage, i get the error, that i can't copy the webroot!
Hmm. It looks like I never commited the change. Strange, I thought I had. It's now in CVS.
May I ask, when Apache 2.2.X will enter testing?
(In reply to comment #40) > May I ask, when Apache 2.2.X will enter testing? > When it's ready. :p Seriously though, I'm the only person working on it and my job has had me working upwards of 50 hours a week lately, duriing our busy summer period. Things are starting to slow down, so I should hopefully have more time to focus on this. There isn't much left to do, I just need to find the time to do it.
Hi! The Answer should be "When it's done" :D Well, do you need help? Maybe I could help? Atm, my Apache 2.2.3 eBuild is working without any Problems.
Yes, you can help, anyone can help. There are a number of modules (http://www.alteredeclipse.org/blog/projects/gentoo/apache/module-test-2.2) that do not work with apache 2.2. Tracking down the issues and getting them working would be a great help. There are a few bugs already filed for some of the modules (python, fastcgi, auth_ldap IIRC), if you come up with solutions for the others, file bugs with the solutions to those as well. Also, anyone who wants to test the upgrade path from 2.0 to 2.2 (and maybe even 1.3 to 2.2!) and then write some documentation for everything that needs to be done, general gotchas and such, that would be a big help as well.
(In reply to comment #43) > Yes, you can help, anyone can help. There are a number of modules > (http://www.alteredeclipse.org/blog/projects/gentoo/apache/module-test-2.2) > that do not work with apache 2.2. Tracking down the issues and getting them > working would be a great help. There are a few bugs already filed for some of > the modules (python, fastcgi, auth_ldap IIRC), if you come up with solutions > for the others, file bugs with the solutions to those as well. (In reply to comment #43) > Yes, you can help, anyone can help. There are a number of modules > (http://www.alteredeclipse.org/blog/projects/gentoo/apache/module-test-2.2) > that do not work with apache 2.2. Tracking down the issues and getting them > working would be a great help. There are a few bugs already filed for some of > the modules (python, fastcgi, auth_ldap IIRC), if you come up with solutions > for the others, file bugs with the solutions to those as well. Your list has net-www/mod_auth_ldap under "does not compile." It looks like this is a third party module. Should it be deprecated and replaced with mod_authnz_ldap which is now included with Apache?
One of the key reasons for upgrading to 2.2 is to use the new proxy_balancer module. For some reason this didn't get built the first time I installed Apache 2.2, but it did when I re-emerged it?? However, I think the ebuild should probably be updated as below to add it as one of the options enabled with "-D Proxy" in the conf.d file. # This is a mapping of module names to the -D option in APACHE2_OPTS # Used for creating optional LoadModule lines mod_defines="info:INFO status:INFO ldap:LDAP authnz-ldap:AUTH_LDAP proxy:PROXY proxy_connect:PROXY proxy_http:PROXY + proxy_balancer:PROXY ssl:SSL suexec:SUEXEC userdir:USERDIR" Additionally I notice that the server fails to start when using mod_svn. It fails with an error about DBD. I don't have the exact error handy but it looks a bit like a perl kind of error about a missing DBD driver? (Does mod_svn use perl under the bonnet?). Obviously this is no help without an exact error message, but I thought I would note it in case anyone else was seeing the same
(In reply to comment #45) Same goes for proxy_ajp. + proxy_ajp:PROXY
(In reply to comment #45) > Additionally I notice that the server fails to start when using mod_svn. It > fails with an error about DBD. I don't have the exact error handy but it looks > a bit like a perl kind of error about a missing DBD driver? (Does mod_svn use > perl under the bonnet?). Obviously this is no help without an exact error > message, but I thought I would note it in case anyone else was seeing the same I doubt the DBD error is related to mod_svn, at least if it's the same one that I'm getting: [Sat Oct 28 13:46:32 2006] [crit] (70023)This function has not been implemented on this platform: DBD: driver for [DBDriver unset] not available [Sat Oct 28 13:46:32 2006] [crit] (70023)This function has not been implemented on this platform: DBD: failed to initialize This is a harmless error. The bug for it being displayed has been fixed upstream and the fix will be in the next version of Apache. If you don't like this harmless error spamming up your logs, you can do one of two things: 1) disabled mod_authn_dbd by commenting out the LoadModule line 2) configure mod_authn_dbd http://httpd.apache.org/docs/2.2/mod/mod_authn_dbd.html
Earlier today I committed a modified depend.apache.eclass that allows modules that don't work with some versions of apache to specify which versions they do work with. Any module that doesn't work with all versions of apache should now use only need_apache (instead of need_apache1 or need_apache2) and pass as an argument to need_apache the versions that it supports (one or more of 1.3 2.0 2.2 or 2.x). For backwards compatibility, if there are no arguments passed to need_apache, it assumes all versions of apache are supported. I have just committed net-www/apache-2.2.3-r1. This should now be feature complete, with the following changes just going in: - Completed init script that implements all routines of apache2ctl - apache2ctl now is a symlink to the init script - Example virtual host configurations: name-based, ip-based, ssl-vhost - Correctly enabled mod_proxy_ajp and mod_proxy_balancer and used -D PROXY for enabling them at run-time - Added more upgrading instructions to the ebuild - USE=srvdir to use /srv/<FQDN>/www instead of /var/www/<FQDN> After you have upgrade to apache 2.2, you should add the following to /etc/portage/package.mask: <net-www/apache-2.2.0 This will prevent an accidental downgrade to apache 2.0 if you try to install a module that does not work with Apache 2.2 yet. If you are upgrading from apache 2.0 you will need to rebuild all your add on modules (php, mod_security, etc) Before I can unmask this, there are 2 things that need to be done: * Refactor/patch apr-util so that it uses the system's libtool for smoother building * Modify any modules that don't work with apache 2.2 to depend on apache-2.0 only (by using the updated need_apache call in depend.apache.eclass) Please test this extensively, including upgrading from 2.0.
Hi! It does not work here! I am upgrading from 2.2.3 to 2.2.3-r1 ... I get this Error: BlackBox / # emerge -av apache These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] net-www/apache-2.2.3-r1 [2.2.3] USE="mpm-worker ssl -debug -doc -ldap -mpm-event -mpm-peruser -mpm-prefork -no-suexec (-selinux) -srvdir% -static-modules (-threads%*)" 0 kB Total: 1 package (1 upgrade), Size of downloads: 0 kB Would you like to merge these packages? [Yes/No] >>> Emerging (1 of 1) net-www/apache-2.2.3-r1 to / * httpd-2.2.3.tar.bz2 MD5 ;-) ... [ ok ] * httpd-2.2.3.tar.bz2 RMD160 ;-) ... [ ok ] * httpd-2.2.3.tar.bz2 SHA1 ;-) ... [ ok ] * httpd-2.2.3.tar.bz2 SHA256 ;-) ... [ ok ] * httpd-2.2.3.tar.bz2 size ;-) ... [ ok ] * gentoo-apache-2.2.3-r1-20061126.tar.bz2 MD5 ;-) ... [ ok ] * gentoo-apache-2.2.3-r1-20061126.tar.bz2 RMD160 ;-) ... [ ok ] * gentoo-apache-2.2.3-r1-20061126.tar.bz2 SHA1 ;-) ... [ ok ] * gentoo-apache-2.2.3-r1-20061126.tar.bz2 SHA256 ;-) ... [ ok ] * gentoo-apache-2.2.3-r1-20061126.tar.bz2 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking httpd-2.2.3.tar.bz2 ;-) ... [ ok ] * checking gentoo-apache-2.2.3-r1-20061126.tar.bz2 ;-) ... [ ok ] * Selected MPM: worker >>> Unpacking source... >>> Unpacking httpd-2.2.3.tar.bz2 to /var/tmp/portage/net-www/apache-2.2.3-r1/work >>> Unpacking gentoo-apache-2.2.3-r1-20061126.tar.bz2 to /var/tmp/portage/net-www/apache-2.2.3-r1/work !!! ERROR: net-www/apache-2.2.3-r1 failed. Call stack: ebuild.sh, line 1568: Called dyn_unpack ebuild.sh, line 708: Called src_unpack apache-2.2.3-r1.ebuild, line 95: Called die !!! srvdir sed failed (1) !!! If you need support, post the topmost build error, and the call stack if relevant.
BlackBox / # emerge --info Portage 2.1.2_rc2-r2 (default-linux/x86/2006.1/server, gcc-4.1.1, glibc-2.5-r0, 2.6.18-gentoo-r3 i586) ================================================================= System uname: 2.6.18-gentoo-r3 i586 Geode(TM) Integrated Processor by AMD PCS Gentoo Base System version 1.12.6 Last Sync: Mon, 27 Nov 2006 06:50:01 +0000 distcc 2.18.3 i586-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.4 [enabled] dev-java/java-config: 1.3.7, 2.0.30 dev-lang/python: 2.4.4 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.4-r6 sys-apps/sandbox: 1.2.18.1 sys-devel/autoconf: 2.13, 2.61 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.14 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.17-r1 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i586-pc-linux-gnu" CFLAGS="-march=k6-2 -Os -mmmx -m3dnow -pipe -fomit-frame-pointer -mfpmath=387" CHOST="i586-pc-linux-gnu" CONFIG_PROTECT="/etc /var/bind" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/revdep-rebuild /etc/splash /etc/terminfo" CXXFLAGS="-march=k6-2 -Os -mmmx -m3dnow -pipe -fomit-frame-pointer -mfpmath=387 -fvisibility-inlines-hidden" DISTDIR="/usr/portage/distfiles" EMERGE_DEFAULT_OPTS="" FEATURES="autoconfig ccache distlocks metadata-transfer parallel-fetch sandbox sfperms strict" GENTOO_MIRRORS="ftp://pandemonium.tiscali.de/pub/gentoo/" LANG="de_DE.utf8" LC_ALL="de_DE.utf8" LDFLAGS="-Wl,-O1" LINGUAS="de" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_EXTRA_OPTS="--exclude-from=/etc/portage/rsync_excludes" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/portage/local" SYNC="rsync://rsync.de.gentoo.org/gentoo-portage" USE="x86 / acpi alsa apache2 berkdb bzip2 caps cdinstall clamav crypt cups dedicated elibc_glibc ftp gd gpm iconv imap input_devices_keyboard input_devices_mouse jabber java javascript jpeg jpeg2k kernel_linux ldap linguas_de mbox mmx mp3 mysql mysqli ncurses nls nptl odbc offensive pam pcre php png postgres readline samba sasl session slang snmp spell ssl symlink tcpd threads tiff truetype unicode usb userland_GNU vhosts video_cards_cyrix video_cards_fbdev video_cards_nsc video_cards_v4l video_cards_vesa video_cards_vga vorbis xinetd xml zlib" Unset: CTARGET, INSTALL_MASK
The logic bug that was causing USE=-srvdir to fail has now been fixed.
Thanks! Working perfect here!
Regarding my own comment #24, mod-python-3.2.10 can run under apache 2.2.x already, so you do not have to wait for final mod-python-3.0. ;) And 3.2.10 is available at least on ~x86. ;-)
There's no LoadModule for mod_authnz_ldap in httpd.conf as of 2.2.3-r1; I added it as part of the IfDefine LDAP (as below), and all's well. [Whether it should be AUTH_LDAP rather than just LDAP... well, that sounds like a package maintainer call to me]. <IfDefine LDAP> LoadModule ldap_module modules/mod_ldap.so LoadModule authnz_ldap_module modules/mod_authnz_ldap.so </IfDefine>
Hmm, apache-2.2.4 is out it seems: 2.2.4 : Tagged on January 5, 2007 And there are quite a few bugfixes: http://svn.apache.org/repos/asf/httpd/httpd/tags/2.2.4/CHANGES Anybody working on that? Not available in layman as well :-(
(In reply to comment #56) > Anybody working on that? As soon as I have finished the module cleanup I'll try to get Apache 2.2 going. ;) > Not available in layman as well :-( Sure, as there is no overlay for Apache stuff that I know of, at least nothing remotely official... Best regards, CHTEKK.
Created attachment 107641 [details] apache-2.2.4.ebuild Just a version bump of the 2.2.3-r3 ebuild. Needs the new patch tarball as the 99_* series security fixes are now upstream. Note: gentoo-apache-2.2.4-20070121.tar.bz2 (the patches) NEED to be in DISTDIR, I couldn't get it to unpack them from FILESDIR.
Created attachment 107642 [details] gentoo-apache-2.2.4-20070121.tar.bz2 The patches, based on gentoo-apache-2.2.3-r1-20061126.tar.bz2
Apache APR 1.2.8 and Apache APR Util 1.2.8 are out! We should update them to. Renaming just works ;) Apache 2.2.4, APR 1.2.8, APR-Util 1.2.8 compile here fine and works at least for me fine ;)
Created attachment 107665 [details] apr-1.2.8.ebuild apr-1.2.8.ebuild
Created attachment 107666 [details] apr-util-1.2.8.ebuild apr-util-1.2.8.ebuild
First thanks a lot for the new ebuilds! However I've seen that the mpm-itk patch/use-flag (among others) has disappeared compared to the 2.0.x versions. Is there a reason for this removal? Incompatibility? Thanks
Looks like mpm-threadpool & mpm-leader don't exist in the 2.2.x tree. mpm-metux (http://www.sannes.org/metuxmpm/) hasn't released a patch since 2.0.48/49 (and I think the ebuilds stopped including it earlier than that). No idea about mpm-itk (http://home.samfundet.no/~sesse/mpm-itk/). I haven't tried it, but the last update was Oct. 2006. Try it and see if the patch applies cleanly.
Any new News?
Created attachment 110152 [details, diff] ebuild patch for mpm-itk support Attached a patch to the apache-2.2.4.ebuild which adds the mpm-itk patch. It compiles without problems here and after a short test it seems to work. I compiled apache2 with php 5 and posix_getuid() returns the correct value. (configured a vhost to change user)
Is there anything I can to to speed up the unmaksing of this package? I'll probably will start testing tonight together with mpm_itk
I can report that apache 2.2 runs on my server for 2 weeks without problems now. (using mpm itk)
*** Bug 170014 has been marked as a duplicate of this bug. ***
Are we ready to go for testing?
Hmm, it seems that Michael Stewart (the maintainer?) is RETIRED ... And now?
I've got it running on my box. Anything we can do to help move this forward?
Running apache 2.2.4 with mod python & php since: Mon Jan 22 04:42:25 2007 >>> net-www/apache-2.2.4 on production system with many many hits, no problems. I think, it's time to add to stable tree.
(In reply to comment #73) > Running apache 2.2.4 with mod python & php since: > > Mon Jan 22 04:42:25 2007 >>> net-www/apache-2.2.4 > > on production system with many many hits, no problems. > > I think, it's time to add to stable tree. > forgot to say: arch x86
I've managed to install it fine using the mpm-itk patch on amd64 This hasn't been deployed live yet, still building the application in tomcat. I upgraded for the mod_proxy_ajp module.
I don't think the issue is does if it works or not -- I too am using 2.2 on all my systems, some high volume. The question is: are there any outstanding issues (this bug's dependencies state no), and does the upgrade path from 2.0 to 2.2 work? If, especially the later, is met I too would like to push this for stable. The question remains whether or not we have a a maintainer that can do so.
I've noticed in apache-2.2.4 it is now installing /usr/sbin/apxs and not apxs2 which php and likely other modules are still calling. Is this a bug in the apache-2.2 ebuild or an attempt to standardize the apache install. Ramin
(In reply to comment #77) > I've noticed in apache-2.2.4 it is now installing /usr/sbin/apxs and not apxs2 > which php and likely other modules are still calling. Is this a bug in the > apache-2.2 ebuild or an attempt to standardize the apache install. > Both. Fixed in 2.2.4-r1 by installing *2 symlinks.
(In reply to comment #78) The same problem appears with suexec binary. Apache looks for /usr/sbin/suexec and mod_suexec.c is compiled with /usr/sbin/suexec2 path. A temp fix for everyone using this ebuild is making a symlink by hand until the ebuild fixes the problem. > (In reply to comment #77) > > I've noticed in apache-2.2.4 it is now installing /usr/sbin/apxs and not apxs2 > > which php and likely other modules are still calling. Is this a bug in the > > apache-2.2 ebuild or an attempt to standardize the apache install. > > > Both. Fixed in 2.2.4-r1 by installing *2 symlinks. >
apache-2.2.4-r1 unmasked; closing this looong bug. For any issues w/ apache-2.2*, please file new bugs.
