Package Base Details: mozc

Git Clone URL: https://aur.archlinux.org/mozc.git (read-only)
Submitter: ponsfoot
Maintainer: ponsfoot
Last Packager: ponsfoot
Votes: 55
Popularity: 1.130031
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


[pnsft-pur]

SigLevel = Optional TrustAll

Server = https://osdn.net/projects/ponsfoot-aur/storage/pur/x86_64


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

See https://wiki.archlinux.org/index.php/Mozc for more detail.

Latest Comments

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

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/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

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?

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

@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.

taro-k commented on 2014-10-13 03:25

@ponsfoot thx. IMO, not trivial amount of users have concern about security/privacy especially for this kind of program. The direct download from upstream must make this point clear at least. If you don't like to do that, I will submit another package based on your great work. For such users, some additional makedepends don't matter. Also I just downloaded by svn but it took only 1 min. with narrow band not in developed country.

ponsfoot commented on 2014-10-13 02:08

@taro-k:
The upstream doesn't provide source tar balls for each version's any more.
If you want to get latest version of Mozc from upstream, you have to clone from svn repo. I think it's not efficient for end users as AUR package which requires longer download time and svn as makedepends.

taro-k commented on 2014-10-13 01:32

Hi, thx lot for your contribution. The "source" seems to be the private storage, not official/upstream source tree. I feel it's better the source is downloaded from upstream directly like many of other AUR packages.

ponsfoot commented on 2014-06-07 04:08

@hagabaka:
It means that you will build all packages (and install all depends/makedepends) even if there are packages which you won't use.

BTW, I noticed that ibus-mozc isn't mandatory (for uim-mozc users). I'll make it configurable.