[gstreamer-bugs] [Bug 340762] can no longer play m4a files in rhythmbox after gst-plugins-bad upgrade

[GStreamer (bugzilla.gnome.org)]

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=340762
 GStreamer | gst-plugins-bad | Ver: 0.10.3





------- Comment #2 from Eric Bair  2006-05-05 20:32 UTC -------
Actually, I think I may have figured out the problem already.  As noted above,
when I encountered the error, I was using faad2 version faad2-2.0-8.fc5.rf. 
When I "upgraded" to faad2 version faad2-2.0-8.lvn5, the problem I described
above disappeared.

Hence, I'm not sure that this is a bug in gst-plugins-bad or even gstreamer per
se.  This seems to be a problem with faad2, and it's a problem that I've
encountered before.  More specifically, it appears that version 2.0-8 of the
faad2 packages distributed by freshrpms/dries are incompatible with the faad2
package distributed by livna.  Any package that is built using the
freshrpms/dries version of faad2 won't play m4a files on a system where the
livna version of faad2 is installed, and similarly, a package build against the
livna version of faad2 won't play m4a files on a system where the
freshrpms/dries version of faad2 is installed.

I'm almost certain that's the reason that my gstreamer-plugins-bad plugin
stopped working when I upgraded this morning.  Previously I was using the
gstreamer-plugins-bad package distributed by freshrpms, which was presumably
built against the freshprms version of faad2.  When I upgraded to the
gstreamer-plugins-bad package distributed by gstreamer, I assume it was built
against the livna version of faad2, and hence the problem.

I'm not sure what is the best way to deal with the issue.  I plan on filing bug
reports at both livna and freshrpms to let them know that even though their
respective faad2 packages have the same version number, they are incompatible
with one another.  Ideally they would make their packages compatible, but that
might be too much to hope for.  At the bare minimum, it seems like they should
give the two packages different version numbers and make sure that any package
depending of faad2 insists on having the correct version installed.

Also, I should mention that this only seems to be a problem on x86_64 machines.
 On my i386 machine, the livna version of faad2 is installed, but I can play
m4a files using packages distributed by freshrpms/dries without any problems
(at least that I have observed thus far).


-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.