Search Criteria
Package Details: mozc-ut-full-common 2.30.5618.102.20241212-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/mozc-ut-full.git (read-only, click to copy) |
---|---|
Package Base: | mozc-ut-full |
Description: | A Japanese Input Method for Chromium OS, Windows, Mac and Linux (the Open Source Edition of Google Japanese Input) |
Upstream URL: | https://github.com/fcitx/mozc |
Licenses: | custom |
Submitter: | brli |
Maintainer: | brli |
Last Packager: | brli |
Votes: | 6 |
Popularity: | 0.021865 |
First Submitted: | 2022-07-04 17:27 (UTC) |
Last Updated: | 2024-12-13 02:40 (UTC) |
Dependencies (14)
- bazel (bazel-gitAUR, bazel024-binAUR, bazel3AUR, bazel3-binAUR, bazel5AUR, bazelisk-gitAUR, bazeliskAUR, bazelisk-binAUR) (make)
- clang (llvm-rocm-gitAUR, llvm-gitAUR, clang-minimal-gitAUR, clang17-binAUR) (make)
- curl (curl-quiche-gitAUR, curl-http3-ngtcp2AUR, curl-gitAUR, curl-c-aresAUR) (make)
- emacs (emacs-native-comp-gitAUR, emacs-ng-gitAUR, emacs-ngAUR, emacs-lucid-gitAUR, emacs28AUR, emacs28-nativecompAUR, emacs28-noxAUR, emacs-gitAUR, emacs29-gitAUR, emacs-pretestAUR, emacs-pgtk-gitAUR, emacs-lucidAUR, emacs-lucid-nativecompAUR, emacs29-lucid-native-comp-gitAUR, emacs-nativecomp, emacs-nox, emacs-wayland) (make)
- fcitx5 (fcitx5-gitAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- ibus (ibus-gitAUR) (make)
- mesa (mesa-minimal-gitAUR, mesa-gitAUR, mesa-wsl2-gitAUR, amdonly-gaming-mesa-gitAUR, mesa-amd-bc250AUR, mesa-amber) (make)
- pkg-config (pkgconf-gitAUR, pkg-config-gitAUR, pkgconf) (make)
- python (python37AUR, python311AUR, python310AUR) (make)
- python-six (make)
- qt6-base (qt6-base-gitAUR, qt6-base-headlessAUR) (make)
- subversion (make)
- qt6-base (qt6-base-gitAUR, qt6-base-headlessAUR) (optional) – Display GUI of mozc_tool
Required by (3)
Sources (21)
- 0001-remove-download.patch
- git+https://chromium.googlesource.com/breakpad/breakpad
- git+https://chromium.googlesource.com/external/gyp
- git+https://github.com/abseil/abseil-cpp.git
- git+https://github.com/fcitx/mozc.git#commit=f53990354c2efc868a40b00a5d2baa13cadcd01e
- git+https://github.com/google/googletest.git
- git+https://github.com/google/protobuf.git
- git+https://github.com/hiroyuki-komatsu/japanese-usage-dictionary.git
- git+https://github.com/open-source-parsers/jsoncpp.git
- git+https://github.com/utuhiro78/merge-ut-dictionaries.git
- https://gitlab.com/BrLi/brli-aur/-/raw/fcitx5-mozc-ut/jigyosyo-202110.zip
- https://gitlab.com/BrLi/brli-aur/-/raw/fcitx5-mozc-ut/x-ken-all-202110.zip
- jawiki-latest-pages-articles-multistream-index-20241212.txt.bz2
- mozcdic-ut-alt-cannadic-20241212.txt.bz2
- mozcdic-ut-edict2-20241212.txt.bz2
- mozcdic-ut-jawiki-20241212.txt.bz2
- mozcdic-ut-neologd-20241212.txt.bz2
- mozcdic-ut-personal-names-20241212.txt.bz2
- mozcdic-ut-place-names-20241212.txt.bz2
- mozcdic-ut-skk-jisyo-20241212.txt.bz2
- mozcdic-ut-sudachidict-20241212.txt.bz2
Latest Comments
1 2 3 4 Next › Last »
Dettorer commented on 2024-11-03 01:01 (UTC)
I think this package wasn't update along the recent design changes:
source
changed, they end with.txt.bz2
instead of.txt.tar.bz2
now;_dictdate
value in them it seems, so thecat
command fails;merge/tmerge_dictionaries.py
script?).ToastedWookiee commented on 2024-10-24 14:14 (UTC) (edited on 2024-10-25 06:12 (UTC) by ToastedWookiee)
In "merge-ut-dictionaries" in a commit 3 days ago the files for "remove_duplicate_ut_entries.py", "count_word_hits.py", and "apply_word_hits.py" were removed from the "src" directory and are located in "src/merge"
https://github.com/utuhiro78/merge-ut-dictionaries/commit/b2198e7f15145f1ed4ef84ac0ffaa5f81a8931e0
but then in the current file, there is an error, due to the removal of the file download line, which has been changed in the src:
ToastedWookiee commented on 2024-10-24 07:21 (UTC) (edited on 2024-10-24 07:22 (UTC) by ToastedWookiee)
BudgieUser commented on 2024-10-22 15:48 (UTC) (edited on 2024-10-22 15:49 (UTC) by BudgieUser)
hearth commented on 2024-08-03 09:15 (UTC)
The url for
x-ken-all-202110.zip
appears to be incorrect:brli commented on 2024-07-30 00:34 (UTC)
hi,
thanks for using this aur and posting issues.
sorry for the late update that takes so far.
I was having issue accessing my build box, but hopefully that is fixed.
this push of 20240730 should have fixed a couple of mentioned issues including the protobuf build error and python switch.
soylens commented on 2024-07-29 06:11 (UTC)
Apparently either something in GCC or in Protobuf is causing problems for me. Anyone else?
soylens commented on 2024-07-14 17:03 (UTC) (edited on 2024-07-14 17:32 (UTC) by soylens)
So a few recent upstream updates implies that minor changes to PKGBUILD are needed. Anyone should be able to figure out within 10min by themself.
Anyway:
merge-ut-dictionaries switched to python from ruby. one reads the old/new sources and modifies PKGBUILD accordingly.
bazel relies on java 21 now. there is an explicit line setting JAVA_HOME in the PKGBUILD that causes issues. it's obvious what to do.
EDIT: also something is broken protobuf and causes problems when it gets to map_fields.cc there. Not sure what and when though.
jaro3 commented on 2024-07-02 17:09 (UTC)
That was after rm -rf /root/.cache/bazel
Now when I replaced bazel5 from AUR another error terminates the compilation:
==> Starting build()... Extracting Bazel installation... Starting local Bazel server and connecting to it... INFO: Reading rc options for 'build' from /usr/src/tmp/mozc-ut-full/src/mozc/src/.bazelrc: 'build' options: --cxxopt -std=c++20 --copt -funsigned-char --copt -Wno-sign-compare --copt -Wno-char-subscripts --host_cxxopt -std=c++20 --host_copt -funsigned-char --host_copt -Wno-sign-compare --host_copt -Wno-char-subscripts --objccopt -fsigned-char --noenable_bzlmod ERROR: --noenable_bzlmod :: Unrecognized option: --noenable_bzlmod ==> ERROR: A failure occurred in build(). Aborting...
This thing doesn't compile on current Arch installation, I am going to mozc-ut + ibus-mozc
brli commented on 2024-07-02 09:13 (UTC)
@jaro3: please use code tag to include output.
Also, make sure your using clean chroot.
But still, you can try to rm -rf /root/.cache, and retry.
1 2 3 4 Next › Last »