Package Base Details: mozc

Git Clone URL: (read-only, click to copy)
Submitter: ponsfoot
Maintainer: ponsfoot
Last Packager: ponsfoot
Votes: 61
Popularity: 0.55
First Submitted: 2010-08-09 04:27
Last Updated: 2018-11-30 11:34

Packages (3)

Pinned Comments

ponsfoot commented on 2013-05-28 07:43

(repository moved)
Unofficial user repository of Mozc is ready.
If you want to use the repo, add the following into your /etc/pacman.conf


SigLevel = Optional TrustAll

Server =

You can specify `pacman -S mozc-im' to choose all of Mozc packages.

See for more detail.

Latest Comments

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

ishitatsuyuki commented on 2015-05-18 09:01

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

nash commented on 2015-05-18 02:07

We need to revise the commit id (_mozcrev) in PKGBUILD.

ponsfoot commented on 2015-05-16 08:25

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

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:

Note: Please show me full build log using from the next time.

wiegraffolles commented on 2015-02-09 09:55

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/ ../out_linux/Release/gen/gui/character_pad/data/cp932_map.h character_pad/data/ ../data/unicode/CP932.TXT
File "../build_tools/", 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 "", line 1454, in <module>
File "", line 1450, in main
procedure[1](cmd_opts, cmd_args, original_directory_name)
File "", line 1070, in BuildMain
BuildOnLinux(options, targets, original_directory_name)
File "", line 1026, in BuildOnLinux
RunOrDie([make_command] + build_args + target_names)
File "/tmp/makepkg/mozc/src/mozc/build_tools/", line 99, in RunOrDie
ERROR: ninja -j 8 -C out_linux/Release mozc_server mozc_tool ibus_mozc mozc_renderer
==> ERROR: A failure occurred in build().
:: 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

It seems that the latest Mozc source requiers gyp available as a command:

Traceback (most recent call last):
File "", line 1478, in <module>
File "", line 1474, in main
procedure[1](cmd_opts, cmd_args, original_directory_name)
File "", line 958, in GypMain
RunOrDie(gyp_command + gyp_options)
File "/tmp/yaourt-tmp-brilliant/aur-mozc/src/mozc/build_tools/", line 99, in RunOrDie

Maybe we should depend on gyp / gyp-svn, or set $PATH to enable gyp instantly?

o_caino commented on 2014-11-04 23:51

it seems that ninja is still required
ERROR: ninja -j 2 -C out_linux/Release mozc_server mozc_tool ibus_mozc mozc_renderer

ponsfoot commented on 2014-11-03 06:06

ninja is unnecessary as makedepends anymore.

taro-k commented on 2014-10-13 06:48

@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

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.