Am Thu, 4 Apr 2024 09:36:37 +0200
schrieb Sebastian Ramacher :
> Now I get the following on arm{hf,el}:
>
> --- debian/libmpg123-0.symbols (libmpg123-0_1.32.6~dev+20240403022201-1_armhf)
> +++ dpkg-gensymbolspYII3c 2024-04-03 09:52:12.863133592 +
> @@ -8,8 +8,8 @@
> mpg123_current_deco
Hi Thomas
On 2024-04-03 08:09:59 +0200, Thomas Orgis wrote:
> Hi again,
>
> (after Easter hiatus … or rather xz backdoor meltdown?)
>
> I had a stab at this, detecting a system that forces 64 bit offsets on
> a 32 bit base in configure. This is to ensure that you do not encounter
> the same symb
Hi again,
(after Easter hiatus … or rather xz backdoor meltdown?)
I had a stab at this, detecting a system that forces 64 bit offsets on
a 32 bit base in configure. This is to ensure that you do not encounter
the same symbol (like mpg123_tell() on two builds of the library on the
same platform of
Hi Sebastian,
thanks for not escalating on the anger that has shown through the end
of my last reply. It really seems to be an endless stream of pain that
results from once having put off_t into public API. This is the message
I have to any developer: Do not put types into your API that could
depe
Hi Thomas
On 2024-03-23 15:24:58 +0100, Thomas Orgis wrote:
> Hi Sebastian,
>
>
> Am Sat, 23 Mar 2024 10:40:43 +0100
> schrieb Sebastian Ramacher :
>
> > +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_decode_frame_32@Base
> > 1.13.7
> > +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)
Hi Sebastian,
Am Sat, 23 Mar 2024 10:40:43 +0100
schrieb Sebastian Ramacher :
> +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_decode_frame_32@Base
> 1.13.7
> +#MISSING: 1.32.5-1+b1# (arch-bits=32|arch=!x32)mpg123_feedseek_32@Base 1.13.7
> +#MISSING: 1.32.5-1+b1#
> (arch-bits=32|arch=
Hi Thomas
On 2024-02-05 15:05:25 +0100, Thomas Orgis wrote:
> Am Mon, 05 Feb 2024 08:36:28 +
> schrieb Steve Langasek :
>
> > we have identified
> > mpg123 as a source package shipping runtime libraries whose ABI
> > either is affected by the change in size of time_t, or could not be
> > ana
Am Mon, 05 Feb 2024 08:36:28 +
schrieb Steve Langasek :
> we have identified
> mpg123 as a source package shipping runtime libraries whose ABI
> either is affected by the change in size of time_t, or could not be
> analyzed via abi-compliance-checker (and therefore to be on the safe
> side we
Source: mpg123
Version: 1.32.4-1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t
NOTICE: these changes must not be uploaded to unstable yet!
Dear maintainer,
As part of the 64-bit time_t transition req
9 matches
Mail list logo