Easy fix indeed. 
yay is working as usual now.
yay
[sudo] password for asmit:
:: Synchronizing package databases…
core is up to date
extra is up to date
community is up to date
multilib is up to date
endeavouros is up to date
:: Starting full system upgrade…
there is nothing to do
:: Searching databases for updates…
:: Searching AUR for updates…
there is nothing to do
yay konsave
1 aur/konsave 2.1.1-1 (+6 1.05) (Installed)
Save and apply your KDE Plasma customizations with just one command!
==> Packages to install (eg: 1 2 3, 1-3 or ^4)
4 Likes
7 Likes
Can confirm both EOS and Arch are working this morning. That being said, I would have interpreted that statement to mean 2/4 (yesterday) was the day the “routes are removed” and everything not patched will break. As I said though, yay is working on both machines as of this morning.
The dev left a comment that it was a typo 
This was meant to be **03/04**, apologies.
3 Likes
So, the solution to this was to do nothing.
I have applied this to real life and when things fail miserably around me, I will continue to do nothing.
Thanks Everybody!
8 Likes
Someone has to do something during the month or there will be problems again. 
The API has been changed to no longer support / RPC.php. There is a pull request to solve this problem, but support for this file has been restored for a month to allow time to update the project. At that time, it will be deleted. Please make sure you stay always update next month to avoid problems in the future.
Nice to see someone taking responsibility
https://lists.archlinux.org/pipermail/aur-general/2022-February/036787.html
2 Likes
I hear a lot about Someone. It’s an unbelievably common name, but I’ve never actually met a “Someone.”
I stand my ground on the nothing. It worked swimmingly yesterday.
3 Likes
Someone just did something 
. New version will be released tomorrow.
5 Likes
“Much ado about…” 
2 Likes
well the ado might have been about nothing but I panicked yesterday and used pamac to install paru 
I thought my system is borked. today yay was working swell.
thinking about what was actually the problem (AUR issue it seems) I wonder why paru was not affected. why was pamac not affected either… ?
1 Like
I switched to Ubuntu in the meantime as posted above. But since everything is ok I switched back to eos. 
My predictions were true, about 3-4 new user accounts and all new topics asking the same question. 
read people read…there is a search function in top of the forum.
Glad I did not update yay yesterday, I probably would have panicked.
2 Likes
I tried to update yesterday. Had a look around online, did NOT panic, watched TV instead. Here we are today and hey ho everything is fixed. Sometimes things don’t work for a while, but they get fixed. I can’t believe people were considering changing distros just because there was a little hiccup for 24 hours with a package manager! 
3 Likes
A lot can happen in 24.
3 Likes
Simply because they already used the url without .php in it…
Previously both of the following API calls were working:
https://aur.archlinux.org/rpc.php?v=5&type=search&arg=yay
https://aur.archlinux.org/rpc?v=5&type=search&arg=yay
Now Arch migrated from their PHP based version to their Python version (from 5.x to 6.0.0) where it was not possible to use the .php URL anymore (which makes sense). Later on they fixed it by making a routing from rpc.php/ to rpc/ (which they will remove again after one month’s grace period when all AUR helpers have been adapted to uses the “non .php” URL…)
1 Like
Well strangely the opposite happened, people were switching to eos while yay broke. Just strange the number of new accounts that pop up recently on the forum, almost like telegram. Seems there is a mass migration to eos. Totally off topic.
the make use of it article
4 Likes
I originally asked because, “check to see if it’s a known issue” is one of my troubleshooting steps. Other than that, I’ve been wanting to give paru a look anyway and this was a pretty good excuse
1 Like