Package Details: espanso-wayland-git 2.4.0.r8.g3c4a281a-1

Git Clone URL: https://aur.archlinux.org/espanso-git.git (read-only, click to copy)
Package Base: espanso-git
Description: Cross-platform Text Expander written in Rust (built for Wayland)
Upstream URL: https://espanso.org
Keywords: expand expander rust shortcut text wayland xorg
Licenses: GPL-3.0-or-later
Conflicts: espanso
Provides: espanso
Submitter: Scrumplex
Maintainer: txtsd
Last Packager: txtsd
Votes: 7
Popularity: 0.023307
First Submitted: 2019-10-08 17:40 (UTC)
Last Updated: 2026-08-25 07:23 (UTC)

Required by (1)

Sources (1)

Latest Comments

1 2 Next › Last »

txtsd commented on 2026-08-25 07:22 (UTC)

@quinnri Pushed an update! Thanks for letting me know!

quinnri commented on 2026-08-25 04:56 (UTC)

This failed to build for me, but I got it to build by changing "icon.png" to "espanso.png" at lines 111 and 138 of the PKGBUILD.

Commit f07bd04 from 11 days ago I think is what made this necessary: https://github.com/espanso/espanso/commit/f07bd0472963f8b357b7d27e7f6f21c675ccc090

dasarne commented on 2025-05-19 07:15 (UTC)

If you see the following error when trying to build espanso from the AUR:

error: failed to parse lock file at: .../Cargo.lock
Caused by: lock file version 4 was found, but this version of Cargo does not understand this lock file, perhaps Cargo needs to be updated?

It means your version of Rust and Cargo is too old to understand the lock file format used by espanso. To fix this, update Rust and Cargo to the latest stable version using rustup:

sudo pacman -S rustup
rustup update stable

After updating, try building espanso again. This should resolve the issue.

Alternatively, if you are building from source, you can delete the existing Cargo.lock file in the espanso source directory and let Cargo regenerate it:

rm path/to/espanso/Cargo.lock

Then rebuild the project.

shawny commented on 2025-02-08 15:33 (UTC)

@txtsd Thank you. Confirmed.

txtsd commented on 2025-02-08 13:45 (UTC)

I pushed an update. Circumstantially because of the hash it won't ask to update again.

shawny commented on 2025-02-07 07:48 (UTC)

@txtsd Any progress on fixing the package? I can confirm the below problem on two machines.

shawny commented on 2025-02-05 16:34 (UTC)

There appears to be something broken with this package. Using the yay helper, this package will show as out of date and reinstall on every run of yay, following a successful prior build and install.

 yay
:: Synchronizing package databases...
 core is up to date
 extra is up to date
 multilib is up to date
:: Searching AUR for updates...
:: Searching databases for updates...
:: 1 package to upgrade/install.
1  aur/espanso-wayland-git  2.2.2.r0.g5d5d0d4d-1 -> 2.2.2.r0.g42a6c95a-1
==> Packages to exclude: (eg: "1 2 3", "1-3", "^4" or repo name)
 -> Excluding packages may cause partial upgrades and break systems

Schlaefer commented on 2025-01-26 19:59 (UTC) (edited on 2025-01-27 17:21 (UTC) by Schlaefer)

Upstream has tagged 2.2.2 in the dev branch, which is currently the new r0, but the commit hash results in a "lower version" than the "2.2.2.r0..." PKGBUILD in the AUR.

xircon commented on 2025-01-25 12:45 (UTC)

Something wrong with PKGBUILD, the package is constantly rebuilding.

txtsd commented on 2023-11-08 06:29 (UTC)

@hans Try building it with a default /etc/makepkg.conf. It built fine for me in a chroot using pkgctl build -c from the devtools package.

1 2 Next › Last »