Bug#1016771: marked as done (nmu: liboqs_0.7.2~rc1-1)
Your message dated Sun, 7 Aug 2022 20:36:19 +0200
with message-id <YvAGI/BvaaB8dJZK@ramacher.at>
and subject line Re: Bug#1016771: nmu: liboqs_0.7.2~rc1-1
has caused the Debian Bug report #1016771,
regarding nmu: liboqs_0.7.2~rc1-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 owner@bugs.debian.org
immediately.)
--
1016771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016771
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu
Hello,
I want to request binNMU on amd64 for recently accepted new package.
nmu liboqs_0.7.2~rc1-1 . amd64 . unstable . -m "Rebuild on buildd"
Thanks,
Andrius
--- End Message ---
--- Begin Message ---
On 2022-08-07 08:08:00 +0300, Andrius Merkys wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: binnmu
>
> Hello,
>
> I want to request binNMU on amd64 for recently accepted new package.
>
> nmu liboqs_0.7.2~rc1-1 . amd64 . unstable . -m "Rebuild on buildd"
liboqs regressed on mips64el and now FTBFS there. An upload will be
required to fix that and hence this rebuild won't be needed.
Cheers
--
Sebastian Ramacher
--- End Message ---
Reply to: