Bug#1085173: mozc: New upstream release available: 2.30.5544.102

[Kentaro HAYASHI]

Source: mozc
Version: 2.28.4715.102+dfsg-2.3
Severity: normal
X-Debbugs-Cc: ***@xdump.org

Dear Maintainer,

The upstream repository has released 2.30.5544.102.

It would be nice to upgrade the Debian package to that release.

But currently, there are technical difficulty exists to following
upstream releases in some cases.

* GYP was deprecated
* Instead, newer Bazel is required to build it, but not exist on
Debian yet.
* Only old Bazel is available on Debian
* bazel-bootstrap stick to 4.x, need to update Bazel 7.x (maybe)
* Newer version of Abseil is required
* Mozc 2.30.5544.102 requires Abseil 20240116.1 or newer one.

As a practical approach, it is reasonable to update existing GYP patch
to refactor for newer mozc version which targets at max 2.29.5544.102.

Here is the brief review of current patches.

* 0001-Update-uim-mozc-to-c979f127acaeb7b35d3344e8b1e40848e.patch
* Required
* 0002-Support-fcitx.patch
* Required
* 0003-Change-compiler-from-clang-to-gcc.patch
* (maybe) Not needed anymore
* Related commits:
https://github.com/google/mozc/commit/ae169acdcc9f7c205a30d432486dcbf13dc3e316
https://github.com/google/mozc/commit/aba090da42a8366e72bc320dfafc3f9f93755edf
* 0004-Add-usage_dict.txt.patch
* Required. (maybe)
* 0005-Enable-verbose-build.patch
* Required.
* 0006-Update-gyp-using-absl.patch
* Required and need **massive** refactoring.
* 0007-common.gypi-Use-command-v-instead-of-which.patch
* (maybe) Not needed anymore
* 0009-protobuf.gyp-Add-latomic-to-link_settings.patch
* Required.
* 0010-Fix-the-compile-error-of-ParseCommandLineFlags-with.patch
* Required. Should be merged into 0006 patch.
* 0011-Fix-missing-abseil-gyp-link-settings.patch
* Required. Should be merged into 0006 patch.

FYI: Mozc's tags:

* 2.30.5544.102 Require abseil 20240116.1 or later
* 2.29.5544.102 GYP was deprecated
* 2.29.5374.102
* 2.29.5268.102 No gtk renderer anymore, need Qt.
* 2.29.5160.102 The last version that gtk renderer is available.
* 2.28.5029.102
* 2.28.4880.102
* 2.28.4715.102+dfsg Debian sid

Regards,

[Kentaro HAYASHI]

Post by Kentaro HAYASHI
* 2.30.5544.102 Require abseil 20240116.1 or later
* 2.29.5544.102 GYP was deprecated
* 2.29.5374.102
* 2.29.5268.102 No gtk renderer anymore, need Qt.
* 2.29.5160.102 The last version that gtk renderer is available.

Since 2.29.5160.102, --use_gyp_for_ibus_build option was removed.

Post by Kentaro HAYASHI
* 2.28.5029.102
* 2.28.4880.102

[Kentaro HAYASHI]

FYI:

Fedora ships 2.29.5111.102 (enable GTK renderer)
openSUSE ships 2.29.5268.102 (migrated build system to Bazel)

On Thu, 17 Oct 2024 22:29:49 +0900 Kentaro HAYASHI

Post by Kentaro HAYASHI

Post by Kentaro HAYASHI
* 2.30.5544.102 Require abseil 20240116.1 or later
* 2.29.5544.102 GYP was deprecated
* 2.29.5374.102
* 2.29.5268.102 No gtk renderer anymore, need Qt.
* 2.29.5160.102 The last version that gtk renderer is available.

Since 2.29.5160.102, --use_gyp_for_ibus_build option was removed.

As a practical approach, it might better to target 2.29.5160.102
for a while.
Then try to upgrade it to more newer version gradually.

I've tried to refresh patch set for 2.29.5160.102 and attached it.

* support-uim.patch
* support-fcitx.patch
* change-compiler-from-clang-to-gcc.patch
* add-japanese-usage-dictionary.patch
* enable-verbose-build.patch
* update-gyp-using-system-abseil.patch
* gyp-using-command-instead-of-which.patch
* gyp-protobuf-link-with-atomic.patch
* enable-deprecated-gtk-renderer.patch
* fix-compile-error-of-ParseCommandLineFlags.patch
* enable-use_gyp_for_ibus_build-again.patch
* ibus-drop-needless-client_mock.patch
* protobuf-revert-internal-cleanup.patch
* uim-mozc-fix-ftbfs.patch

