I notice !110 was disabled. Was this because of people using the Yaru gnome shell theme? Yaru used to be buggy with !110, but has updated to accommodate !110, and in fact now is buggy without !110:
https://github.com/ubuntu/yaru/issues/1466
So if disabling !110 by default was only for the sake of Yaru users, it should now be re-enabled. The Yaru release requiring !110 is 19.10.1, released 11 days ago.
Edit: Actually, the Yaru AUR package maintainer has decided to hold back Yaru to 19.04.3 and not package the newer upstream version for now, presumably until gnome shell 3.34 is in Arch. So probably leave !110 disabled for now after all.
Pinned Comments
saltyming commented on 2021-11-18 14:16 (UTC) (edited on 2024-03-24 05:25 (UTC) by saltyming)
If you are getting errors like
fatal: bad revision '73e8cf32'
while building this package, refer to PKGBUILD and see which patches caused this. Then, go to the related URLs, replace the commit hashes. If there are conflicts, comment out the patches.Please notify me in comment section if this happens.
Note that a
debug
option is disabled in this package.To enable the check() process, set an env:
_enable_check=y
To disable building the docs package, set an env:
_disable_docs=y
If the building process is getting failed on
check()
likegnome-shell/src/st/meson.build:195:2: ERROR: Dependency "libmutter-test-11" not found, tried pkgconfig and cmake
then you might want to do one of these:
0) Unset an env:
_enable_check=y
1) Rebuild
mutter-performance
package with_enable_check=y
env.And try again.
The optional performance patches are by default enabled.
A package for mutter (compositor) performance patches: https://aur.archlinux.org/packages/mutter-performance/
Terence commented on 2019-08-02 16:35 (UTC) (edited on 2019-08-02 19:09 (UTC) by Terence)
Warning: Before making a report of something broken, make sure it is not caused by an extension or a custom theme!