I know that many people like the chaotic-aur. However I am also sure I am not the only one who dislikes it. Disabling it should not be difficult, it is just commenting 2 lines:
The problem with this is that the chaotic `chaotic-keyring` are there and the Garuda repo needs them. Or at least that’s my understanding of this.
[garuda]
Include = /etc/pacman.d/chaotic-mirrorlist
The way I have been solving the issue of getting updated keyring is to uncomment the `chaotic-aur` upgrading the `chaotic-keyring` and only that and then commenting back to upgrade the rest.
Maybe I am doing something wrong, however I find no good reason not to have their own keyring or at least offer the chaotic-keyring in the Garuda repo.
I also haven’t found any documentation of how to opt-out of chaotic-aur from Garuda so maybe I am doing it wrong.
I’m not sure I fully understand the issue. Doesn’t chaotic-aur repo only matter if you install packages from that repo? If you don’t, then just ignore any packages that can be installed from there and install it from the AUR…?
Unfortunately, chaotic-aur is not an optional component of Garuda Linux. Some official Garuda Linux packages rely on certain packages from chaotic-aur existing on the system. In the future, a system update might break your system because one of these packages might be too far outdated.
My problem with chaotic-aur is that is not uncommon for it to break stuff and I just got tired of fixing them (Which almost always gets solved by disabling the chaotic-aur and reinstalling the package from AUR).
Some official Garuda Linux packages rely on certain packages from chaotic-aur existing on the system.
That would be a very good reason to mirror a copy of the needed packages inside the Garuda repo. At the end of the day, a repo should not assume another non-official repo is available.
In the future, a system update might break your system because one of these packages might be too far outdated.
This way my system has not broken and that’s more than what I can say about chaotic-aur.
The problem I have is that when I install something, if it is available in chaotic-aur, then it gets installed from there instead of using the AUR. So it’s not easy to ignore it.
Classic case of lib mismatch, which also occurs when you install from AUR initially and then update your system. Removing just postpones the issue to the next update.
We do have things in place to recompile.. but I yesterday noticed it seems to be not triggering since about a month. Need to investigate.
This however is only active for certain packages, and reporting the ones breaking would help getting this done for more of them.
The chaotic-aur is an official repo. It is run in part by the Garuda Linux team. It is NOT an optional repository. garuda-health even has a check that will make sure it is present.