Arch Linux User Repository

I'm not sure. Can you try to reproduce this?

git clone https://aur.archlinux.org/yaak.git
cd yaak
pkgctl build
tar tf yaak-2026.2.0-1-x86_64.pkg.tar.zst | grep usr/src/debug

@svenstaro: nothing is left behind by installing this package; you should check the current hooks on your system.

There's a lot of stuff in /usr/src/debug after installing this package. I don't think that's intended.

@ruan: Thank you for spotting this problem and for facilitating the fix with your patch! I have updated the package.

Installation is failing, seems related to some changes in the tauri build logic, in release 2026.1.0, as per the release notes: https://github.com/mountain-loop/yaak/releases/tag/v2026.1.0

• Decouple core Yaak logic from Tauri in #354 -> Check https://github.com/mountain-loop/yaak/pull/354

Logs:

   Compiling yaak-http v0.1.0 (/home/user/.cache/yay/yaak/src/yaak/crates/yaak-http)
   Compiling yaak-tauri-utils v0.1.0 (/home/user/.cache/yay/yaak/src/yaak/crates-tauri/yaak-tauri-utils)
   Compiling yaak-plugins v0.1.0 (/home/user/.cache/yay/yaak/src/yaak/crates/yaak-plugins)
   Compiling git2 v0.20.2
   Compiling yaak-ws v0.1.0 (/home/user/.cache/yay/yaak/src/yaak/crates/yaak-ws)
   Compiling yaak-git v0.1.0 (/home/user/.cache/yay/yaak/src/yaak/crates/yaak-git)
    Finished `release` profile [optimized] target(s) in 3m 43s
       Built application at: /home/user/.cache/yay/yaak/src/yaak/target/release/yaak-app
        Info Patching binary "/home/user/.cache/yay/yaak/src/yaak/target/release/yaak-app" for type deb
    Bundling yaak_2026.1.0_amd64.deb (/home/user/.cache/yay/yaak/src/yaak/target/release/bundle/deb/yaak_2026.1.0_amd64.deb)
    Finished 1 bundle at:
        /home/user/.cache/yay/yaak/src/yaak/target/release/bundle/deb/yaak_2026.1.0_amd64.deb

sed: can't read /home/user/.cache/yay/yaak/src/yaak/src-tauri/target/release/bundle/deb/yaak_2026.1.0_*/data/usr/share/applications/yaak.desktop: No such file or directory
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: yaak-exit status 4
 -> Failed to install the following packages. Manual intervention is required:

I'm using yay, and I found the yaak.desktop in:

/home/user/.cache/yay/yaak/src/yaak/target/release/bundle/deb/yaak_2026.1.0_amd64/data/usr/share/applications/yaak.desktop

So I guess the file is now being created here:

${srcdir}/yaak/target/release/bundle/deb/yaak_${pkgver}_.../data/usr/share/applications/yaak.desktop

I guess some adjustments to the build process are necessary.

Edit: Here's a patch to fix the issue, tested locally:

From e03dcab3bbeea70719d70a6a6922a6153dbf94fd Mon Sep 17 00:00:00 2001
From: Ruan Bahia <ruanmed@live.com>
Date: Wed, 21 Jan 2026 15:05:28 -0300
Subject: [PATCH] fix: tauri decoupling in yaak 2026.1.0

---
 PKGBUILD | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/PKGBUILD b/PKGBUILD
