Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 18017 - emerge sync fails with apache/php_mod conflict
Summary: emerge sync fails with apache/php_mod conflict
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High critical (vote)
Assignee: PHP Bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-22 17:45 UTC by david mattatall
Modified: 2003-04-03 03:22 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description david mattatall 2003-03-22 17:45:59 UTC
!!! all ebuilds that could satisfy ">=net-www/apache-2.0.43-r1" have been 
masked.
!!!    (dependency required by "dev-php/mod_php-4.3.1" [ebuild])

!!! Problem with ebuild dev-php/mod_php-4.3.1
!!! Possibly a DEPEND/*DEPEND problem.

!!! Depgraph creation failed.

If I remove line 27:

apache2? ( >=net-www/apache-2.0.43-r1 )

it works without problem.

Reproducible: Didn't try
Steps to Reproduce:
1.
2.
3.

Actual Results:  
guh?

Expected Results:  
Bah?
Comment 1 Joakim 2003-03-24 17:22:34 UTC
You don't give whole sceenario of what you are doing, but I assume you try to emerge 
apache2? First thing I think you need to do is to run a '#emerge sync' to get your 
portage tree uptodate. Latest apache is 2.0.44 and not 2.0.43-r1. Then to get those 
packages you need 'ACCEPT_KEYWORDS="~x86"' in your /etc/make.conf and also 
'USE="apache2"   
 
OR 
 
You can get them running this 'ACCEPT_KEYWORDS="~x86" emerge apache 
mod_php 
 
But this latest is just a guess as I already have those running so I can't try, but it 
should be safe at least. 
 
 
Comment 2 Arto Kitula 2003-04-02 02:17:20 UTC
With latest sync, doing

# emerge -u world

produced same error. I have 2.0.44 apache installed.
Comment 3 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2003-04-03 01:01:16 UTC
david, did try joakim's advice ? 
If yes to advice, did it resolve the problem?
If no to either, please post your emerge info output and the commandline you were trying to use.
Comment 4 david mattatall 2003-04-03 03:22:54 UTC
This is actually a bug in ufed. I had turned on the apache2 use flag while doing some testing 
with Apache2. Once I was done, I uninstalled apache2 and removed the use flag using 
ufed...the flag was still there when I checked a few days ago. So ta-da my problem is fixed 
now. I should file a bug report for ufed.