1 |
On Tue, Jan 13, 2009 at 8:19 PM, Michael P. Soulier |
2 |
<msoulier@×××××××××××××.ca> wrote: |
3 |
> So, I noticed this on an emerge |
4 |
> |
5 |
> !!! Multiple package instances within a single package slot have been pulled |
6 |
> !!! into the dependency graph, resulting in a slot conflict: |
7 |
> |
8 |
> www-client/mozilla-firefox:0 |
9 |
> |
10 |
> ('ebuild', '/', 'www-client/mozilla-firefox-2.0.0.19', 'merge') pulled in by |
11 |
> =www-client/mozilla-firefox-2* required by ('installed', '/', |
12 |
> 'net-www/mplayerplug-in-3.50', 'nomerge') |
13 |
> (and 1 more) |
14 |
> |
15 |
> ('installed', '/', 'www-client/mozilla-firefox-3.0.5', 'nomerge') pulled in |
16 |
> by |
17 |
> www-client/mozilla-firefox required by world |
18 |
> |
19 |
> So, I interpret this as the mplayer plugin not being available for firefox |
20 |
> 3.0, which is why it's pulling in the 2.0 stream. So, my best solution is |
21 |
> probably just to uninstall the mplayer plugin, is that right? |
22 |
> |
23 |
> It seems to work fine in firefox 3.0. If I want to run the risk and keep it, |
24 |
> is masking out firefox 2.0 the way to go? |
25 |
> |
26 |
> Thanks, |
27 |
> Mike |
28 |
|
29 |
After getting fed up with emerge/compile issues with mplayerplug-in i |
30 |
switched to net-www/gecko-mediaplayer and it seems to work okay. |
31 |
|
32 |
Paul |