"<=apache-1.99" is in my 'world' file. "-apache2" is in my USE flag # emerge -upv mod_php These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild U ] dev-java/java-config-1.2.6 [1.2.5] 12 kB [ebuild U ] dev-util/yacc-1.9.1-r2 [1.9.1-r1] 0 kB [ebuild N ] net-www/apache-2.0.49 +berkdb +gdbm +ldap 0 kB [ebuild U ] net-libs/libwww-5.4.0-r2 [5.4.0-r1] +mysql +ssl 0 kB [ebuild U ] dev-php/mod_php-4.3.6_rc2 [4.3.4-r4] +X -apache2 +berkdb +crypt -curl -doc -fdftk -firebird -flash +freetds +gd -gd-external +gdbm -gmp +imap -informix -ipv6 +java +jpeg +ldap -mcal -memlimit +mysql +nls -oci8 -odbc +pam +pdflib +png -postgres -qt -snmp +spell +ssl +tiff +truetype +xml2 -yaz 3,865 kB Total size of downloads: 3,877 kB Help! I don't want apache2! Reproducible: Always Steps to Reproduce: 1. emerge -upv mod_php 2. 3. Actual Results: portage wants to install apache2 Expected Results: Not install apache2 I currently have apache-1.3.29-r1 installed, but not apache2. I have mod_php-4.3.4-r4 installed.
do 'emerge mod_php' and see what it does try to install we've had issues with it spitting out the wrong pretend deps before, due to how we use slots. also, a good way to make really sure, is to install apache1 yourself before mod_php.
portage attempts to download and compile apache2. apache1 has been installed previously.
very strange. try: rm /usr/portage/metadata/cache/net-www/apache-* /var/cache/edb/dep/net-www/apache-* then run the emerge -p again.
The problem arises when I run: emerge -up mod_php not when I run: emerge -p mod_php After I removed the files, I ran emerge -upv mod_php There are less dependencies now, because java-config and yacc were upgraded during the test to see if apache2 would be installed # emerge -upv world These are the packages that I would merge, in order: Calculating world dependencies /has_version() in global scope: net-www/apache-2.0.48 has_version() in global scope: net-www/apache-2.0.48-r2 has_version() in global scope: net-www/apache-2.0.48-r4 has_version() in global scope: net-www/apache-2.0.47 has_version() in global scope: net-www/apache-2.0.48-r1 has_version() in global scope: net-www/apache-2.0.48-r3 has_version() in global scope: net-www/apache-2.0.47-r1 ...done! [ebuild N ] net-www/apache-2.0.49 +berkdb +gdbm +ldap 0 kB [ebuild U ] net-libs/libwww-5.4.0-r2 [5.4.0-r1] +mysql +ssl 0 kB [ebuild U ] dev-php/mod_php-4.3.6_rc2 [4.3.4-r4] +X -apache2 +berkdb +crypt -curl -doc -fdftk -firebird -flash +freetds +gd -gd-external +gdbm -gmp +imap -informix -ipv6 +java +jpeg +ldap -mcal -memlimit +mysql +nls -oci8 -odbc +pam +pdflib +png -postgres -qt -snmp +spell +ssl +tiff +truetype +xml2 -yaz 0 kB Total size of downloads: 0 kB
i'm passing this on to the portage people as the mod_php DEPEND stuff has not been touched since 4.3.4-r4.
-u will try to update dependencies, apache is a dependency and is therefore upgraded to the latest unmasked version. The problem here is that it ignores SLOT information and will upgrade even if the new version is in a different SLOT, this is discussed in bug 4698. Until that one is fixed there are two possible workarounds: - for users: mask >=apache-2 in /etc/portage/package.mask - for ebuilds: depend on =apache-1* if the apache2 flag is not set
Simple clean workaround: /usr/portage/dev-php/mod_php/mod_php-4.3.6.ebuild ln 5: IUSE="${IUSE} apache2" should be ln 5: IUSE="${IUSE} apache-1" I still got some version errors, but i wrote that off to the failed tests searching for apache2. simple reason for this is because mod_php's base only depends on apache-1.x not apache-2.x (yet). I suppose by the next stable release of php(5) apache 2 might be stable enough. /just though i'd put a real straight forward responce to the problem. /Sorry if it is fixed in the next sync.
marius: your ebuild solution there is not correct. the apache2 use flag is defined as PREFER apache2 support where something is available for both apache1 AND apache2. for anybody that wants only the old apache, I strongly recommend adding '>=apache-2' to /etc/portage/package.mask.
it happens to me to... it try to upgrade my apache2 (2.0.52-r1) to another versione of apache2 (2.0.54-r4) ... it happen from the upgrade to the 2Q-2005
(In reply to comment #9) > it happens to me to... it try to upgrade my apache2 (2.0.52-r1) to another > versione of apache2 (2.0.54-r4) > > ... > it happen from the upgrade to the 2Q-2005 That is correct behaviour. This bug is about only the case of upgrading apache1 to apache2.
*** This bug has been marked as a duplicate of 4698 ***
