Arch Linux User Repository

@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 :)

@chrisjbillington there seems to be a lot of movement in the master branch of yaru lately with gtk4 commits (last one I see is 1dece88568a336b8cf82883ac6843e1113d4c416). Maybe you could update the PKGBUILD to get the latest goodies?

Why does "yaru-gtk-theme" depend on gtk-engine-murrine and, by implication, gtk2? I just realized that yaru-gtk-theme pulls in Gtk2, even though nothing else actually needs gtk2 on my system.

Could gtk-engine-murrine perhaps be turned into an optdepends?

Have applied the workaround to the PKGBUILD for now, since eCryptFS is not uncommon.

eCryptFS can only store filenames of up to 143 characters

@drakkan

touch: cannot touch 'aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa': File name too long
144

@chrisjbillington Yes, $HOME is encrypted with eCryptFS I'll try the temp fix. EDIT: pkgBuild fix worked. Thanks.-:)

Hi,

please try a script like this:

num=1
while [ true ]
do
   if ! touch $(printf "%${num}s"  | tr ' ' 'a')
   then
       echo $num
       break
   fi
   ((num++))
done

to understand your file name limit. Are you using something like eCryptfs?

@vlatkoB no idea why that's happening. You could shorten the directory like this if you like as a temporary fix until this package starts shipping an official release again (which will have a shorter name owing to not containing a commit hash):

diff --git a/PKGBUILD b/PKGBUILD
index c55a3b1..7170eb4 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -24,7 +24,8 @@ source=("https://github.com/ubuntu/yaru/archive/${_commit}.tar.gz")
 sha256sums=('e2a400527451e33abb44d96b6878514482d008355639add6ab30d6e9b2dd70f3')

 build() {
-  arch-meson $pkgbase-$_commit build
+  mv $pkgbase-$_commit $pkgbase
+  arch-meson $pkgbase build
   meson configure build -Dubuntu-unity=true
   ninja -C build
 }

@chrisjbillington Using ext4

$ df -TH
Filesystem            Type        Size  Used Avail Use% Mounted on
/dev/nvme0n1p3        ext4        388G  326G   46G  88% /home

What filesystem are you using @vlatkoB? 161 characters shouldn't be too much to ask for a filepath on any system I know about.

Obviously the fact that the filepath now contains a commit hash is pushing something over a limit, but I would not expect limits this short (I certainly don't see the problem here on an ext4 filesystem).