It’s not a problem of pacman, but of updating the system. This is the reason, why I chose this category.
When trying to update the system, I get the following message.
yay -Syu
:: Paketdatenbanken werden synchronisiert …
core ist aktuell
extra ist aktuell
community ist aktuell
multilib ist aktuell
endeavouros ist aktuell
:: Vollständige Systemaktualisierung wird gestartet …
Es gibt nichts zu tun
:: Durchsuche Datenbanken für Updates...
:: Durchsuche AUR für Updates...
-> response decoding failed: invalid character '<' looking for beginning of value
response decoding failed: invalid character '<' looking for beginning of value
response decoding failed: invalid character '<' looking for beginning of value
I already updated the mirrorlist, which didn’t change anything. Community repositories went smoothly. This is the reason why there are no updates available for the official repositories.
Maybe someone has an idea, where to dig.
There are a number of other posts about this - the problem is a change in the AUR presentation (apparently) which affect yay. There exist already ‘fixes’ for yay, with more on the way shortly. You could just wait (briefly) for that to show up in your updates list - or apply on the short-term fixes.
In the meantime, everything except AUR packages (which, on EnOS, includes yay) can be updated as usualy by direct use of pacman - that is "sudo pacman -Syu, and leave the AUR side until the fixes reach you. A search here in the forums will tell you much more if you want to know…
Thanks for the quick response. Community repositories, what you called everything except AUR, updated fine using yay. I know, how pacman works, but thanks for the hint.
It obviously does not only affect yay, but other pacman wrappers too.
I just heard that the change to the AUR will be reverted temporarily, and delayed for a month before being re-applied. So yay will work again without intervention in a few hours…
Was there any notice of this change in advance (Arch News)? Might have been a good idea, if something does not work as expected. Problems are not unusual, when making changes like this. Not all users have a closer look at all news sources or mailing lists. So many will be caught off guard.
AUR helpers are not supported by Arch Linux. You should become familiar with the manual build process in order to be prepared to troubleshoot problems.
The AUR is not meant to be used with the help of other software, so such issues were not taken into account originally. The (to Arch) normal method (download from the AUR, and makepkg -si) was not affected by the change. I guess they got enough feedback from actual Archers to change their mind.
The fix for yay was the blanking out of an option (could be done with a sed command) - so it wasn’t particularly world-shaking (really) except for the spewing of an error message in an unexpected place! At least a visit here usually clears things up quickly…
Perhaps the lead dev learned something along the way from when he implemented yay. Or, he didn’t bother with adding the alternate access to the info that changed when he wrote paru… I sure don’t know which. I have rarely seen an easier fix than blanking out 3 letters in one place in the code!
Of course - even that should not be needed now that the AUR change has been reverted and delayed for a month for the ‘helpers’ to get modified…
I guess they got enough feedback from actual Archers to change their mind.