upgrading the apache package will not make mod_ssl being upgraded (tested it with apache-1.3.26-r4 to 1.3.27 upgrade: mod_ssl is still 2.8.10) since mod_ssl releases comes in sync with apache.
just copied .10 to .11 and tested it out ... ssl was workin on my machines ... added to cvs ... woodchip, dont know if you want to test anything else ...
yup i think all that mod_ssl needs is a simple version bump. Spanky, Im afraid Im realy busy this week, would you mind taking care of this for me? I think all that needs to be done, is bump the mod_ssl revision in the apache ebuild (if its not already done) and bump the revision of the mod_ssl ebuild on CVS. If not, I'll get to it ASAP, probably this weekend.
already done ;)
Im experiencing the same problems: emerge updated to apache-1.3.28 but mod_ssl has been left behind.
I think the reason is because apache-1.3.28 has been marked stable and mod_ssl-2.8.15 has not. Marking mod_ssl-2.8.15 as stable should solve the problem.