Arch Linux User Repository

Appreciate the work, but wouldn't it have made more sense to hold off updating the package to the 23.04 release, seeing as Arch is still on Gnome 43? There's been some shuffling in the new control center of Gnome 44, so 23.04 "bugs out" with Gnome 43.

@Gio sounds like a problem with your AUR helper. Can you build manually by cloning and running makepkg?

With your AUR helper, I'd recommend clearing its cache, or asking it to cleanbuild the package, if that's an option.

Hi. When attempting to update from v22.04.1-1 to v22.04.3.1-1 , it shows:

Checking yaru-icon-theme dependencies... Resolving dependencies... Checking inter-conflicts...

Building yaru... ==> ERROR: PKGBUILD does not exist.

I'm getting an error when trying to install the dependencies:

error: libsass: signature from "Jerome Leclanche <jerome@leclan.ch>" is unknown trust
:: File /var/cache/pacman/pkg/libsass-3.6.5-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: sassc: signature from "Jerome Leclanche <jerome@leclan.ch>" is unknown trust
:: File /var/cache/pacman/pkg/sassc-3.6.2-3-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] 
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.
error installing repo packages

Should I fill a bug report here? -> https://archlinux.org/packages/community/x86_64/sassc/

Edit: Removing some keys and running sudo pacman-key --populate archlinux fixed it.

@Remedan you're using eCryptFS? It has a 143 character filename limit.

If you scroll down/click onto the next page of comments, another user had the same issue when this package was using a git commit as the source - the filenames all had a full git hash in them which made them very long.

That's no longer the case, but there are nontheless filenames bumping up against the limit.

Not a whole lot this PKGBUILD can do about that unless there's some flags we can pass to whatever component of the build process makes those horrendous filenames, telling it to do something else. Anybody know which build tool is responsible for the .cache___aurutils___sync___yaru___src___ type filenames with slashes replaced with underscores, storing a full path in a single filename?

The underlying issue is that that tool and eCryptFS are not playing nice together, since one breaks the assumptions of the other.

I'm using aurutils to manager AUR packages. It builds packages in ~/.cache/aurutils/sync. This results in the following error:

ninja: error: stat(gnome-shell/src/___home___remedan___.cache___aurutils___sync___yaru___src___yaru-21.10.1___gnome-shell___src___gnome-shell-sass___widgets____network-dialog.scss): File name too long

A workaround that worked for me is to move ~/.cache/aurutils/sync/yaru under a shorter path and then symlink it back.

@JoveYu the mixed theme has been removed due to poor toolkit support:

https://github.com/ubuntu/yaru/pull/2922

The next version of Ubuntu won't have it either.

this package contains two theme yarn and yarn-dark,is there a theme using light content and dark title? just like ubuntu default.

With Yaru tagging 21.10.1, This package is now back to official releases instead of a git commit.

@coxackie this package is for stable releases generally - it was only pointed at a git commit since no stable release supported gnome 40 yet, but that should be a once off.

Unless it's actually broken on Arch due to other packages here updating ahead of Yaru's release cycle (is that the case with gtk4?) I think its best to stick with official releases.

Those who want goodies can use yaru-git :)