Bug#512844: ffmpeg-debian breaks binary compatibility

[Reinhard Tartler]

clone 512844 -1
retitle 512844 ffmpeg libraries need more strict internal dependencies
retitle -1 mplayer must not use ffmpeg internal functions like ff_gcd
stop

Paul Gevers <paul at climbing.nl> writes:

> Severity: normal
> Thanks
>
> The problem is that you are using mplayer from unstable, with ffmpeg
> from experimental.

close. mplayer in unstable uses ff_gcd, which is a strictly internal
function of libavutil. It has been renamed to av_gcd on Jan, 17, 2009.
Applications like mplayer are not supposed to use such functions. I just
checked mplayer's trunk, at found this commit:

------------------------------------------------------------------------
r28338 | cehoyos | 2009-01-17 12:29:36 +0100 (Sa, 17. Jan 2009) | 1 line

Fix compilation: s/ff_gcd/av_gcd.

> The experimental version of ffmpeg-debian creates libavcodec52, where
> your mplayer should depend on if you want to use it.  But the ffmpeg
> in unstable builds/needs libavcodec51, so that is why mplayer depends
> on it. You can at this moment not mix ffmpeg from experimental with
> mplayer from unstable.
>
> Maybe ffmpeg should conflict with old versions of the libraries, ie
> Conflicts libavcodec51, libavcodec-unstripped-51 etc...

yes, we need more strict internal dependencies in ffmpeg, which we
happen to fact to discuss right now. However mplayer mustn't use
internal functions. for av_gcd, this function has just been introduced
in the new ffmpeg version, so updating mplayer to a version later than
28338 will fix this issue.

(or alternatively backport that svn revision to current mplayer)

-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4