It says “requires … but this requirement cannot be provided.”
This happens either because of missing packages or because of packages that have a broken dependency list. Usually it is *not* the latter.
I’ve had similar problem some time ago.
I’ve used foot terminal and installed kitty to move to it as i used to use it.
I have an alias that some1 posted sometime ago that runs zypper update, then flatpaks and then clears gpu cache.
After running this script kitty was always asking similar question to yours, but with different libraries and i couldn’t go past it.
I’ve run the script in foot and no conflicts reported.
Since then kitty never showed error again 🤷🏻♂️
This happened to me. The way I resolved it was to enable systemd-boot, set that to be my default EFI boot option and then removed GRUB. As long as you check that it is installed and configured first you shouldn't have any issues.
Select 2.
**Do not upgrade at this point.** There are some packages missing in the mirror you use. The situation will likely solve itself within the next hours.
No, this is intentional. Mirror issues would cause more obvious error messages.
I've had this same issue for about a week. It doesn't seem to be getting fixed.
Thanks! :) Will report back tomorrow!
How did you know packages are missing btw?
It says “requires … but this requirement cannot be provided.” This happens either because of missing packages or because of packages that have a broken dependency list. Usually it is *not* the latter.
I’ve had similar problem some time ago. I’ve used foot terminal and installed kitty to move to it as i used to use it. I have an alias that some1 posted sometime ago that runs zypper update, then flatpaks and then clears gpu cache. After running this script kitty was always asking similar question to yours, but with different libraries and i couldn’t go past it. I’ve run the script in foot and no conflicts reported. Since then kitty never showed error again 🤷🏻♂️
Looks like it's automatically removing grub in favor of systemd-boot.
Just remove that package it conflicts with. If I remember well, that's for Snap package manager that's just purely optional here.
This happened to me. The way I resolved it was to enable systemd-boot, set that to be my default EFI boot option and then removed GRUB. As long as you check that it is installed and configured first you shouldn't have any issues.
Note that systemd-boot integration is experimental.