Package Details: mozc 2.30.5448.102-3

Git Clone URL: https://aur.archlinux.org/mozc.git (read-only, click to copy)
Package Base: mozc
Description: The Open Source edition of Google Japanese Input
Upstream URL: https://github.com/google/mozc
Licenses: Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND MIT AND NAIST-2003 AND Unicode-3.0 AND LicenseRef-Okinawa-Dictionary
Conflicts: mozc-ut
Submitter: ponsfoot
Maintainer: Nocifer
Last Packager: Nocifer
Votes: 79
Popularity: 1.32
First Submitted: 2010-08-09 04:27 (UTC)
Last Updated: 2024-05-17 08:53 (UTC)

Dependencies (7)

Sources (1)

Pinned Comments

Nocifer commented on 2022-05-29 21:53 (UTC) (edited on 2023-08-22 09:33 (UTC) by Nocifer)

If you're getting compilation errors, please delete your Bazel cache (~/.cache/bazel by default).

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 16 Next › Last »

ishitatsuyuki commented on 2015-05-18 09:01 (UTC)

Pacaur: ==> Extracting sources... -> Creating working copy of mozc git repo... fatal: reference is not a tree: 40f67e035d32365dab823d292c173a0d67ad23c7

nash commented on 2015-05-18 02:07 (UTC)

We need to revise the commit id (_mozcrev) in PKGBUILD. https://github.com/google/mozc/issues/290

ponsfoot commented on 2015-05-16 08:25 (UTC)

If you use mozc 2.16.2072.102-1 or earlier and build mozc yourself, remove $SRCDEST/{mozc,gyp} before building 2.17.2095.102-1.

ponsfoot commented on 2015-02-09 10:51 (UTC)

@wiegraffolles: Build preparation (ln -sf `which python2` $srcdir/python in PKGBUILD) seems to failed. Try again. It's not reproduced on my system. If you don't have a strong insistence, try to use unofficial user repository: https://wiki.archlinux.org/index.php/Mozc#Unofficial_user_repository Note: Please show me full build log using http://pastebin.com/ from the next time.

wiegraffolles commented on 2015-02-09 09:55 (UTC)

I get this error when trying to build the latest update: INFO: Running: ninja -j 8 -C out_linux/Release mozc_server mozc_tool ibus_mozc mozc_renderer ninja: Entering directory `out_linux/Release' [8/841] ACTION Generating gen/gui/character_pad/data/cp932_map.h. FAILED: cd ../../gui; python ../build_tools/redirect.py ../out_linux/Release/gen/gui/character_pad/data/cp932_map.h character_pad/data/gen_cp932_map.py ../data/unicode/CP932.TXT File "../build_tools/redirect.py", line 61 print '==========' ^ SyntaxError: Missing parentheses in call to 'print' [8/841] ACTION Generating Resource file from config_dialog.qrc ninja: build stopped: subcommand failed. Traceback (most recent call last): File "build_mozc.py", line 1454, in <module> main() File "build_mozc.py", line 1450, in main procedure[1](cmd_opts, cmd_args, original_directory_name) File "build_mozc.py", line 1070, in BuildMain BuildOnLinux(options, targets, original_directory_name) File "build_mozc.py", line 1026, in BuildOnLinux RunOrDie([make_command] + build_args + target_names) File "/tmp/makepkg/mozc/src/mozc/build_tools/util.py", line 99, in RunOrDie '=========='])) build_tools.util.RunOrDieError: ========== ERROR: ninja -j 8 -C out_linux/Release mozc_server mozc_tool ibus_mozc mozc_renderer ========== ==> ERROR: A failure occurred in build(). Aborting... :: mozc cleaning skipped :: failed to build ibus-mozc,mozc package(s) Any ideas on how to fix it?

m13253 commented on 2015-01-25 14:20 (UTC)

It seems that the latest Mozc source requiers gyp available as a command: Traceback (most recent call last): File "build_mozc.py", line 1478, in <module> main() File "build_mozc.py", line 1474, in main procedure[1](cmd_opts, cmd_args, original_directory_name) File "build_mozc.py", line 958, in GypMain RunOrDie(gyp_command + gyp_options) File "/tmp/yaourt-tmp-brilliant/aur-mozc/src/mozc/build_tools/util.py", line 99, in RunOrDie Maybe we should depend on gyp / gyp-svn, or set $PATH to enable gyp instantly?

ponsfoot commented on 2014-11-03 06:06 (UTC)

ninja is unnecessary as makedepends anymore.

taro-k commented on 2014-10-13 06:48 (UTC)

@ponsfoot Thanks lot for your immediate reply and understanding. Also I am happy about you understood this is general security thing on AUR (and beyond, as you stated.) I am looking forward to the next release.

ponsfoot commented on 2014-10-13 05:26 (UTC)

@taro-k: I can see how you feel (but, in your opinion, all binary repos and many other distros which provides source tar balls themselves like debian, fedora etc. have same concern). Actually, getting source from upstream directly is easier than current style for maintenance. You think 1 min for download is just 'only' (and you should downloaded depot_tools using git, too), I will accommodate a request from you (on the next release) if there is no opposition from other people. mozc-svn is suitable for your concern.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 12 .. 16 Next › Last »