Your message dated Sun, 22 Nov 2020 18:46:28 +0200
with message-id
<CAM8zJQuAHr6ZxRf==z5jrtfut_gae0fets6uxpxaj27opzm...@mail.gmail.com>
and subject line Re: Bug#975448: nmu: antimony_0.9.3-2
has caused the Debian Bug report #975448,
regarding nmu: antimony_0.9.3-2
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 [email protected]
immediately.)
--
975448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975448
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: binnmu
The antimony binnmus for the python 3.9 transition failed due to bug
975109 . The maintainer made an upload fixing the bug but unfortunately it was
not source-only and the included amd64 binary was not built against python 3.9
(the other architectures were built on buildds against python 3.9). There are
no Architecture: all or Multi-Arch: same binaries so a binnmu should be
sufficent to get this into a migratable state.
nmu antimony_0.9.3-2 . amd64 . unstable . -m "Python 3.9 as default"
--- End Message ---
--- Begin Message ---
On Sun, 22 Nov 2020 at 14:54, plugwash <[email protected]> wrote:
> nmu antimony_0.9.3-2 . amd64 . unstable . -m "Python 3.9 as default"
Scheduled, thanks!
--- End Message ---
