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