| 1 |
So, I noticed this on an emerge |
| 2 |
|
| 3 |
!!! Multiple package instances within a single package slot have been pulled |
| 4 |
!!! into the dependency graph, resulting in a slot conflict: |
| 5 |
|
| 6 |
www-client/mozilla-firefox:0 |
| 7 |
|
| 8 |
('ebuild', '/', 'www-client/mozilla-firefox-2.0.0.19', 'merge') pulled in by |
| 9 |
=www-client/mozilla-firefox-2* required by ('installed', '/', |
| 10 |
'net-www/mplayerplug-in-3.50', 'nomerge') |
| 11 |
(and 1 more) |
| 12 |
|
| 13 |
('installed', '/', 'www-client/mozilla-firefox-3.0.5', 'nomerge') pulled in |
| 14 |
by |
| 15 |
www-client/mozilla-firefox required by world |
| 16 |
|
| 17 |
So, I interpret this as the mplayer plugin not being available for firefox |
| 18 |
3.0, which is why it's pulling in the 2.0 stream. So, my best solution is |
| 19 |
probably just to uninstall the mplayer plugin, is that right? |
| 20 |
|
| 21 |
It seems to work fine in firefox 3.0. If I want to run the risk and keep it, |
| 22 |
is masking out firefox 2.0 the way to go? |
| 23 |
|
| 24 |
Thanks, |
| 25 |
Mike |
| 26 |
-- |
| 27 |
Michael P. Soulier <msoulier@×××××××××××××.ca> |
| 28 |
"Any intelligent fool can make things bigger and more complex... It takes a |
| 29 |
touch of genius - and a lot of courage to move in the opposite direction." |
| 30 |
--Albert Einstein |
Archives