On Wed, 1 Jan 2025 19:55:02 +0900 Kentaro HAYASHI <[email protected]> wrote: > > As 2.29.5160.102 was landed on Debian sid, so next target is > 2.29.5268.102. >
Hello, As you know, recently newer Bazel related packages were landed into debian/unstable, so now I'm planning to update Mozc from 2.29.5160.102 to 3.33.6133. * Why was Mozc 3.33.6133 chosen? Now latest version of Mozc is 3.34.x, but it requires Bazel 9.x. Please recall that Bazel 7.7.1 was introduced Debian/unstable. And more, newer dependency libraries are required. You might feel that target version is too high from 2.29.5160.102, but if we upgrade to more older Mozc, it means that it requires to backport Mozc to older libabsl compatible codes. * What will be brought to you? I want to keep uim mozc and fcitx5-mozc, but drop fcitx-mozc. (uim mozc might be also dropped) Upstream changed to use Qt renderer, so GTK3 dependency will be also removed. * When is the new version of Mozc for Debian available? Not sure. There are many technical tasks to solve. * Revisit patch sets to apply * Porting uim mozc patch and fix FTBFS * Porting fcitx5 mozc patch and fix FTBFS * Fix src/third_party vendoring * Switch from GYP to Bazel build systems * ... At least, it will likely require several rounds of testing in the Debian experimental. I'm currently trying to switch to a new build system. Best Regards,