Regards,

[Kentaro HAYASHI]

FYI:

I'm testing built packages by myself mainly fcitx5-mozc.

https://github.com/kenhys/mozc/releases/tag/debian-2.29.5160.102

[Kentaro HAYASHI]

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

[Kentaro HAYASHI]

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,

Post by Kentaro HAYASHI
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

[Kentaro HAYASHI]

Post by Kentaro HAYASHI
There is a blocker uploading to unstable.
* uim-mozc: candidate words are shown with flickering

NOTE:

This behavior is observed with uim-mozc on GNOME.
(explicitly switched to uim-mozc with im-config configuration)

[Kentaro HAYASHI]

Post by Kentaro HAYASHI

Post by Kentaro HAYASHI
There is a blocker uploading to unstable.
* uim-mozc: candidate words are shown with flickering

This behavior is observed with uim-mozc on GNOME.
(explicitly switched to uim-mozc with im-config configuration)

FYI:

I've reported above issue as if it occurs with
2.29.5160.102+dfsg-1~exp1, but it was *also* reproducible
with 2.28.4715.102+dfsg-2.3.

So it was not regression with 2.29.5160.102+dfsg-1~exp1.

ibus-mozc 2.28.4715.102+dfsg-2.3+b1
mozc-data 2.28.4715.102+dfsg-2.3
mozc-server 2.28.4715.102+dfsg-2.3+b1
mozc-utils-gui 2.28.4715.102+dfsg-2.3+b1
uim-mozc:amd64 2.28.4715.102+dfsg-2.3+b1

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.28.4715.102+dfsg-2.3+b1
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

Regards,

[Kentaro HAYASHI]

Post by Kentaro HAYASHI

Post by Kentaro HAYASHI

Post by Kentaro HAYASHI
There is a blocker uploading to unstable.
* uim-mozc: candidate words are shown with flickering

This behavior is observed with uim-mozc on GNOME.
(explicitly switched to uim-mozc with im-config configuration)

I've reported above issue as if it occurs with
2.29.5160.102+dfsg-1~exp1, but it was *also* reproducible
with 2.28.4715.102+dfsg-2.3.
So it was not regression with 2.29.5160.102+dfsg-1~exp1.

To be more presicely, the issue will happen when uim-mozc is
used with wayland. (Under XOrg, it will not happen)

Thus GNOME and derivatives might not be affected.
(ibus-mozc will be used)

Regards,

[Kentaro HAYASHI]

Post by Kentaro HAYASHI
* 2.30.5544.102 Require abseil 20240116.1 or later
* 2.29.5544.102 GYP was deprecated
* 2.29.5374.102
* 2.29.5268.102 No gtk renderer anymore, need Qt.

It seems that newer protobuf upgrading mozc package from
2.29.5160.102+dfsg-1~exp1 to 2.29.5268.102.

There is libprotobuf-dev 3.25.4-1+b2 on experimental.
2.29.5268.102 requires it to build the following modules:

* unix/ibus/ibus.gyp:ibus_mozc
* unix/emacs/emacs.gyp:mozc_emacs_helper
* server/server.gyp:mozc_server

But, it seems that it requires auto-protobuf transition to
be passed.

https://release.debian.org/transitions/html/auto-protobuf.html

Regards,

[Kentaro HAYASHI]

Hi,

IMHO mozc_2.29.5160.102+dfsg-1~exp1 is now ready to ship it, so
to make things forward, I've uploaded mozc_2.29.5160.102+dfsg-1
into DELAYED Queue with max delay (15-day).

Regards,

[Kentaro HAYASHI]

FYI:

As I noted previously, mozc_2.29.5160.102+dfsg-1
was landed on unstable now.

https://tracker.debian.org/news/1596502/accepted-mozc-2295160102dfsg-1-source-into-unstable/

On Thu, 5 Dec 2024 22:42:01 +0900 Kentaro HAYASHI

Post by Kentaro HAYASHI
Hi,
IMHO mozc_2.29.5160.102+dfsg-1~exp1 is now ready to ship it, so
to make things forward, I've uploaded mozc_2.29.5160.102+dfsg-1
into DELAYED Queue with max delay (15-day).
Regards,