Ok, this post definitely belongs in newbie lol. I’m still learning how to deal with these scenarios, as it’s not a common one I cross paths with.
I was trying to install libheif on my Arch system to view .HEIC images, and couldn’t remember how I got it working on my other EOS machine. I installed it via yay -S libheif and that was not enough to get it working, so I tried to remove it before trying other methods and I ran into:
[user@Arch ~]$ yay -R libheif
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing libheif breaks dependency 'libheif' required by gd
:: removing libheif breaks dependency 'libheif' required by gimp
-> exit status 1
I tried to mark the dependencies as explicitly installed before attempting to remove the AUR again, but that also didn’t work, as there were other chained dependencies.
There seems to be some misunderstanding regarding the functioning of yay.
yay is not only an AUR helper targeting packages in AUR. It is also a pacman wrapper meaning it is capable of operating on the packages from Arch’s repos as well.
So, when you run yay -S X, if X is from Arch’s repo, it will be installed from there.
That one flew over my head. I didn’t pay attention to the -S in the yay command, in fact that’s the first time I’ve added -S to yay, but that makes sense now. Thanks for pointing that out.
That being said, I’m still not sure how to get the HEIC images to load.