Your message dated Sun, 4 Mar 2012 13:52:39 +0000
with message-id <20120304135239.ga8...@reptile.pseudorandom.co.uk>
and subject line Re: Bug#641836: Fails to hide internal symbols
has caused the Debian Bug report #641836,
regarding Fails to hide internal symbols
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
641836: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641836
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmpg123-0
Version: 1.12.1-3.2
Severity: serious
Hi,
I'm transforming the attached message from the public mplayer developer
mailing list to a proper debian bug report.
Daniel, it seems you haven't touch this package since two NMUs, maybe
you want to join pkg-multimedia and have the package team maintained there?
--- Begin Message ---
Erik Auerswald wrote:
> Hi,
>
> On Tue, Sep 13, 2011 at 03:58:56PM +0200, Diego Biurrun wrote:
>> On Tue, Sep 13, 2011 at 02:39:19PM +0200, Erik Auerswald wrote:
>>> On Tue, Sep 13, 2011 at 01:51:45PM +0200, Diego Biurrun wrote:
>>>> On Tue, Sep 13, 2011 at 09:09:49AM +0200, Erik Auerswald wrote:
>>>>> On Mon, Sep 12, 2011 at 06:12:41PM +0200, Reimar Döffinger wrote:
>>>>>> [...]
>>>>>> If we want to remove things: Does anyone remember a reason to keep
>>>>>> mp3lib? Because that one is high-cost in comparison.
>>>>> I currently need mp3lib because the default mpg123 crashes on every mp3
>>>>> file I have.
>>>> What do you mean by "default mpg123"?
>>> That MPlayer decides to use the mpg123 (based?) code by default.
>> I'm still not following. Is "default mpg123"
>>
>> a) what MPlayer carries along in the mp3lib/ directory or
>> b) the upstream libmpg123 from mpg123.de (which version)?
>
> I'll check when I'm back at my home system (not before Friday). I suppose
> configure output and existing system librarys should be enough to decide
> this. If system libs are used, they are from Debian/Sid, last updated
> Sunday.
libmpg123 package 1.12.1-3.2 on debian/sid is broken (it fails to hide internal
symbols, they overridden by symbols from MPlayer/mp3lib [with different ABI],
resulting in crash).
As package from squeeze (same upstream version) is *not* broken in same way, and
changes in packaging looks minor and unrelated, have no idea why it is broken.
Likely ./configure --disable-mp3lib also will fix this crash :-)
> Anyway, If I specify "-afm mp3lib" I can play mp3 files and videos with
> included mp3 audio. If I don't specify -afm ..., mplayer crashes when
> trying to play an mp3.
>
> What I am trying to say is that I need mp3lib support. I don't currently
> know if the version included in mplayer is used or some system lib. I
> assumed that the included code is used without even checking for a system
> wide replacement; I don't specify anything mp3 related when calling
> configure. But I don't know for sure and cannot check at the moment.
>
> Thanks,
> Erik
_______________________________________________
MPlayer-dev-eng mailing list
mplayer-dev-...@mplayerhq.hu
https://lists.mplayerhq.hu/mailman/listinfo/mplayer-dev-eng
--- End Message ---
--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4
--- End Message ---
--- Begin Message ---
On Sun, 04 Mar 2012 at 13:18:14 +0000, Simon McVittie wrote:
> The i386 NMU was the one built by the uploader, so there are no build logs.
> I suspect the uploader just had a broken toolchain or something? I've asked
> adsb to rebuild it on the i386 buildd and we'll see whether that fixes it.
Fixed in 1.12.1-3.2+b1. According to the build log, only symbols that look
as though they ought to be public are exported from the binNMU
(<https://buildd.debian.org/status/fetch.php?pkg=mpg123&arch=i386&ver=1.12.1-3.2%2Bb1&stamp=1330868268>,
search for dpkg-gensymbols) so I think it's all OK now.
Regards,
S
--- End Message ---
