Please test and mark stable new-style apache.
net-www/gentoo-webroot-default-0.2 (needed by both apache-1 and apache-2
net-www/lingerd-0.94 (needed by apache-1 if USE lingerd)
net-www/apache-1.3.33-r12 net-www/mod_ssl-2.8.24-r1 <-- need to be done as close
together as possible due to circular deps
Note that you will need to have apr and apr-util stable as well (see bug 105516)
For those of you keywording these ebuilds, keep in mind these revision bumps are
brand new as of Sept 18th and have not been through the 3 week test cycle like
they should have been. The changes in them are big enough to warrant it.
I have marked net-www/gentoo-webroot-default-0.2 and net-www/apache-2.0.54-r31
stable on amd64. They work well here, although I had not noticed they
hadn't spent the recommended amount of time in testing. Waiting on ATs to test
net-www/apache-1.3.33-r12 and friends.
subversion-1.2.3 (the stable one) has these dependances :
apache2? ( >=net-www/apache-2.0.48 !>=net-www/apache-2.0.54-r30 )
so we need to mark 1.2.3-r1 stable to not block apache-2.0.54-r31
Tested the following:
Apache would not build (see bug #31239) until I specifically installed
=db-1.85-r1 (should this be a DEPEND?)
After that, all packages built.
Apache (built with lingerd keyword) starts and serves pages with lingerd running.
Pages are also served on https if -D SSL is passed.
Right all requested packages in this bug are stable on amd64. Thanks to aja for
testing the 1.3.* stuff.
www-apache/mod_chroot-0.4 is building and working fine with apache2 on an amd64
It would be nice if it could at least be keyworded ~amd64
ppc stable for a while now, removing from CC.
hppa seems to be up to date. Removing CC.
mips: it does not look like you have a stable new-style ebuild for 1.3. the apache herd will no longer support old-style configuration after March 1, if you would like your arch supported for apache 1.3 please test and keyword. Thanks!
(In reply to comment #13)
> mips: it does not look like you have a stable new-style ebuild for 1.3. the
> apache herd will no longer support old-style configuration after March 1, if
> you would like your arch supported for apache 1.3 please test and keyword.
All old-style ebuilds have been removed from the tree, mips no longer has a stable apache 1.3 (though there is a stable apache 2.0). Assigning this bug directly to mips so I don't have to look at it anymore. Mips can close it if you don't care about apache 1.3 anymore.
None of MIPS devs use apache-1.3. We are not aware of users with apache-1.3 either. Closing the bug.
(Is "FIXED" correct resolution in this case?)