can not download with _japanese_usage_dictionary_rev=0, the latest version is 10
maybe we can update mozc to 2.16.2003.102?
Search Criteria
Package Details: fcitx-mozc-ut 2.28.4990.102-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/fcitx-mozc-ut.git (read-only, click to copy) |
---|---|
Package Base: | fcitx-mozc-ut |
Description: | Mozc module for Fcitx |
Upstream URL: | https://github.com/fcitx/mozc |
Licenses: | GPL, custom, LGPL, MIT, Apache |
Conflicts: | fcitx-mozc |
Provides: | fcitx-mozc |
Submitter: | naoina |
Maintainer: | Nocifer |
Last Packager: | Nocifer |
Votes: | 5 |
Popularity: | 0.000000 |
First Submitted: | 2014-01-21 09:00 (UTC) |
Last Updated: | 2023-01-21 18:34 (UTC) |
Dependencies (7)
- fcitx
- mozcAUR (mozc-utAUR)
- bazel (bazel-gitAUR, bazel024-binAUR, bazel3-binAUR, bazelisk-gitAUR, bazeliskAUR, bazelisk-binAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- python (python37AUR, python311AUR, python310AUR) (make)
- qt5-base (qt5-base-gitAUR, qt5-base-headlessAUR) (make)
- fcitx-configtool (optional)
Required by (1)
- fcitx-input-support (requires fcitx-mozc) (optional)
Sources (2)
Latest Comments
« First ‹ Previous 1 2 3
amazingfate commented on 2015-01-10 17:19 (UTC)
<deleted-account> commented on 2014-11-18 08:10 (UTC)
Mozc UT Dictionary updated 20141110
naoina commented on 2014-02-27 03:22 (UTC)
@tuxsavvy
Thank you for your report. I fixed it.
tuxsavvy commented on 2014-02-27 03:06 (UTC)
http://download.fcitx-im.org/fcitx-mozc/fcitx-mozc-icon.tar.gz link is invalid. The new location for the file is https://fcitx.googlecode.com/files/fcitx-mozc-icon.tar.gz. The checksum also matches.
http://download.fcitx-im.org/fcitx-mozc/fcitx-mozc-icon.tar.gzのリンクは無効です。。あの新しいファイル場所はhttps://fcitx.googlecode.com/files/fcitx-mozc-icon.tar.gzです。同じファイルのチェックサムにかないます。
Pinned Comments
Nocifer commented on 2022-05-29 21:56 (UTC)
Due to the recent GCC 12.1 update, if you try to update a Mozc package that was built with an older GCC version you will need to yet again delete your Bazel cache (
~/.cache/bazel/...
by default) in order to prevent the following error (or some such):It's more than likely that this error can also be prevented by removing one or more specific files within Bazel's cache instead of the whole lot of it, so in the future such toolchain updates may become much less painful; but for the time being, and unless otherwise noted, be aware that an updated toolchain will always mean that you need to delete Bazel's cache and suffer a full recompilation.