On Tue, Aug 03, 2010 at 11:30:48 (EDT), Norbert Preining wrote:

> Hi,
> I see the comment:
>>> ii  libavcodec52       5:0.6~svn20100603-0.0 library to encode decode 
>>> multimedi
>>> ii  libavformat52      5:0.6~svn20100603-0.0 ffmpeg file format library
>>> ii  libpostproc51      5:0.6~svn20100603-0.0 postproc shared libraries
>>> ii  libswscale0        5:0.6~svn20100603-0.0 ffmpeg video scaling library
>>^^ Not Debian packages, knowing to cause breakage.
> And in bug report #591349 I see:
>> You are mixing debian-multimedia.org libraries with debian's system
>> libraries, and this is guaranteed to cause problems. More specifically,
>> mplayer rc3 is not compatible with ffmpeg 0.6,
> Yes, sooo *what* breakage please?

The breakage that mplayer uses internal symbols of ffmpeg that mplayer
is not supposed to do. This of course causes problems when the system
ffmpeg version doesn't match the copy of mplayer.

> What I see is:
> - marillat provides working packages since ages
> - your packages do not cooperate with the libs he is shipping

yes, that's technically infeasible.

> Why did you (maintainer) choose that specific version number:
>       2:1.0~rc3++final.dfsg1-1
> with ++? Only to make sure that the packages at marillat are overridden
> by packages that suddenly break video playback in many applications?

no, that was to fix a versioning mistake I did in the past.

> Yes, of course, the answer is: "I don't care for package outside Debian"
> as we have seen above, but that is *not* the best way to go.

feel free to propose patches.

I would propose to change marillat's packages to not replace the system
libraries. But last time I've asked him that, he rejected that. Another
option would be to make his packaging providing static libraries only.

> Why not choose a version number which is below the one of marillat? It
> would still be the default package to be installed in Debian unless
> people know what they are doing and adding marillat source. 

marillat does no longer provide mplayer. he is now focusing on
mplayer-git, a fork of mplayer.

> Or is it about ego, my packages has to be the one that breaks all the
> system out there???

I don't think so.

> Furthermore, you (Reinhard Tartler) said that mplayer is not compatbile
> with ffmep 0.6, so why does the one from mdebian-multimedia run?

His old package didn't and his new mplayer-git don't have this
particular problem because he has always compiled against ffmpeg
libraries statically. This is not acceptable for Debian for obvious

> You say that "mixing debian-multimedia libs with debians *guarantees*
> to cause problems", well, up to today I never had these kinds of problems
> in the last years, so it might be your personal observation, but mine 
> kind of disagrees with that. Can you please provide reasonable data point
> beyond shipping a breaking package that supports your ideas?

I'd suggest that you compare the exported symbols between 'his' and the
packages that he is replacing for a start.

> THere is no statistical data, but I would expect that most people in
> one or the other way use packages from marillat.

this is sad, yes.

> Anyway, I have "downgraded" to working packages and hope yours will 
> take a reasonable version number. But actually I don't care for them.

that's okay for me.

take care!

Reinhard Tartler, KeyID 945348A4

pkg-multimedia-maintainers mailing list

Reply via email to