Package Details: fcitx5-mozc-ut 2.30.5618.102-1

Git Clone URL: https://aur.archlinux.org/fcitx5-mozc-ut.git (read-only, click to copy)
Package Base: fcitx5-mozc-ut
Description: Mozc module for Fcitx5
Upstream URL: https://github.com/fcitx/mozc
Licenses: Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND GPL-2.0-or-later AND MIT AND NAIST-2003 AND Unicode-3.0 AND LicenseRef-Okinawa-Dictionary
Conflicts: fcitx5-mozc
Provides: fcitx5-mozc
Submitter: Nocifer
Maintainer: Nocifer
Last Packager: Nocifer
Votes: 34
Popularity: 2.29
First Submitted: 2020-12-08 09:21 (UTC)
Last Updated: 2024-10-10 12:39 (UTC)

Pinned Comments

Nocifer commented on 2022-05-29 21:55 (UTC) (edited on 2023-08-22 09:32 (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 Next › Last »

Ayaka commented on 2022-11-02 08:34 (UTC)

  -> Downloading mozcdic-ut-20220723.tar.bz2...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0
curl: (22) The requested URL returned error: 404
==> ERROR: Failure while downloading https://osdn.net/users/utuhiro/pf/utuhiro/dl/mozcdic-ut-20220723.tar.bz2
    Aborting...
 -> error downloading sources: mozc-ut-full 
         context: exit status 1 

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

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

Nocifer commented on 2022-02-25 19:18 (UTC)

Nah, it's already a hard dependency of bazel so it's guaranteed to be present on the system.

ruahcra commented on 2022-02-25 01:36 (UTC)

export JAVA_HOME='/usr/lib/jvm/java-11-openjdk/'

Should the PKGBUILD have 'java-environment==11' in makedepends?

ruahcra commented on 2022-02-01 12:17 (UTC)

I just tried it one more time before trying one of your suggestions and it just happened to work :P Thanks anyway, I will try deleting the cache next time if it happens.

Nocifer commented on 2022-02-01 11:22 (UTC)

Hmm, I just tried it twice and the file downloaded without problem. Does the package build with makepkg itself? If so, it could be something to do with paru. Also, if you haven't already, you could try removing Bazel's cache; even though it sounds counterintuitive in regards to this particular issue, Bazel is known for producing such weird quirks from time to time.

ruahcra commented on 2022-02-01 09:51 (UTC) (edited on 2022-02-01 09:52 (UTC) by ruahcra)

Is anyone else having trouble during install with Bazel failing to download the files from the japan post site (works fine in browser though...)?

/home/user/.cache/paru/clone/mozc/src/mozc-git/src/WORKSPACE.bazel:170:13: fetching http_archive rule //external:zip_code_jigyosyo: Traceback (most recent call last):
    File "/home/user/.cache/bazel/_bazel_user/4c479eee4713cbfd37f7dd3576dee827/external/bazel_tools/tools/build_defs/repo/http.bzl", line 111, column 45, in _http_archive_impl
        download_info = ctx.download_and_extract(
Error in download_and_extract: java.io.IOException: Error downloading [https://www.post.japanpost.jp/zipcode/dl/jigyosyo/zip/jigyosyo.zip] to /home/user/.cache/bazel/_bazel_user/4c479eee4713cbfd37f7dd3576dee827/external/zip_code_jigyosyo/temp14725772222497573027/jigyosyo.zip: Unknown host: www.post.japanpost.jp

Nocifer commented on 2022-01-13 09:37 (UTC) (edited on 2022-01-13 09:44 (UTC) by Nocifer)

Due to a mistake I made in the previous release, newer versions of this package may fail to gracefully update over a preexisting 2.26.4596.102 setup (installing fresh won't be an issue) with the following error (or something similar):

error: failed to prepare transaction (could not satisfy dependencies)
:: installing mozc (2.26.4610.102-1) breaks dependency 'mozc=2.26.4596.102' required by fcitx5-mozc-ut

The TL;DR version of it is that you will need to do one of the following:

1) Uninstall this package and then reinstall it; or

2) Edit the file /var/lib/pacman/local/fcitx5-mozc-ut-2.26.4596.102-1/desc and replace

%DEPENDS%
fcitx5
mozc=2.26.4596.20211205

with

%DEPENDS%
fcitx5
mozc>=2.26.4596.20211205

and then proceed to update as per usual.

(In other words, the mozc version dependency should be a lax >= instead of a strict =; which AFAIR is also standard PKGBUILD practice, but somehow I completely forgot about it.)

Hopefully this is now fixed, but I'll wait for your input (if any) before I can be certain. Sorry for the inconvenience.

Nocifer commented on 2022-01-10 21:14 (UTC)

@lionslancer Yup, I'd say you've summed it up pretty nicely. The naming/packaging situation is a bit of a mess right now, but contacting the maintainers of fcitx5-mozc and mozc-ut in order to try and find a proper solution is already on my to-do list. Hopefully things won't prove to be too confusing for the users in the meantime.

lionslancer commented on 2022-01-10 20:03 (UTC) (edited on 2022-01-10 20:05 (UTC) by lionslancer)

Hi! I recently ran into an issue where I had to reinstall this package because the new release depends on mozc, which mozc-ut-common didn't provide pre-update, causing it do attempt to install the mozc package which conflicts with the former.

From looking at various PKBUILDs, it looks like you've become the maintainer of mozc and this change is to make the various framework module packages compatible with both mozc and mozc-ut-common. Am I then correct in assuming that the relevant packages going forward are the following?

  • mozc and mozc-ut-common for the engine
  • fcitx5-mozc-ut, ibus-mozc, and emacs-mozc for the modules

If I've understood correctly, there's no longer anything UT-specific about this package, and the names fcitx5-mozc and mozc-ut would have been used if not for the naming conflict with existing packages. Is this accurate?

(edit: I accidentally deleted my comment while initially trying to edit the formatting, sorry if you received multiple notifications.)