Bug#1005343: marked as done (nmu: asterisk-flite_3.0-4)

["Debian Bug Tracking System" <owner@bugs.debian.org>]

Your message dated Sat, 12 Feb 2022 14:51:34 +0100
with message-id <164467389424.2636895.15585753177184644318@auryn.jones.dk>
and subject line Re: Bug#1005343: nmu: asterisk-flite_3.0-4
has caused the Debian Bug report #1005343,
regarding nmu: asterisk-flite_3.0-4
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 owner@bugs.debian.org
immediately.)


-- 
1005343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005343
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

--- Begin Message ---

• To: Debian Bug Tracking System <submit@bugs.debian.org>
• Subject: nmu: asterisk-flite_3.0-4
• From: Jonas Smedegaard <dr@jones.dk>
• Date: Fri, 11 Feb 2022 18:44:28 +0100
• Message-id: <[🔎] 164460146835.3288358.8317615306435847277.reportbug@auryn.jones.dk>

Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

nmu asterisk-flite_3.0-4 . ANY . unstable . -m "rebuild against asterisk-1:18.10.0~dfsg+~cs6.10.40431411-1"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmIGoHwACgkQLHwxRsGg
ASFhMQ/9G8Ef5zhHcBYz898NFx3l9hw8g0cITEyoNZgo/f5Kqi5H1AEoEYV5i99Q
YZORP89rFcwhy8jVN4ggBB6IIVzmAiWf0mo0QTExd5vfAjPrk6/y1AXIf2IM7xSX
LU6rAhIGMh6ITVuBjlzmWwj3hKWa7vtuXupLdcf+jVUJ9SpJqpOnOuI46hG8+pHb
kQxXidURsrQbBHocTdTYAD279VI9XdTCg7dKQRS3iZa2rNoO/dJfXC3riCWvOyFv
NC1Gx8L1MHhBnn8cd9etmP4xKu202HhSRKpjUgRsZ3LOtDqHaYYtvd/qW0aPJTJv
M+LhQ0xTJzgXRgT15JUSHjczoqydd6v7u59IyTRx/kaRL385W6H1kMTezPIjU9fY
rwyiGu3LwHDlEfj0OV/kXHPQwRkw9Yp7ROkDWalyvdeomg6r3EmWd7eEw7C37K3Q
DOgYEJsHh9UULwTvA38MJM6j1Ddd+aNKJqAlxsv1dAHBxV3tZvmd1EVqBhAHlOpl
/HYBh6/B43ju6BKbF1i7jQiv5WTxhKMR1EKctrodzNHaYOaS6b7nYBhCEd5glizf
AiJPqWx888NEcumnKHNTBlwCzVqM/o8CAlffcSlc2vHVf8YIKY1KY2MUR+zBGzFX
rrUNoWguaQ0KshOw41nCwBaAllEXwWp1wZKpt98NyhWiQOtCu+8=
=9LuI
-----END PGP SIGNATURE-----

--- End Message ---

--- Begin Message ---

• To: 1005343-done@bugs.debian.org
• Cc: Sebastian Ramacher <sramacher@debian.org>
• Subject: Re: Bug#1005343: nmu: asterisk-flite_3.0-4
• From: Jonas Smedegaard <dr@jones.dk>
• Date: Sat, 12 Feb 2022 14:51:34 +0100
• Message-id: <164467389424.2636895.15585753177184644318@auryn.jones.dk>
• Reply-to: 1005343@bugs.debian.org
• In-reply-to: <[🔎] YgemQXlGUeFD2kaV@ramacher.at>
• References: <[🔎] 164460146835.3288358.8317615306435847277.reportbug@auryn.jones.dk> <[🔎] YgemQXlGUeFD2kaV@ramacher.at>

Quoting Sebastian Ramacher (2022-02-12 13:21:21)
> Control: tags -1 moreinfo
> 
> On 2022-02-11 18:44:28 +0100, Jonas Smedegaard wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian.org@packages.debian.org
> > Usertags: binnmu
> > 
> > nmu asterisk-flite_3.0-4 . ANY . unstable . -m "rebuild against asterisk-1:18.10.0~dfsg+~cs6.10.40431411-1"
> 
> Why is this rebuild needed?

Oh!  No rebuild is needed.

I was blindly assuming that asterisk releases 
1:16.23.0~dfsg+~cs6.10.40431411-1 and 1:18.10.0~dfsg+~cs6.10.40431411-1 
would have different ABI, but surprisingly that's not the case.

I will close this bugreport and check if there is perhaps a bug in how 
asterisk ABI is computed...

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: signature

--- End Message ---