You are not logged in.
I get an error when searching AUR for updates. This only started occurring today.
[user@hostname ~]$ yay
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
there is nothing to do
:: Searching databases for updates...
:: Searching AUR for updates...
-> response decoding failed: invalid character '<' looking for beginning of value
Offline
Did you try another aur package helper?
I just tried with "paru" and it worked fine. I updated several aur packages.
Offline
I have the same issue. Started today as well.
I thought it was reflector, so I just checked everything, and it appears fine. Not sure what's afoot yet, but this is really the only directly relevant search hit.
*ETA: forgot to mention - pacman is unaffected or not throwing the same error.
Last edited by tixetsal (2022-02-04 23:32:29)
Offline
Exactly the same happens to me - also just started today - around 1 hour ago... Hope someone knows how to fix it, following (and maybe a lot more will join us soon, in dealing with this problem?)...
Offline
Have you read the latest comment on the yay AUR page?
https://aur.archlinux.org/packages/yay#comment-850524
https://github.com/Jguer/yay/issues/1682
Offline
You are not alone
Offline
Good, thought I was the only one; I've been pulling my hair out for ~15 minutes
EDIT: Humar's suggestion seems like a good fix in the meantime, paru worked like a charm. I had no luck with trizen though...
Last edited by doggle (2022-02-04 23:46:06)
Offline
paru works. Yay hasn't been updated since January 2, so whatever is causing this recent error is not in the yay or yay-bin package.
Offline
There are a lot of useful answers, however not direct instructions hot to fix the issue so I'll post pretty obvious thing:
0. Wait until issue will be fixed(as of now it is not)
1. Uninstall previous versions of yay
2. Install new version using instruction
Link to AUR page https://aur.archlinux.org/packages/yay
Thx to 2ManyDogs for the link:
To monitor progress of the fix use https://github.com/Jguer/yay/issues/1682
Last edited by xproger (2022-02-05 01:03:02)
Offline
I switched to paru for now, as I am having the same error with yay.
Offline
I'm not sure what all the speculation in the github issues is for. Test with curl and you can see the AUR RPC is not responding - this has nothing to do wth yay itself:
curl 'https://aur.archlinux.org/rpc/?v=5&type=search&arg=yay'
Replace "yay" at the end with whatever search term you want - at present it will not give any result at all regardless of the query.
EDIT: Ah, thanks for the below. My aur script is back up and running now. It looks like the Aurweb RPC wiki page needs an update.
Last edited by Trilby (2022-02-05 03:05:00)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
I'm not sure what all the speculation in the github issues is for. Test with curl and you can see the AUR RPC is not responding - this has nothing to do wth yay itself:
curl 'https://aur.archlinux.org/rpc/?v=5&type=search&arg=yay'
Replace "yay" at the end with whatever search term you want - at present it will not give any result at all regardless of the query.
The problem here is that the newly released aurweb is running on FastAPI, and trailing slashes are rewritten by default. I'm thinking we'll stop this rewrite from occurring, but, what's happening is that it's responding with a redirect, but your curl command is not following it.
Working:
curl -L 'https://aur.archlinux.org/rpc/?v=5&type=search&arg=yay'
Heads up in terms of yay; this issue has already been seen and they've completely removed the trailing slashes from RPC queries, in addition to fixing their endpoint from `/rpc.php` to `/rpc`. There is a PR up for it and it's already been approved by one maintainer, they'll get it merged in pretty soon.
https://github.com/Jguer/yay/pull/1685
Edit: Indeed, I have decided, we will support non-redirected trailing slashes for the RPC and only the RPC. Throughout the rest of the website, trailing slashes will still be redirected, but browsers already handle that implicitly. I'll be pushing a patch and it'll be deployed to the AUR on the morning of 02/05. This kind of breakage is unnecessary for people expecting unredirected responses as observed in the AUR previously.
Last edited by kevr (2022-02-05 03:07:36)
Kevin Morris <kevr@0cost.org>
Hangs out in #archlinux-aurweb. Loves the AUR.
Offline
paru works. Yay hasn't been updated since January 2, so whatever is causing this recent error is not in the yay or yay-bin package.
Yes, the issue is indeed present in both the yay and yay-bin packages. The cause of the recent error isn't because of something in yay, it's that the AUR itself updated to 6.0.0. The AUR API endpoint no longer uses PHP and it breaks yay. So yeah there is an error in yay, but it's not caused by yay, if that makes any sense.
Using yay-git currently will not fix it. There is a pull request that is hopefully going to be fast-tracked, and it indeed does fix the issue, as confirmed by multiple people (and I've confirmed it myself).
Unfortunately, right now to use yay you will need to use the yay-git package with a patch created from the PR added. If it's okay to do here, I can post my PKGBUILD and the patch (all you need to do is clone the yay-git repo, copy the PKGBUILD and patch and paste them into the yay-git directory, then run makepkg to build and then install.)
PKGBUILD (just copy this over the yay-git PKGBUILD, or delete the PKGBUILD and paste this into a new PKGBUILD file).
That's all you need.
Or, conversely, you can just run a one-liner to grab and run the little script I made to do it for you:
wget -O yayfix.sh https://gist.githubusercontent.com/gardotd426/f03cf227fede8a81b7c2352eb5e98c01/raw/20e10c8ca70f0719e2c66a86e4a4b6d57d5ccea1/yayfix.sh && chmod +x yayfix.sh && ./yayfix.sh
That'll literally do everything for you, and it takes about 8 seconds. You'll end up with a functioning yay.
Offline
We'll also be restoring `/php-fpm/?` endpoint support for a month: https://gitlab.archlinux.org/archlinux/ … 924ea63a42
Hitting the shores in probably 8 hours or so.
Last edited by kevr (2022-02-05 04:20:23)
Kevin Morris <kevr@0cost.org>
Hangs out in #archlinux-aurweb. Loves the AUR.
Offline
Same issue. yay not working. paru works fine.
Offline
Same issue. yay not working. paru works fine.
@sasha-ant as @kevr said, they're re-enabling the stuff that broke yay in the AUR API so just wait about 8 hours and you'll be good. If you can't wait, look at my comment above @kevr's and you can run that one liner to install a slightly modified yay-git package that will work.
Offline
As you can read here:
https://github.com/Jguer/yay/issues/168 … 1030511989
you just have to execute this command:
sudo sed -i 's:rpc.php:rpc////:g' /usr/bin/yay
which patches yay replacing rpc.php (which was causing the issue) with rpc///. Hope this helps!!
Offline
We'll also be restoring `/php-fpm/?` endpoint support for a month:
Since the output of https://aur.archlinux.org/rpc.php?v=5&t … arg=yay%20 and https://aur.archlinux.org/rpc?v=5&type=search&arg=yay is the same, why don't you just keep the /rpc.php (at least for a while longer*)?
It doesn't matter if it's not using PHP anymore, but if you remove it in a month and a user doesn't use a AUR helper during this month, that AUR helper might not work anymore.
Tho what you could do is to add a fake package to the response containing info that the AUR helper is using the unsupportet /rpc.php and that the user might want to report this to the maintainers of his AUR helper or to switch to another package helper.
*tho wasn't there a WC3 standard about resource locations that shouldn't change? Found at least https://www.w3.org/Provider/Style/URI during a quick search. Yes, in this case it's an API but still...
Last edited by Thomas Müller (2022-02-06 06:51:43)
Offline
kevr wrote:We'll also be restoring `/php-fpm/?` endpoint support for a month:
Since the output of https://aur.archlinux.org/rpc.php?v=5&t … arg=yay%20 and https://aur.archlinux.org/rpc?v=5&type=search&arg=yay is the same, why don't you just keep the /rpc.php (at least for a while longer)?
It doesn't matter if it's not using PHP anymore, but if you remove it in a month and a user doesn't use a AUR helper during this month, that AUR helper might not work anymore.
Tho what you could do is to add a fake package to the response containing info that the AUR helper is using the unsupportet /rpc.php and that the user might want to report this to the maintainers of his AUR helper or to switch to another package helper.
Any maintainer of an AUR helper that is not subscribed to aur-general shouldn't be writing an AUR helper in the first place. A month is more than enough time to adapt.
Offline
Okay, yeah. The wording could be different, indicating that the devs of the AUR helper might not follow the mailing list.
But my post was more about what happens when users don't use their AUR helper within that month.
So even if the AUR helper got an update, the user won't get it without using a different AUR helper or using makepkg.
Last edited by Thomas Müller (2022-02-06 07:04:21)
Offline
AUR helpers are not supported, and anyone using one should be more than capable of building an AUR package using makepkg.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
the user won't get it without ... using makepkg.
As it was when they initially installed the "helper". What's so hard about using three simple commands to update the helper?
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
This post from one year ago might be interesting. It explains the differences between yay and paru.
Offline
As you can read here:
https://github.com/Jguer/yay/issues/168 … 1030511989
you just have to execute this command:sudo sed -i 's:rpc.php:rpc////:g' /usr/bin/yay
which patches yay replacing rpc.php (which was causing the issue) with rpc///. Hope this helps!!
Can confirm this works just fine.
sam
Offline
If only these helpers would allow changing the AUR endpoint without requiring users to directly edit binaries...
Last edited by Alad (2022-02-16 16:18:44)
Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby
Offline