There is a blocker uploading to unstable. * uim-mozc: candidate words are shown with flickering
It might be caused by broken update patch set for uim, but not confident yet because of lacking knowledge about uim-mozc enough. Above issue was verified with: ibus-mozc 2.29.5160.102+dfsg-1~exp1 mozc-data 2.29.5160.102+dfsg-1~exp1 mozc-server 2.29.5160.102+dfsg-1~exp1 mozc-utils-gui 2.29.5160.102+dfsg-1~exp1 uim-mozc:amd64 2.29.5160.102+dfsg-1~exp1 libuim-custom2:amd64 1:1.8.8-9.5+b2 libuim-data 1:1.8.8-9.5 libuim-scm0:amd64 1:1.8.8-9.5+b2 libuim8:amd64 1:1.8.8-9.5+b2 uim 1:1.8.8-9.5+b2 uim-data 1:1.8.8-9.5 uim-fep 1:1.8.8-9.5+b2 uim-gtk2.0 1:1.8.8-9.5+b2 uim-gtk2.0-immodule:amd64 1:1.8.8-9.5+b2 uim-gtk3 1:1.8.8-9.5+b2 uim-gtk3-immodule:amd64 1:1.8.8-9.5+b2 uim-mozc:amd64 2.29.5160.102+dfsg-1~exp1 uim-plugins:amd64 1:1.8.8-9.5+b2 uim-qt5 1:1.8.8-9.5+b2 uim-qt5-immodule:amd64 1:1.8.8-9.5+b2 uim-xim 1:1.8.8-9.5+b2 By the way, do we still need uim-mozc? and should it be? Surely current task-japanese-desktop prefers uim-mozc instead of uim-anthy. I'm not sure that uim-mozc maintenance is sustainable enough. Who can actively maintain it? Regards, On Sun, 24 Nov 2024 23:13:23 +0900 Kentaro HAYASHI <ken...@xdump.org> wrote: > FYI: > > It is hard directly upgrade to Mozc 2.30, so I've > tried minor version of Mozc upgrade (from 2.28.4715.102 to > 2.29.5160.102) for experimental. > > Accepted mozc 2.29.5160.102+dfsg-1~exp1 > https://lists.debian.org/debian-experimental-changes/2024/11/msg00339.html
