After doing an 'emerge rysnc' I checked packages in my world database that needed to be updated. OpenSSL 0.9.6g went to OpenSSL 0.9.6i. I emerged the new OpenSSL package, and restarted all programs dependent on it. Checking phpinfo() under Apache revealed that it was still using OpenSSL 0.9.6g instead of i. I then re-emerged mod_ssl--same version as before, 2.8.12--and restarted Apache again. This time phpinfo() reported mod_ssl was linked to the new version of OpenSSL. I'm not sure if this is a "feature" or an error, but in the instance, when installing a new version of a crypto package, it would make sense to have that version automatically used in its most common application. Reproducible: Always Steps to Reproduce: 1. Install Gentoo with Apache/openssl/mod_ssl 2. emerge rysnc 3. update just openssl Actual Results: mod_ssl still used old version. Expected Results: mod_ssl would use the new openssl package. From phpinfo() After updating openssl and restarting Apache, but before emerge mod_ssl again: Apache/1.3.27 (Unix) (Gentoo/Linux) mod_gzip/1.3.19.1a mod_ssl/2.8.12 OpenSSL/0.9.6g PHP/4.3.1 After emerging mod_ssl and restarting Apache having already emerged the new openssl pacakge a: Apache/1.3.27 (Unix) (Gentoo/Linux) mod_gzip/1.3.19.1a mod_ssl/2.8.12 OpenSSL/0.9.6i PHP/4.3.1
please make a new -rX with >=openssl-0.9.6i as depend
please go right ahead, this is a community project.
fixed apache with -r3 (stable) and -r4 (unstable) now php has to be fixed
mod_ssl also fixed
umm, updating DEPEND is wrong ... you should add mod_ssl and stuff as a PDEPEND to the openssl ebuild ... or mark this bug as a duplicate of the bugs which discuss auto updating packages when libraries are updated ...
SpanKY do you know the bugid from marking this as duplicate ?
*** This bug has been marked as a duplicate of 1991 ***