media-sound/banshee-1.4.3 depends >=media-libs/gst-plugins-bad-0.10.9 which is masked and conflicts with media-plugins/gst-plugins-faad-0.10.9. According to /usr/portage/media-sound/banshee-1.4.3.ebuild, banshee depends on gst-plugins-faad when 'aac' USE flag is specified: aac? ( >=media-plugins/gst-plugins-faad-${GVER} ) while always depending on gst-plugins-bad: >=media-libs/gst-plugins-bad-${GVER} which is contradictory. Therefore, an updated ebuild file needs to be published, which resolves the conflicting dependencies by removing either gst-plugins-bad or gst-plugins-faad dependency. Reproducible: Always Steps to Reproduce: 1. Add the following lines to /etc/portage/package.keywords: media-sound/banshee ~x86 =dev-dotnet/gtk-sharp-2.12* ~x86 =dev-dotnet/gnome-sharp-2.24* ~x86 =dev-dotnet/mono-addins-0.4* ~x86 =dev-lang/mono-2.2* ~x86 =dev-dotnet/taglib-sharp-2.0* ~x86 =dev-dotnet/gconf-sharp-2.24* ~x86 =dev-dotnet/notify-sharp-0.4* ~x86 =x11-misc/notification-daemon-0.4* ~x86 =x11-libs/libnotify-0.4* ~x86 =dev-dotnet/glade-sharp-2.12* ~x86 =dev-dotnet/art-sharp-2.24* ~x86 =dev-dotnet/gtk-sharp-gapi-2.12* ~x86 =dev-dotnet/glib-sharp-2.12* ~x86 =dev-dotnet/atk-sharp-2.12* ~x86 =dev-dotnet/pango-sharp-2.12* ~x86 =dev-dotnet/gdk-sharp-2.12* ~x86 =dev-dotnet/libgdiplus-2.2* ~x86 =dev-dotnet/gnomevfs-sharp-2.24* ~x86 =media-plugins/gst-plugins-taglib-0.10* ~x86 =media-libs/gst-plugins-good-0.10* ~x86 =media-plugins/gst-plugins-mad-0.10* ~x86 =media-libs/gst-plugins-base-0.10* ~x86 =media-libs/gstreamer-0.10* ~x86 =media-plugins/gst-plugins-gconf-0.10* ~x86 =media-plugins/gst-plugins-faad-0.10* ~x86 =media-libs/gst-plugins-ugly-0.10* ~x86 2. Unmask media-libs/gst-plugins-bad 3. emerge =media-sound/banshee-1.4.3 Actual Results: Successful build Expected Results: Dependency conflicts
I can confirm that removing the dependency '>=media-libs/gst-plugins-bad-${GVER}' from banshee-1.4.3.ebuild fixes the problem. Banshee seems to run fine, too.
Please read the package.mask entry for the gst-plugins-bad you've unmasked: # Samuli Suominen <ssuominen@gentoo.org> (24 Dec 2008) # - drop .la files (and static libs) # - monolithic version, EAPI=2, commented versions for new devs # Talk with the actual gstreamer team before unmasking these - # we are completely against the notion of monolithic versions, these # here should be considered an experimentation =media-libs/gstreamer-0.10.21-r10 =media-libs/gst-plugins-good-0.10.11-r1 =media-libs/gst-plugins-bad-0.10.9-r1 =media-libs/gst-plugins-ugly-0.10.10-r1 =media-libs/gst-plugins-base-0.10.21-r1
My point is that banshee-1.4.3 depends on masked components. The ebuild of banshee needs to be updated to depend on individual gstreamer plugins instead of depending on masked components.
If doing so is impossible, then I'm fine with marking this issue as invalid. I actually switched back to rhythmbox which works much better for me. :)
(In reply to comment #3) > My point is that banshee-1.4.3 depends on masked components. What I'm telling you is that no, that is not the case. > The ebuild of > banshee needs to be updated to depend on individual gstreamer plugins instead > of depending on masked components. It has always depended on individual gstreamer plugins. The gst-plugins-bad package provides some audio and video codecs. The gst-plugins-faad package provides and interface to faad2. You have unmasked gst-plugins-bad-0.10.9-r1 which is an experiment to see how having all the modularized gst-plugins packages in their tarball-packages would look like. It has a big warning. If you don't want conflicting dependencies, don't unmask it.
Thanks for your kind explanation and your time.
