Arch Linux User Repository

Adopted and updated. 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 -

Hey man. eww-wayland-git has been deleted from AUR.

@eclairevoyant, bug #739 is fixed. Can we get just eww-git? I can confirm that eww binary works on bspwm and hyprland.

Another option that worked for me is to simply uninstall the nightly toolchain which maybe be more of a shotgun surgery approach but is a lot more convenient than switching to a different aur helper (I use yay)

I ran: rustup toolchain uninstall nightly

PS: This will result in the toolchain being downloaded again when the package is being built

I missed that export in PKGBUILD, it should be enough.
I still can't think of any other reasons build keeps failing, and to me it looked like stable toolchain kept being used (in chroot with nothing, but base-devel and PKGBUILD dependencies), since the moment I pull rust-nightly as dependency instead, everything is fine.
If there actually is an issue it's probably not with this package, so forget the part about cargo-nightly being wrong. Sorry for bothering you.

@nx-que No no, you are not nitpicking, and I appreciate proper attention to packaging quality, but you are simply wrong. I built this package using extra/rustup, that is the actually the point of rustup to be able to install arbitrary versions of rust since it is the rust version manager. In fact it is the only provide of cargo-nightly in the repos, why would I build some random AUR package instead?

Perhaps there is some way to specify nightly toolchain from PKGBUILD instead

Yes there is, read the PKGBUILD as well as https://wiki.archlinux.org/title/Rust_package_guidelines#Depends

I noticed someone else having issues with this inconsistency in replies below.

No one else is having such inconsistency when following this process: https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot

It builds in chroot, but not when official repo rustup package is used (one of valid cargo-nightly providers, which satisifies current make dependency).
It does indeed build when rust-nightly-bin is used, but makepkg can't differentiate between those and will accept either. I know it may sound nitpicking, but this may lead to package not bulding, depending on what you pull first (does in my case, so I was using updated version with cargo-nightly).
From my limited rust knowledge, rustup allows for specifying any toolchain, which includes, but is not limited to nightly, therefore the incosistency. Perhaps there is some way to specify nightly toolchain from PKGBUILD instead, but it doesn't seem to be doing that right now.
Feel free to disregard all of this if it's too much of a hassle, I was just pinching a solution to this, since I noticed someone else having issues with this inconsistency in replies below.

@nx-que your comment doesn't make sense. the package conforms to Rust packaging guidelines and builds fine in a clean chroot as per https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot.

Package may not build in chroot, since cargo-nightly is provided by rustup(-git) as well.
Consider using rust-nightly(-bin) explicitly as make dependency instead of it.

@eclairevoyant Thanks for clearing that up, I was mistaken clean build with a clean chroot. Using a clean chroot with paru indeed worked, though I've had to disable ccache in makepkg.conf.

@NoXPhasma yay does not have an option for clean chroots, only aurutils and paru do. Even then, they don't use it by default.

If you didn't set up a local repository and chroot manually but try to use aurutils or paru, then you are not using a clean chroot. see https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot