filo
6 November 2022 14:56
6
With rolling releases these things happen, and even more with AUR packages, where in the end you are the maintainerā¦
You look smart, some interesting reading as final takeover
The normal reasons
Generally, there will be two reasons why an AUR package has āstopped workingā:
A repo package was updated and the AUR package was built against an older (and incompatible) version of that repo package;
The AUR package was updated and requires a repo package version not present on your system.
The solutions to these:
Rebuild the AUR package.
Update your system fully.
The other reasons
The other, less frequent reasons, are
The package file (PKGBUILD) has an issue and neeā¦
https://wiki.archlinux.org/title/Pacman/Rosetta
(to learn searching eg to which package a file belongs to)
But none of these could have avoided the problem in this caseā¦
3 Likes