Your message dated Thu, 2 May 2024 14:18:14 +0200
with message-id <df9dd54d-2d4c-4055-94f8-0076ed577...@gmail.com>
and subject line Re: Bug#1070230: nmu: osmo-msc_1.9.0+dfsg1-2 
osmo-sgsn_1.9.0+dfsg1-3
has caused the Debian Bug report #1070230,
regarding nmu: osmo-msc_1.9.0+dfsg1-2 osmo-sgsn_1.9.0+dfsg1-3
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.)


-- 
1070230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: binnmu

nmu osmo-msc_1.9.0+dfsg1-2 . ANY . unstable . -m "Rebuild against libosmo-sccp 
with t64 renaming reverted."
nmu osmo-sgsn_1.9.0+dfsg1-3 . ANY . unstable . -m "Rebuild against libosmo-sccp 
with t64 renaming reverted."

libosmo-sccp has been restricted to 64-bit architectures and therefore
the t64 renaming has been reverted. The reverse dependencies (which have
been removed from the 32-bit architectures) now need another binNMU.


Andreas

--- End Message ---
--- Begin Message ---
On 02/05/2024 12:35, Andreas Beckmann wrote:
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: binnmu

nmu osmo-msc_1.9.0+dfsg1-2 . ANY . unstable . -m "Rebuild against libosmo-sccp with 
t64 renaming reverted."
nmu osmo-sgsn_1.9.0+dfsg1-3 . ANY . unstable . -m "Rebuild against libosmo-sccp with 
t64 renaming reverted."

libosmo-sccp has been restricted to 64-bit architectures and therefore
the t64 renaming has been reverted. The reverse dependencies (which have
been removed from the 32-bit architectures) now need another binNMU.

Scheduled. Though note there's a patch in #1065790 which seems sensible.

Cheers,
Emilio

--- End Message ---

Reply via email to