This issue has now been fixed. The cause was a faulty regex on the chaotic-aur router level that existed there for months now, but only actually became an issue ever since r2 launched for Garuda. Should be all good now, give it a go!
This issue has now been fixed. The cause was a faulty regex on the chaotic-aur router level that existed there for months now, but only actually became an issue ever since r2 launched for Garuda. Should be all good now, give it a go!