All ebuilds for net-www/apache prior to 1.3.33-r1 [1] are incompatible with older versions of db, gdbm and ndbm with regards to mod_ssl, resulting in a broken set-up when ssl is enabled. The fix has been back-ported to 1.3.33-r1. Arches, please test apache-1.3.33-r1 and mark stable. Thanks, [1] apache-1.3.33-r1 has been in the tree for several months as part of the big Apache herd refresh; because of this, the 'refreshed' ebuild has been moved to -r2 and -r1 is now a copy of -r0 + fix - you may need to 'cvs up' before keywording.
apache ebuild 1.3.33-r1 wants to emerge apache-1.3.32-r1 ???? Is this an issue ???? emerge --update --pretend --verbose --deep apache These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild N ] dev-libs/mm-1.2.1 211 kB [ebuild N ] net-www/apache-1.3.33-r1 +pam +ssl 3,161 kB [ebuild N ] net-www/apache-1.3.32-r1 +pam 2,430 kB [ebuild N ] net-www/mod_ssl-2.8.21 0 kB Total size of downloads: 5,803 kB
Thanks for the testing Robert. I've just committed a DEPEND fix to mod_ssl-2.8.21 which should takes care of this. Can you emerge --sync and give it another shot ?
mod_ssl-2.8.21 now depends on apache-1.3.33-r2, which is still ~arch. Was this a typo or do you want apache-1.3.33-r2 stable instead of -r1?
Elfyn, I have emerged =apache-1.3.33 yesterday to avoid installing 1.3.32-r1 and did an emerge --update after 1.3.33 was on disk. Portage did not want to emerge 1.3.32-r1 updating apache from 1.3.33 to 1.3.33-r1, so I think my reported bug is only reproducible if apache is not installed (new install). Sorry, can't test it for you, cause I now have 1.3.33-r1 up and running...
Sorry folks, mod_ssl's DEPEND (ugh !) is now fixed and will now work with 1.3.32*, 1.3.33 or 1.3.33-r1. Seems as though I didn't test the upgrade with enough versions so I'm doing that now - please hold off on the keywording until I report back. Thanks all and apologies for the breakage. :)
@Weeve: No typo, just broken deps - i.3.33-r1 is the ebuild to go stable. Okay, I've tested upgrading/downgrading to and from 1.3.32*, 1.3.33 and 1.3.33-r1 and a clean install - all go. Marking x86 stable. Arches, please test apache-1.3.33-r1 and mark stable. :) Thanks,
If I try to emerge mod_ssl after having emerged apache-1.3.33-r1 I get the following; >>> emerge (2 of 2) net-www/mod_ssl-2.8.21 to / >>> md5 src_uri ;-) mod_ssl-2.8.21-1.3.32.tar.gz >>> Unpacking source... >>> Unpacking mod_ssl-2.8.21-1.3.32.tar.gz to /var/tmp/portage/mod_ssl-2.8.21/work >>> Source unpacked. Configuring mod_ssl/2.8.21 for Apache/1.3.32 ./configure:Error: The mod_ssl/2.8.21 can be used for Apache/1.3.32 only. ./configure:Error: Your Apache source tree under /usr is version 1.3.33. ./configure:Hint: Please use an extracted apache_1.3.32.tar.gz tarball ./configure:Hint: with the --with-apache option, only. !!! ERROR: net-www/mod_ssl-2.8.21 failed. !!! Function src_compile, Line 44, Exitcode 1 !!! bad ./configure !!! If you need support, post the topmost build error, NOT this status message. This is using the latest versions of the ebuilds available in CVS at the time of this writing.
I have just failed emergeing apache with ssl support. The error: >>> original instance of package unmerged safely. * * Please remember to update your config files in /etc/apache * as --datadir has been changed to /var/www/localhost! * >>> Regenerating /etc/ld.so.cache... * Caching service dependencies... >>> net-www/apache-1.3.33-r1 merged. >>> clean: No packages selected for removal. >>> emerge (2 of 2) net-www/mod_ssl-2.8.21 to / >>> md5 src_uri ;-) mod_ssl-2.8.21-1.3.32.tar.gz >>> Unpacking source... >>> Unpacking mod_ssl-2.8.21-1.3.32.tar.gz to /var/tmp/portage/mod_ssl-2.8.21/work >>> Source unpacked. Configuring mod_ssl/2.8.21 for Apache/1.3.32 ./configure:Error: The mod_ssl/2.8.21 can be used for Apache/1.3.32 only. ./configure:Error: Your Apache source tree under /usr is version 1.3.33. ./configure:Hint: Please use an extracted apache_1.3.32.tar.gz tarball ./configure:Hint: with the --with-apache option, only. !!! ERROR: net-www/mod_ssl-2.8.21 failed. !!! Function src_compile, Line 44, Exitcode 1 !!! bad ./configure !!! If you need support, post the topmost build error, NOT this status message. My emerge info: root@scorsese2 localhost # emerge info Portage 2.0.51.19 (default-linux/x86/2004.3, gcc-3.3.5, glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r4 i686) ================================================================= System uname: 2.6.11-gentoo-r4 i686 AMD Athlon(tm) XP 2200+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Mar 23 2005, 10:43:03)] distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] dev-lang/python: 2.3.4-r1 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.4.22-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-pipe -O3 -march=athlon-xp -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-pipe -O3 -march=athlon-xp -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig buildpkg ccache distcc distlocks fixpackages sandboxsfperms" GENTOO_MIRRORS="ftp:///ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://ftp-mirror.internap.com/pub/gentoo/ http://gentoo.ccccom.com http://gentoo.mirror.sdv.fr http://distro.ibiblio.org/pub/Linux/distributions/gentoo/ http://gentoo.mirrors.pair.com/http://gentoo.ccccom.com/ http://gentoo.osuosl.org/" MAKEOPTS="-j9" PKGDIR="/var/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage-fabrica /usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 alsa apm arts avi berkdb bitmap-fonts crypt cups emboss encode fam font-server foomaticdb fortran gdbm gif gpm gtk2 imlib jpeg ldap libg++ libwww mad mikmod motif mp3 mpeg mysql ncurses oggvorbis opengl oss pam pdflib perl png python quicktime readline sdl slang spell ssl svga tcpd truetype truetype-fonts type1-fonts xml2 xmms xv zlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS Is there another mod_ssl to be used?
What's the story with mod_ssl and apache here?
Folks, I'm really sorry this has been left broken for so long - I've had little-to-no access to the 'net in the last week or so. I won't be back online properly until Monday night/Tuesday morning so I have therefore hard-masked it (apache-1.3.33-r1), and will fix this bugger up then. If someone else from the Apache herd could look into this/fix the deps the 1.3.33-release mod_ssl, I'd appreciate it. Thanks for the testing & apologies for wasting everyones time !
Hmm - seems that it was a bad idea to hardmask 1.3.33-r1 after it has been marked stable. As I 've reported earlier I had some 'issues' upgrading to 1.3.33-r1, but FIRST upgrading to 1.3.33 and then to 1.3.33-r1 did avoid these dependency issues. Now, as you have marked 1.3.33-r1 as hard-masked, I got 2(!!) downgrades by running emerge, one caused by apache itself (to 1.3.33 - that's okay) and the other to apache-1.3.32-r1 (which is IMHO not ok!) caused by mod_ssl... Hope that helps... emerge --update --pretend --verbose --deep world These are the packages that I would merge, in order: Calculating world dependencies ...done! [ebuild UD] net-www/apache-1.3.32-r1 [1.3.33-r1] +pam 0 kB [ebuild UD] net-www/apache-1.3.33 [1.3.33-r1] +pam +ssl 0 kB
ok, this should be fixed now i'm wondering why 1.3.33 suppport was added to the 2.8.21 ebuild, you need 2.8.22... please see the changelogs for details
reopening bug, arch teams, please test and mark stable, thx
please test the mod_ssl-2.8.22 ebuild as well
now it's happy. sparc stable.
stable ia64
stable on hppa
amd64 stable, sorry for the big delay
Marked ppc stable, sorry for the delay. (And the wrong bug # in the commit :p)
This bug is out of date as a later revision is already stable on on archs.
