Check "Notify of new comments" at https://aur.archlinux.org/packages/yaourt/ , so next time you don't need to ask a stupid question about an official unsupported tool anymore, at an AUR unrelated mailing list, since the yaourt comments nowadays are misused as a forum, it's impossible to miss even the slightest issue and workarounds [1]. However, again yaourt isn't out-of-date and there's no need to rebuild it. As Eli already pointed out, you need to rebuild package-query{,-git} [2], to do this download the tarball and use makepkg. [1] zanny commented on 2016-02-29 21:02 New package-query fixes everything, crisis averted. Thank you to all the hardworking volunteers for pushing a release so quickly! Skunnyk commented on 2016-02-29 20:45 Please update to package-query 1.8 (just released: https://aur.archlinux.org/packages/package-query). It should fix all rpc v5 problems. A new yaourt version will follow in a few days. Ralf_Mardorf commented on 2016-02-29 13:08 If something like this happens, I build temporarily from git, but keep the package name without the "-git" extension, instead I add an "r" to the output of git describe. [rocketmouse@archlinux package-query]$ pacman -Q package-query package-query 1.7.r172.g4d856ec-1 An official release update of package-query should replace the temporarily build package. Skunnyk commented on 2016-02-29 12:08 Yes, the "old" aur rpc api is broken since this morning (new api included in aurweb 4.2.0, see https://lists.archlinux.org/pipermail/aur-dev/2016-February/003993.html ) Fortunately, package-query-git already support the new api v5. We need to make an official release of yaourt / package-query to fix theses problems. viq commented on 2016-02-29 09:35 gourdacaptain: pacaur seems to manage fine right now gourdcaptain commented on 2016-02-29 07:06 Similar issue. Does anyone know if this is also applying for other AUR helpers? EDIT: Installing package-query-git fixed the issue for now. josephgbr commented on 2016-02-29 06:13 Me too. It looks like package-query is unable to get package list for some reason. Baemir commented on 2016-02-29 05:37 yay complete breakage zanny commented on 2016-02-29 05:28 Yea I'm not seeing any AUR packages. Fairly sudden, I'm wondering if something on the AUR server is down that yaourt uses. diogobaeder commented on 2016-02-29 05:07 Am I the only one getting "target not found" for any AUR package, with yaourt? [2] [rocketmouse@archlinux ~]$ date;yaourt -Syua Tue Mar 1 08:55:57 CET 2016 [snip] aur/package-query 1.7.r172.g4d856ec-1 -> 1.8-1 [snip]

On Monday, 29 February 2016 22:10:00 IST Rafael Fontenelle wrote:

yaourt 1.7 is (or should be) compatible with package-query 1.8. A new version of yaourt will follow in a few days :)

Thank you. I guess I will be using pacaur for a few days then. -- Cheers Jayesh Badwaik

On Monday, 29 February 2016 19:54:54 IST Marshall Neill wrote:

This is what I fail to understand; How did this get out of testing when obviously something is broke?

AUR does not promise any stability, unlike core and extra packages. -- Cheers Jayesh Badwaik

No I am not, but, yaourt crashes with package-query issue. Now, am I wrong for asking. After all yaourt is used by most everyone and it would seem to me that a simple yaourt -S alsi, a simple program with no real dependencies, would install and not crash. package-query seems to be the issue here, right? Or am I off base? On 02/29/2016 08:03 PM, Eli Schwartz wrote:

On 02/29/2016 08:54 PM, Marshall Neill wrote:

...

This is what I fail to understand; How did this get out of testing when obviously something is broke? Are you seriously suggesting it is the Arch Linux AUR developers who are responsible for making sure every single AUR helper in existence supports newer versions of aurweb, before updating the AUR backend?

OK, fill me in. What are they using then. I see a lot of posts about yaourt not working, so I guess I assumed wrongly. On 02/29/2016 08:19 PM, Jason Ryan wrote:

On 29/02/16 at 08:17pm, Marshall Neill wrote:

...

After all yaourt is used by most everyone…

Patently false.

/J

On 02/29/2016 09:25 PM, Marshall Neill wrote:

OK, fill me in. What are they using then. I see a lot of posts about yaourt not working, so I guess I assumed wrongly.

Some people don't use the AUR at all. Those who do have a number of AUR helpers to consider, assuming they don't simply use makepkg directly. You can see a big list of them here: https://wiki.archlinux.org/index.php/AUR_helpers "most everyone" would imply a(n overwhelming) majority of people, as opposed to simply being one of if not the most popular choices -- which leaves open the very realistic possibility that a majority of people are actually split among the other options. ... As a matter of fact I am a happy yaourt(-git) user. But I would never post about yaourt not working... because those are mainly people who DON'T KNOW WHAT THEY ARE DOING. -- Eli Schwartz

OK then, you have my apologies for going off the handle and assuming something that I shouldn't have. Guess I learned to eat some humble pie today. Again, my apologies. On 02/29/2016 08:23 PM, Eli Schwartz wrote:

On 02/29/2016 09:17 PM, Marshall Neill wrote:

...

No I am not, but, yaourt crashes with package-query issue. Now, am I wrong for asking. After all yaourt is used by most everyone and it would seem to me that a simple yaourt -S alsi, a simple program with no real dependencies, would install and not crash.

package-query seems to be the issue here, right? Or am I off base? In that case you are *certainly* wrong. And I should have gone with my original response, which was "You clearly have absolutely no idea in the slightest what you are talking about".

Because AUR packages don't have a "testing".

Also, yaourt and package-query both worked fine, until an update to aurweb "broke" package-query. So how can you possibly think any sort of testing would have averted that?

(Let us not get into your claim about most everyone using yaourt.)