Your message dated Thu, 22 May 2025 08:45:58 +0200
with message-id <ac7ijqm4z_9wq...@ramacher.at>
and subject line Re: Bug#1106240: nmu: libm4rie_20250103-1
has caused the Debian Bug report #1106240,
regarding nmu: libm4rie_20250103-1
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.)
--
1106240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106240
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: libm4...@packages.debian.org
Control: affects -1 + src:libm4rie
User: release.debian....@packages.debian.org
Usertags: binnmu
nmu libm4rie_20250103-1 . ANY . unstable . -m "rebuild against fixed libm4ri
(#1099530)"
libm4rie was build with the compiler flags from libm4ri resulting in a
baseline violation. Rebuilding against the fixed libm4ri solves this and
makes the package reproducible.
--- End Message ---
--- Begin Message ---
On 2025-05-21 22:57:00 +0200, Jochen Sprickerhof wrote:
> Package: release.debian.org
> Severity: normal
> X-Debbugs-Cc: libm4...@packages.debian.org
> Control: affects -1 + src:libm4rie
> User: release.debian....@packages.debian.org
> Usertags: binnmu
>
> nmu libm4rie_20250103-1 . ANY . unstable . -m "rebuild against fixed libm4ri
> (#1099530)"
Scheduled
Cheers
--
Sebastian Ramacher
--- End Message ---
