Paru/yay update issue

Since a few hours I see an error while trying to update my system:

15# paru -Syyu
:: Synchronizing package databases...
 core                              131,1 KiB  2,91 MiB/s 00:00 [----------------------------------] 100%
 extra                            1599,6 KiB  15,3 MiB/s 00:00 [----------------------------------] 100%
 community                           5,5 MiB  22,4 MiB/s 00:00 [----------------------------------] 100%
 multilib                          150,4 KiB  11,3 MiB/s 00:00 [----------------------------------] 100%
 endeavouros                        17,3 KiB   960 KiB/s 00:00 [----------------------------------] 100%
 liquorix                            2,6 KiB  0,00   B/s 00:00 [----------------------------------] 100%
 kernel-lts                         19,5 KiB  0,00   B/s 00:00 [----------------------------------] 100%
 kernel-lts.sig                    584,0   B  0,00   B/s 00:00 [----------------------------------] 100%
:: Starting full system upgrade...
warning: binutils: ignoring package upgrade (2.35.1-1 => 2.36.1-2)
 there is nothing to do
:: Looking for AUR upgrades
:: Looking for devel upgrades
error: error decoding response body: expected value at line 1 column 1

This happens also with yay. I tried it on two different computers. Any idea what this is about?

The AUR server is currently unavailable.

Edit: … and, it’s back.

Edit 2: Caused by Pamac, https://gitlab.manjaro.org/applications/pamac/-/issues/1017

2 Likes

Yes, it was the AUR and it is up again.

By the way, during this incident I found an interesting webpage:

https://status.archlinux.org/

2 Likes

Wow. Apparently Pamac started sending partial strings - with each and every every keypress - to find “package suggestions”…

 20:50:20 <Foxboron> grazzolini: ohhh, omg. They hit the AUR for suggestions!
 20:50:29 <Foxboron> partial strings get sent to the AUR!
 20:50:55 <Foxboron> that is hillarious

Some nice programming, there: integrated DDoS. :man_facepalming::rofl:

5 Likes

I love how random stuff is getting posted into the issue like it is a forum post…

3 Likes