Arch Linux User Repository

Make sure to fetch the signing keys from GitHub and import them before building:

curl -sS https://github.com/elkowar.gpg | gpg --import -i -
curl -sS https://github.com/web-flow.gpg | gpg --import -i -

The pinned imports do not fix the issue for me. gpg is throwing "no user ID" errors on the key.

gpg: key 4AEE18F83AFDEB23: no user ID
gpg: Total number processed: 1
 -> problem importing keys

This, after the imports, after pacman-key --refresh-keys.

For people getting a "failed to run gpg --recv-keys" error when updating, just run the 2 lines in the pinned comment. That fixed it for me.

It throws wrong gpg key. Cannot upgrade. Why though there's 'https://aur.archlinux.org/eww.git' instead of 'https://aur.archlinux.org/eww-wayland.git'?

gpg: error reading key: No public key
gpg: error reading key: No public key
gpg: error reading key: No public key

i tried to install but it says that this key has expired: pub rsa3072 2021-05-03 [SC] [expired: 2023-05-03] B558974128820CB473BD9807E321AD71B1D1F27F uid [ expired] Leon Kowarschick 5300871+elkowar@users.noreply.github.com

@eclairevoyant Thanks a lot for the fix!

@GiftShower eww-git already includes wayland support.

Anyway, fixed.

Doing the changes GiftShower suggested and removing the --frozen option from cargo build let me build the package correctly. See the corresponding PKGBUILD below.

# Maintainer: éclairevoyant
# Contributor: Will Elliott <troutcobbler at gmail dot com>

pkgbase=eww
pkgname=(eww-{wayland,x11})
pkgver=0.4.0
pkgrel=4
pkgdesc="Standalone widget system made in Rust"
url='https://github.com/elkowar/eww'
arch=(x86_64)
license=(MIT)
makedepends=(cargo-nightly git)
depends=(gtk3 gtk-layer-shell)
provides=(eww)
conflicts=(eww)
install=$pkgbase.install
source=("git+$url?signed#commit=14713f489c65e227972770f05d67bea52c9c342e")
b2sums=('SKIP')
validpgpkeys=(
    'B558974128820CB473BD9807E321AD71B1D1F27F' # Leon Kowarschick <5300871+elkowar@users.noreply.github.com>
    '94E8F34BCE4F4BA8ED9B29BD50E76B4711E4C3E4' # Leon Kowarschick <5300871+elkowar@users.noreply.github.com>
    '5DE3E0509C47EA3CF04A42D34AEE18F83AFDEB23' # GitHub (web-flow commit signing) <noreply@github.com>
)

prepare() {
    cd $pkgbase
    cargo update
    export RUSTUP_TOOLCHAIN=nightly
}

build() {
    cd $pkgbase

    export CARGO_TARGET_DIR=target_wayland
    cargo build --release --no-default-features --features=wayland

    export CARGO_TARGET_DIR=target_x11
    cargo build --release --no-default-features --features=x11
}

_pkg() {
    cd $pkgbase
    install -vDm644 LICENSE -t "$pkgdir/usr/share/licenses/$pkgname/"
    install -vd "$pkgdir/etc/xdg/$pkgbase/"
    cp -vr examples/eww-bar "$pkgdir/etc/xdg/$pkgbase/"
}

package_eww-wayland() {
    pkgdesc+=" (Wayland backend)"
    depends=(gtk3 gtk-layer-shell)
    _pkg
    install -vDm755 target_wayland/release/$pkgbase -t "$pkgdir/usr/bin/"
}

package_eww-x11() {
    pkgdesc+=" (X11 backend)"
    depends=(gtk3)
    _pkg
    install -vDm755 target_x11/release/$pkgbase -t "$pkgdir/usr/bin/"
}

By adding this line of code at prepare() section of PKGBUILD:

export RUSTUP_TOOLCHAIN=nightly

and changing source to latest commit, package have been successfully built and installed. Looks like above code is required to use latest rust toolchain. Also, the source had to be updated to latest commit in order to solve this error:

error[E0557]: feature has been removed

Edit: Looks like what I did was same as eww-git, but instead building with wayland enabled. If it should be built on current commit in PKGBUILD, I think either package version needs to be specified or use latest rust toolchain and patch outdated code.

@ror5chach My last time building something with rust is some time ago and I am a bit rusty. I remember vaguely how the targeting works. How to determine the up-to-date Value?

Edit1: I looked into the variable $CARCH and it is saying x86_64 which looks kind of right for me. But please teach me wrong. Based on the PKGBUILD I think the variable is set in line 10.

Edit2: After looking through documentation of cargo fetch I removed the --target flag and tried without. Got me similar error than @Madeleaan, but for cfg-expr v0.15.5 asking for rustc 1.70.0. looked further into cargo.lock: I found cfg-expr aswell as toml_edit neither of them specifying the version of rustc necessary. Based on naive approach I think the rustc compiler itself know this dependecies?

Edit3: cloned the repo directly, builded twice. First time following build intruction from documentation, second building with --locked and --frozen as in PKGBUILD. Both worked. Package after paru -S eww-wayland -fm vim and deleting `--target "$CARCH-unknown-linux-gnu" not.

To solve the issue mentioned by @Madeleaan, this line of code:

cargo fetch --locked --target "$CARCH-unknown-linux-gnu"

could be changed in the PKGBUILD (Line 28). Wherever $CARCH is set, it is out of date