Your message dated Thu, 25 May 2023 18:16:26 +0200
with message-id
<cam8zjqvcwcfs-vun87riz9d70x5zb0-dlqemgzrje1gb7a1...@mail.gmail.com>
and subject line Re: Bug#1036164: nmu: fcitx5-zhuyin_5.0.11-1
has caused the Debian Bug report #1036164,
regarding nmu: fcitx5-zhuyin_5.0.11-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 [email protected]
immediately.)
--
1036164: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036164
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: binnmu
X-Debbugs-Cc: [email protected], [email protected]
Control: affects -1 + src:fcitx5-zhuyin
nmu fcitx5-zhuyin_5.0.11-1 . ANY . unstable . -m "Rebuild with libpinyin/2.8.1
(Closes: #1036163)"
There must be better way to track this binary file format, but I'm not sure
how to implement it.
binNMU might be the easiest way currently.
--- End Message ---
--- Begin Message ---
On Tue, 16 May 2023 at 12:03, Shengjing Zhu <[email protected]> wrote:
> nmu fcitx5-zhuyin_5.0.11-1 . ANY . unstable . -m "Rebuild with
> libpinyin/2.8.1 (Closes: #1036163)"
>
> There must be better way to track this binary file format, but I'm not sure
> how to implement it.
> binNMU might be the easiest way currently.
Scheduled, thanks.
--- End Message ---