index 6a6c453..f3c4b7c 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -55,7 +55,7 @@ b2sums=('dd95df94dd785ed9450656ac5c8cafc019f0913b3c546e937361f8dcde6a3a17a54ffed

 build() {
    export YAAK_VERSION="${pkgver}"
-   export TAURI_APP_PATH="${srcdir}/yaak/src-tauri/"
+   export TAURI_APP_PATH="${srcdir}/yaak/crates-tauri/"
    export CI=true

    cd "${srcdir}/yaak/"
@@ -65,12 +65,12 @@ build() {

    sed -e 's|Name=yaak|Name=Yaak|' \
        -e '$aGenericName=API Client' \
-       -i "${srcdir}/yaak/src-tauri/target/release/bundle/deb/yaak_${pkgver}_"*/data/usr/share/applications/yaak.desktop
+       -i "${srcdir}/yaak/target/release/bundle/deb/yaak_${pkgver}_"*/data/usr/share/applications/yaak.desktop
 }

 package() {
    cp -a \
-       "${srcdir}/yaak/src-tauri/target/release/bundle/deb/yaak_${pkgver}_"*/data/usr/ \
+       "${srcdir}/yaak/target/release/bundle/deb/yaak_${pkgver}_"*/data/usr/ \
        "${pkgdir}/usr/"
    install -Dm644 \
        "${srcdir}/yaak/LICENSE" \
-- 
2.52.0

Starting up with the latest version gives this error:

thread 'main' (260797) panicked at /home/yak/.cache/yay/yaak/src/yaak/src-tauri/yaak-plugins/src/manager.rs:154:83:
called `Result::unwrap()` on an `Err` value: TauriShellErr(Io(Os { code: 2, kind: NotFound, message: "No such file or directory" }))
stack backtrace:
   0: __rustc::rust_begin_unwind
             at /rustc/ed61e7d7e242494fb7057f2657300d9e77bb4fcb/library/std/src/panicking.rs:698:5
   1: core::panicking::panic_fmt
             at /rustc/ed61e7d7e242494fb7057f2657300d9e77bb4fcb/library/core/src/panicking.rs:75:14
   2: core::result::unwrap_failed
             at /rustc/ed61e7d7e242494fb7057f2657300d9e77bb4fcb/library/core/src/result.rs:1855:5
   3: tokio::runtime::park::CachedParkThread::block_on
   4: tokio::runtime::runtime::Runtime::block_on
   5: yaak_plugins::manager::PluginManager::new
   6: core::ops::function::FnOnce::call_once{{vtable.shim}}
   7: <tauri::plugin::TauriPlugin<R,C> as tauri::plugin::Plugin<R>>::initialize
   8: tauri::plugin::initialize
   9: tauri::plugin::PluginStore<R>::initialize_all
  10: tauri::app::Builder<R>::build
  11: tauri_app_lib::run

Since the update to 2025.9.x yaak-app doesn't start anymore as all the "vendored" package content is now missing. I had to change the build line to npm run tauri build -- --config ./src-tauri/tauri.release.conf.json --bundles deb --no-sign to get a working package again.

The !strip option in the PKGBUILD also leads to the inclusion of debug package content, commenting this option out still leads to a working binary, so the comment there seems to not be correct (anymore) and the option can be removed.

@dallasrevolt The problem should now be fixed thanks to the suggestion from @kstolp

Hello! I got an error:

[INFO]: 🎯  Checking for the Wasm target...
Error: wasm32-unknown-unknown target not found in sysroot: "/usr"

Used rustc from the following path: "/usr/bin/rustc"
It looks like Rustup is not being used. For non-Rustup setups, the wasm32-unknown-unknown target needs to be installed manually. See https://rustwasm.github.io/wasm-pack/book/prerequisites/non-rustup-setups.html on how to do this.

Caused by: wasm32-unknown-unknown target not found in sysroot: "/usr"

Used rustc from the following path: "/usr/bin/rustc"
It looks like Rustup is not being used. For non-Rustup setups, the wasm32-unknown-unknown target needs to be installed manually. See https://rustwasm.github.io/wasm-pack/book/prerequisites/non-rustup-setups.html on how to do this.

npm error Lifecycle script `build` failed with error:
npm error code 1
npm error path /home/dallas/.cache/yay/yaak/src/yaak/src-tauri/yaak-templates
npm error workspace @yaakapp-internal/templates@1.0.0
npm error location /home/dallas/.cache/yay/yaak/src/yaak/src-tauri/yaak-templates
npm error command failed
npm error command sh -c wasm-pack build --target bundler


> @yaakapp/app@1.0.0 build
> vite build

vite v7.0.8 building for production...
Generated route tree in 199ms
transforming...

A PostCSS plugin did not pass the `from` option to `postcss.parse`. This may cause imported assets to be incorrectly transformed. If you've recently added a PostCSS plugin that raised this warning, please contact the package author to fix the issue.
✓ 3027 modules transformed.
✗ Build failed in 6.85s
error during build:
Could not resolve "./pkg" from "../src-tauri/yaak-templates/index.ts"
file: /home/dallas/.cache/yay/yaak/src/yaak/src-tauri/yaak-templates/index.ts
    at getRollupError (file:///home/dallas/.cache/yay/yaak/src/yaak/node_modules/rollup/dist/es/shared/parseAst.js:401:41)
    at error (file:///home/dallas/.cache/yay/yaak/src/yaak/node_modules/rollup/dist/es/shared/parseAst.js:397:42)
    at ModuleLoader.handleInvalidResolvedId (file:///home/dallas/.cache/yay/yaak/src/yaak/node_modules/rollup/dist/es/shared/node-entry.js:21430:24)
    at file:///home/dallas/.cache/yay/yaak/src/yaak/node_modules/rollup/dist/es/shared/node-entry.js:21390:26
npm error Lifecycle script `build` failed with error:
npm error code 1
npm error path /home/dallas/.cache/yay/yaak/src/yaak/src-web
npm error workspace @yaakapp/app@1.0.0
npm error location /home/dallas/.cache/yay/yaak/src/yaak/src-web
npm error command failed
npm error command sh -c vite build
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: yaak-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
yaak - exit status 4

@kstolp Thanks for the hint! I'll look into it as soon as I can