I'm getting this since upgrading to firefox 3.0.5. I don't use the "xulrunner" use flag which seems to be responsible for the conflict. !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: www-client/mozilla-firefox:0 ('ebuild', '/', 'www-client/mozilla-firefox-2.0.0.19', 'merge') pulled in by =www-client/mozilla-firefox-2* required by ('installed', '/', 'www-client/epiphany-2.22.3', 'nomerge') =www-client/mozilla-firefox-2* required by ('installed', '/', 'gnome-extra/yelp-2.22.1-r2', 'nomerge') =www-client/mozilla-firefox-2* required by ('installed', '/', 'media-video/totem-2.22.2-r1', 'nomerge') (and 1 more) ('installed', '/', 'www-client/mozilla-firefox-3.0.5', 'nomerge') pulled in by www-client/mozilla-firefox required by world It may be possible to solve this problem by using package.mask to prevent one of those packages from being selected. However, it is also possible that conflicting dependencies exist such that they are impossible to satisfy simultaneously. If such a conflict exists in the dependencies of two different packages, then those packages can not be installed simultaneously. For more information, see MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. Reproducible: Always
If you want firefox-3 and keep the other packages that need older xulrunner/firefox, you need to use the xulrunner useflag. It's quite simple, really.
I guess nothing told me this. I just did a normal "emerge -uD world" and firefox 3 was installed, then now with portage 2.1.6.4 I get this.
That's not a portage problem. It's something, that became rather well known in unstable, ever since firefox 3 arrived (though most people seen that as a conflict, when a package depended on either firefox 2 or xulrunner 1.9, depending on useflags). AFAIK, by now in unstable, every package that depended once on firefox, can depend on xulrunner 1.9 now. I'm not sure how far stable got.
(In reply to comment #2) > I guess nothing told me this. > > I just did a normal "emerge -uD world" and firefox 3 was installed, then now > with portage 2.1.6.4 I get this. > The postinst message of firefox-3 clearly warns about this issue.
(In reply to comment #4) > The postinst message of firefox-3 clearly warns about this issue. Hopefully I haven't missed anything obvious, but I'm getting the same error BEFORE installing firefox 3, so don't see any error message like this. Interestingly, I can resolve it by rearranging the order of my install, from "[ebuild U ] sys-libs/e2fsprogs-libs-1.41.3 [1.41.2] USE="nls" 479 kB [ebuild U ] app-editors/nano-2.1.7 [2.1.5] USE="ncurses nls unicode -debug -justify -minimal -slang -spell" 1,435 kB [ebuild U ] sys-apps/busybox-1.12.2-r1 [1.11.1] USE="pam -debug -make-symlinks -savedconfig (-selinux) -static" 1,974 kB [ebuild U ] sys-devel/automake-1.10.2 [1.10.1-r1] 915 kB [ebuild N ] dev-lang/swig-1.3.36 USE="R java perl python -chicken -clisp -doc -guile -lua -mono -mzscheme -ocaml -octave -php -pike -ruby -tcl -tk" 0 kB [ebuild N ] media-libs/lcms-1.17 USE="jpeg python tiff zlib" 878 kB [ebuild N ] net-libs/xulrunner-1.9.0.5 USE="dbus gnome ipv6 java -custom-optimization -startup-notification" 33,307 kB [ebuild U ] www-client/mozilla-firefox-3.0.5 [2.0.0.19] USE="dbus%* gnome"" to "[ebuild U ] sys-devel/automake-1.10.2 [1.10.1-r1] [ebuild N ] dev-lang/swig-1.3.36 USE="R java perl python -chicken -clisp -doc -guile -lua -mono -mzscheme -ocaml -octave -php -pike -ruby -tcl -tk" [ebuild U ] sys-libs/e2fsprogs-libs-1.41.3 [1.41.2] [ebuild U ] app-editors/nano-2.1.7 [2.1.5] [ebuild U ] sys-apps/busybox-1.12.2-r1 [1.11.1] [ebuild N ] media-libs/lcms-1.17 USE="jpeg python tiff zlib" [ebuild N ] net-libs/xulrunner-1.9.0.5 USE="dbus gnome ipv6 java -custom-optimization -startup-notification" [ebuild U ] www-client/mozilla-firefox-3.0.5 [2.0.0.19] USE="dbus%* xulrunner%* -custom-optimization% -startup-notification%" LINGUAS="-bn% -bn_IN% -cy% -eo% -et% -gl% -hi% -hi_IN% -id% -is% -kn% -lv% -mr% -oc% -si% -sq% -sr% -te% -th%""
(In reply to comment #4) > > The postinst message of firefox-3 clearly warns about this issue. Post inst may not be the best place for this; likely to be "too late". In http://bugs.gentoo.org/show_bug.cgi?id=234646#c57 a patch has been proposed to fix this, by adding directly the xulrunner flag in make.defaults . As soon as all archs update their make.defaults, all stable people will get the workaround in a shot. I wonder if there is a better way to fix this for everybody altogether.
Firefox-3.5 will force everyone to xulrunner, it is in tree, will be avaliable as soon as a few issues are wrapped up.
