Since the introduction of gstreamer-1.0 into Factory we now have a mix of programs and libraries linking against one or the other. The trouble is that the gstreamer-* libraries do not use symbol versioning and in some cases progams end up linking to both versions, mostly through indirect shared library dependencies or object which are dlopen'd at runtime. E.g. currently all GTK2/3 applications indirectly link to gstreamer-1.0 through the libcanberra-gtk-module and some directly link against gstreamer-0.10 at the same time, see https://bugzilla.novell.com/show_bug.cgi?id=800963. While this particular case may be solved by removing libcanberra-gtk-module as Dominique offered, there are probably more of such cases and there is the problem that people developing on openSUSE will run into trouble when linking against certain combinations of libraries which have different gstreamer versions in their dependency tree. Identifying such cases is also not straightforward, the dependency information from repository metadata is not helpful since it only covers the package level, directly resolving library dependency trees via recursive ldd turns out to be extremely slow and also does not cover dlopen'd plugins etc. Any ideas how to systematically determine which packages are actually affected by this and how to address this probem before the 12.3 release? -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org