Arch Linux User Repository

Ah interesting, sharp is a transitive dep and when it detects libvips installed it tries to build from source. But authenticator doesn't actually use sharp so I've just disabled its build. Thanks for reporting.

I get this error during yarn install: YN0009: │ sharp@npm:0.33.5 couldn't be built successfully (exit code 1, logs can be found here: /tmp/xfs-74ce54d3/build.log). The referenced log file looks like this:

# This file contains the result of Yarn building a package (sharp@npm:0.33.5)
# Script name: install

sharp: Detected globally-installed libvips v8.18.3
sharp: Attempting to build from source via node-gyp
sharp: Found node-addon-api 
sharp: Found node-gyp 11.5.0
sharp: See https://sharp.pixelplumbing.com/install#building-from-source
?[31m?[1mUsage Error?[22m?[39m: Couldn't find a script name "node-gyp" in the top-level (used by sharp@npm:0.33.5). This typically happens because some package depends on "node-gyp" to build itself, but didn't list it in their dependencies. To fix that, please run "yarn add node-gyp" into your top-level workspace. You also can open an issue on the repository of the specified package to suggest them to use an optional peer dependency.

?[1m$ ?[22myarn run [--inspect] [--inspect-brk] [-T,--top-level] [-B,--binaries-only] [--require #0] <scriptName> ...

I got around the error by adding yarn add node-gyp before yarn install in the PKGBUILD. I don't know if that's the best solution, but it worked for me.

Hi @AlphaLynx,

That was it! I just issued rustup update and after it completed updating all components, I could build proton-authenticator seamlessly. Thanks for guiding me to resolve this issue. Much appreciate it!

@Musikolo I see the issue, you have cargo 1.86.0 (adf9b6ad1 2025-02-28). When rustup package is installed, your cargo and toolchains are installed in your home directory, and don't get updated with the system. So you need to specifically update the Rust toolchain with rustup update. for more info see here.

@AlphaLynx, I repeated the whole process again, and before getting started, I updated my box to latest and rebooted. First, I tried with rustup and the same problem occurred. Then, I replaced rustup with rust and it worked seamlessly. I got some details of each of the setups which shows different cargo versions and targets available:

• rustup 1.29.0-2: pastebin here.
• rust 1:1.95.0-1: pastebin here.

I hope it helps.

@Musikolo I can't reproduce that error. looks like the error means your cargo doesn't recognize 'host-tuple'. That was added in cargo 1.91.0 (https://doc.rust-lang.org/nightly/cargo/CHANGELOG.html#cargo-191-2025-10-30), so maybe you have an older version? try updating, rustup update stable

@AlphaLynx, it looks like builds fail if the host machine has the rustup package installed:

➤ YN0000: └ Completed in 26s 904ms
➤ YN0000: · Done with warnings in 46s 353ms
[root]: Process started
[root]: Process exited (exit code 0), completed in 1s 205ms
Done in 1s 208ms
    Updating crates.io index
error: failed to run `rustc` to learn about target-specific information

Caused by:
  process didn't exit successfully: `/home/musikolo/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/rustc - --crate-name ___ --print=file-names --target host-tuple --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=split-debuginfo --print=crate-name --print=cfg -Wwarnings` (exit status: 1)
  --- stderr
  error: Error loading target specification: Could not find specification for target "host-tuple". Run `rustc --print target-list` for a list of built-in targets

==> ERROR: A failure occurred in prepare().
    Aborting...

I was able to build it by uninstalling it which uses rust as the default package for cargo. However, it would be appreciated if a workaround could be found for this.

Thanks!

This package fails to install. To fix it, I needed to add export SENTRYCLI_SKIP_DOWNLOAD=1 before yarn install. Can you please fix this issue?

(proton-authenticator:94955): Gtk-WARNING **: 15:11:10.272: Theme parsing error: gtk-dark.css:1959:16: 'border-spacing' is not a valid property name

(proton-authenticator:94955): Gtk-WARNING **: 15:11:10.273: Theme parsing error: gtk-dark.css:3272:16: '-gtk-icon-size' is not a valid property name

(proton-authenticator:94955): Gtk-WARNING **: 15:11:10.273: Theme parsing error: gtk-dark.css:3286:16: '-gtk-icon-size' is not a valid property name Gdk-Message: 15:11:11.603: Error 71 (Erro de protocolo) dispatching to Wayland display.

@Evrenos the only reason I have nodejs-lts as a makedepend instead of nodejs is because upstream lists LTS as a prerequisite in the monorepo. I think the package will still build fine with non-LTS nodejs, but it's probably better to use the dependency that upstream says, in case there is some incompatibility between versions.

edit: with nodejs v25 there's some breaking change, so using the LTS version is important