Arch Linux User Repository

You're right, in the upstream thumbnailer is provided by glycin which is disabled here. I enabled the thumbnailer now.

Why is the thumbnailer not built by default?

I'm trying to keep this as close as possible to the upstream packages (with the obvious difference of being compiled without glycin), so I would not want to diverge in any meaningful way such as changing dependencies that could potentially create further complications going forward. Same applies to the librsvg-noglycin and it's PKGBUILD.

librsvg-noglycin should probably be a required dependency, because this package is half broken without it otherwise (I mean in practice, in use).

Building packages with makepkg is the default/basic way of building an AUR package. AUR helpers like pamac, yay, pacaur and similar are just third party made programs to automate that process (including the updates). Why pamac has an issue with librsvg-noglycin I'm not sure, from the message it looks to have something to do with the way pamac is checking dependencies, but I'm not sure what can I do in the package itself to fix it.

@karabaja4 Thank you! I'm really no expert in building AUR-Package locally by hand. Had to add cargo-c, vala first. After that I could build you package. Now I have librsvg-noglycin installed successfully and working GTK-based Apps again.

Still the question: Is it the right way to maintain -glycon spinoffs of standard packages.

I'm not sure about pamac, but you can always build manually: download the snapshot ("Download snapshot") on the top right on this page, extract the file, type "makepkg" in the extracted directory and then install with pacman -U <package>.pkg.tar.zst

@karabaja4: I'm using pamac-manager as a frontend to build librsvg-noglycin from the AUR-Repo (is there any other way to do it?). But before it starts building it does a conflict scan and breaks:

Resolving dependencies... Checking for internal conflicts... Operation could not be prepared successfully: Cannot satisfy dependencies: - Removing librsvg violates dependency 'librsvg-2.so=2-64' required by ffmpeg Operation aborted.

So the new package doesn't get build or installed.

That's interesting, and is unexpected as librsvg-noglycin package provides and conflicts with librsvg, so it should function as a drop-in replacement. Since it works on Arch for me the only thing I can think of is that those distros have ffmpeg that depends on a specific version of librsvg.

I'm going to investigate using a Manjaro VM when I can, if you can please do the same and post the findings here.

EDIT: I just tried to build and install gdk-pixbuf2-noglycin and librsvg-noglycin packages on a fresh Manjaro KDE instance on a VM, where ffmpeg is also installed by default:

https://avacyn.radiance.hr/stuff/librsvg-noglycin.txt

Unfortunately I couldn't reproduce the issue you are describing.

@karabaja4: Thanks for your support.

Tried librsvg-noglycin on a Manjaro Distro. It wants to uninstall lbsrsvg but ffmpeg depends on it, so installation fails on this machine.

That's all very frustrating. Maybe I should wait for icaclient being compatible with the new gdk-pixbuf2 version, got the same problem on another machine running Suse-Linux.