Is it really necessary to put the specific pacman version in the dependency list? It might be not totally clean, but can't you just expect that it is built with the current versions from the official repo? Then yay would as usual upgrade from the offical repos first, build the AUR stuff afterwards and everything would be fine.
Also if we are really strict, if yay-bin is compiled against v5.2 (libalpm.so.12) it will also not run with 5.1.x. So it should also depend on pacman>=5.2, or not? If you fix this that workaround would also not work.
Pinned Comments
jguer commented on 2024-03-16 08:06 (UTC)
This will happen if you upgrade pacman and yay separately If you have this error you need to manually recompile yay
jguer commented on 2019-04-16 14:08 (UTC)
I cannot delete the spam comments appearing regularly in this page, which has also led me to disable notifications from here. I remind that the best way to receive support or report a problem is through the Upstream URL.