I currently have apache2 installed with mod_php 4.3.2-r2. Unfortinatly the dependency checking system keeps telling me I need to upgrade to version 4.3.2 of mod_php, this whouldn't be all that bad but the 4.3.2 dosent correctly detect apache2, and it insists on "upgrading" apache to the 1.x branch. I don't know if this is how it's supose to work. If I install the unstable branch (apache 2.x) it doesn't tell me I have to upgrade to stable branch (apache 1.x), but mod_php seem to insist on upgrading to the stable branch. Reproducible: Always Steps to Reproduce: 1. ACCEPT_KEYWORDS="~x86" emerge apache (installes apache 2.0.46) 2. ACCEPT_KEYWORDS="~x86" emerge mod_php (installes mod_php 4.3.2-r2) 3. emerge -up world Actual Results: >> emerge -up world These are the packages that I would merge, in order: Calculating world dependencies ...done! [ebuild N ] dev-libs/mm-1.2.1 [ebuild U ] net-www/apache-1.3.27-r3 [2.0.46] [ebuild N ] media-libs/tiff-3.5.7-r1 [ebuild U ] dev-php/mod_php-4.3.2 [4.3.2-r2] Expected Results: Shouldn't list any files to update.
1. Apache1 and Apache2 are slotted, you can have both of them installed simultaneously. mod_php is also slotted to the version of apache you are building it for. 2. 4.3.2-r2 is intended for Apache2, and not for only apache1 users presently. The problem here comes because you do 'emerge -up world' _without_ the ACCEPT_KEYWORDS="~x86". Since apache2 and and php-4.3.2-r2 are not available to ~x86, it wishes to downgrade you. It only doesn't show up as a downgrade as it is slotted.
