Arch Linux User Repository

What if you try not using yay, but directly use makepkg in cloned aur directory?

It seems like that line is not correctly executing and uncommenting the DEFAULT_BUILD_LABEL_MACOS. I checked pwd and all, command works fine if I do it, just not in build() for some reason. I tried deleting ALL cache (yay -Scc, yes to all) but that didn't help.

I have managed to build it by using yay -Syu --editmenu and adding a simple sleep 10 after the sed to manually edit the mozc/src/version.bzl file. Scuffed solution if you ask me, but computer should do what it is told and it does not so I must punish it now :)

@Jubiman, @drunkmoe: please check that you're using clean build root, a clean chroot build root would be even better.

Also, check your build src directory if Line 120 of PKGBUILD ( https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=mozc-ut-full#n120 ) has been executed correctly that the line start with DEFAULT_BUILD_LABEL_MACOS is not comment out in mozc/src/version.bzl

I just got the exact same error trying to update

Build failing:

ERROR: Traceback (most recent call last):
        File "/home/john/.cache/yay/mozc-ut-full/src/mozc/src/BUILD.bazel", line 45, column 25, in <toplevel>
                load("//:version.bzl", "DEFAULT_BUILD_LABEL_MACOS")
Error: file '//:version.bzl' does not contain symbol 'DEFAULT_BUILD_LABEL_MACOS'
ERROR: /home/john/.cache/yay/mozc-ut-full/src/mozc/src/BUILD.bazel: no such target '//:compiler_msvc_like': target 'compiler_msvc_like' not declared in package '' defined 
by /home/john/.cache/yay/mozc-ut-full/src/mozc/src/BUILD.bazel
ERROR: /home/john/.cache/yay/mozc-ut-full/src/mozc/src/gui/tool/BUILD.bazel:122:18: errors encountered resolving select() keys for //gui/tool:mozc_tool
ERROR: Analysis of target '//gui/tool:mozc_tool' failed; build aborted

Could be something obvious I'm missing - just thought I'd raise it in case it isn't (and if it is, any advice would be appreciated!)

@Jubiman

This will regularly happen with this package because of the way the dependencies are pulled IIRC. See page 3 of these comments. It is possible to modify the pkgbuild to use specific files or to skip the hash checks. Alternatively you can update the checksums yourself. None of these are an ideal solution.

I am unable to start compiling due to failed sha512sums. It is related to jawiki-latest-pages-articles-multistream-index-20250910.txt.bz2. The expected hash is 5d66953bc816aeba63a166e191f7453a561f755bfd57f611f867378583e18c2aaa25d78340b641070e28672659ed241fd9252010df3d9a64dff79f0b68f613c7 while the hash I get is 87b5dfb5b6464fcd043da20d4cf21eaea3fb74c220261f70bc0f3bec29f31b8cc9383ccfac4094dccc80514034491fcff2585640925099d947a12bb57b4ef025 from files downloaded manually and through yay. Am I the only one or did it get updated in the past few days?

@brli sure, sorry for the lack of context. I think it should be universally reproducible with a clean build now as github changing existing files checksums is a well known problem with an issue created long ago.

Still, here are some additional details. Package: mozc-ut-full-common Stage: build()

14:13:43 ==> Starting build()...
14:13:43 Extracting Bazel installation...
14:13:44 Starting local Bazel server (8.3.1) and connecting to it...
14:13:45 Computing main repo mapping: 
...
14:13:57 Analyzing: 6 targets (178 packages loaded, 5374 targets configured)
14:13:57 WARNING: Download from https://github.com/hiroyuki-komatsu/japanpost_zipcode/raw/refs/heads/main/jigyosyo.zip failed: class com.google.devtools.build.lib.bazel.repository.downloader.UnrecoverableHttpException Checksum was f390501cbfe143921a939884178e5b33ca246181803d814e5f58676c19e91a6c but wanted 0e62af72f56a3039409dc105057051df0e374c2e373a2a068172daaaa1a9af13
14:13:57 INFO: Repository +_repo_rules7+zip_code_jigyosyo instantiated at:
14:13:57   <builtin>: in <toplevel>
14:13:57 Repository rule http_archive defined at:
14:13:57   /home/builder/.cache/bazel/_bazel_builder/ad1e64ce2a5749c9b6295b7eb211686d/external/bazel_tools/tools/build_defs/repo/http.bzl:394:31: in <toplevel>
14:13:57 ERROR: /home/builder/.cache/bazel/_bazel_builder/ad1e64ce2a5749c9b6295b7eb211686d/external/bazel_tools/tools/build_defs/repo/http.bzl:139:45: An error occurred during the fetch of repository '+_repo_rules7+zip_code_jigyosyo':
14:13:57    Traceback (most recent call last):
14:13:57    File "/home/builder/.cache/bazel/_bazel_builder/ad1e64ce2a5749c9b6295b7eb211686d/external/bazel_tools/tools/build_defs/repo/http.bzl", line 139, column 45, in _http_archive_impl
14:13:57        download_info = ctx.download_and_extract(
14:13:57 Error in download_and_extract: java.io.IOException: Error downloading [https://github.com/hiroyuki-komatsu/japanpost_zipcode/raw/refs/heads/main/jigyosyo.zip] to /home/builder/.cache/bazel/_bazel_builder/ad1e64ce2a5749c9b6295b7eb211686d/external/+_repo_rules7+zip_code_jigyosyo/temp15090556650305586974/jigyosyo.zip: Checksum was f390501cbfe143921a939884178e5b33ca246181803d814e5f58676c19e91a6c but wanted 0e62af72f56a3039409dc105057051df0e374c2e373a2a068172daaaa1a9af13
14:13:58 ERROR: no such package '@@+_repo_rules7+zip_code_jigyosyo//': java.io.IOException: Error downloading [https://github.com/hiroyuki-komatsu/japanpost_zipcode/raw/refs/heads/main/jigyosyo.zip] to /home/builder/.cache/bazel/_bazel_builder/ad1e64ce2a5749c9b6295b7eb211686d/external/+_repo_rules7+zip_code_jigyosyo/temp15090556650305586974/jigyosyo.zip: Checksum was f390501cbfe143921a939884178e5b33ca246181803d814e5f58676c19e91a6c but wanted 0e62af72f56a3039409dc105057051df0e374c2e373a2a068172daaaa1a9af13
14:14:00 ERROR: /home/builder/.cache/aurutils/sync/mozc-ut-full/src/mozc/src/dictionary/BUILD.bazel:743:11: //dictionary:zip_code_data depends on @@+_repo_rules7+zip_code_jigyosyo//:JIGYOSYO.CSV in repository @@+_repo_rules7+zip_code_jigyosyo which failed to fetch. no such package '@@+_repo_rules7+zip_code_jigyosyo//': java.io.IOException: Error downloading [https://github.com/hiroyuki-komatsu/japanpost_zipcode/raw/refs/heads/main/jigyosyo.zip] to /home/builder/.cache/bazel/_bazel_builder/ad1e64ce2a5749c9b6295b7eb211686d/external/+_repo_rules7+zip_code_jigyosyo/temp15090556650305586974/jigyosyo.zip: Checksum was f390501cbfe143921a939884178e5b33ca246181803d814e5f58676c19e91a6c but wanted 0e62af72f56a3039409dc105057051df0e374c2e373a2a068172daaaa1a9af13
14:14:00 ERROR: Analysis of target '//server:mozc_server' failed; build aborted: Analysis failed
INFO: Elapsed time: 24.515s, Critical Path: 0.04s
INFO: 1 process: 1 internal.
ERROR: Build did NOT complete successfully
FAILED: 
==> ERROR: A failure occurred in build().
    Aborting...

Hi, @Bitals

Would you mind share more lines between which this error line happens?

At what step of the process do the build system try to download and verify checksum?

'@@+_repo_rules7+zip_code_jigyosyo//': java.io.IOException: Error downloading [https://github.com/hiroyuki-komatsu/japanpost_zipcode/raw/refs/heads/main/jigyosyo.zip] to /home/builder/.cache/bazel/_bazel_builder/ad1e64ce2a5749c9b6295b7eb211686d/external/+_repo_rules7+zip_code_jigyosyo/temp15090556650305586974/jigyosyo.zip: Checksum was f390501cbfe143921a939884178e5b33ca246181803d814e5f58676c19e91a6c but wanted 0e62af72f56a3039409dc105057051df0e374c2e373a2a068172daaaa1a9af13