Grub doesn't detect garuda after upgrade

As far as the conflict is concerned, there are several ways to approach it, see this tutorial.
Basically both (the old version of) expect and whois own those files. Strange that the problem should have been fixed now in expect.
I think that rather than using the overwrites (which I too often suggest :slight_smile: ), you could simply temporarily remove one of the two (probably whois has less dependencies) and update.

2 Likes

Thanks, I added the Garuda repo and upgraded with sudo pacman -Syuu --overwrite '*' and everything worked fine.

Ahhh!
https://gitlab.com/garuda-linux/packages/stable-pkgbuilds/garuda-update/-/blob/master/update-helper-scripts#L15

That is… not at all how you’re supposed to do that :sweat_smile:

2 Likes

If only garuda-update were used, always, by everybody. What a fantastic tool!

2 Likes

I'll see if I can bump the expect version to the newest one maybe to avoid this conflict, even though this is literally the first time I've ever heard of this happening

2 Likes

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.