AUR not working on new install since 2024-10-10 update

On a brand new Manjaro installation, the AUR doesn’t work with pamac-manager (once enabled in the options).

Log:

pamac-manager[989]: Failed to read AUR data from /var/lib/pacman/sync/packages-meta-ext-v1.json.gz : Error when opening file /var/lib/pacman/sync/packages-meta-ext-v1.json.gz : No such file or directory

Updating the packages database through the menu doesn’t fix it.

aur.manjaro.org/packages-meta-ext-v1.json.gz is online though.

Update: although this topic was locked and a post was force marked as a solution, it’s actually a known bug:
Searching AUR points to unexpected db · Issue #1 · manjaro/pamac-cli · GitHub.
Sorry everyone for the loss of time as my post was mistakenly taken for a support request.

pamac update --aur --force-refresh

That said - custom built packages using AUR may cause instability when used on stable branch.

Be warned.

1 Like

Thanks, but this is a new install, so it should work without any further command.
And will it auto update after that like it used to?

It may still be useful; to refresh the databases as @linux-aarhus has indicated, especially if an update (via pamac) has not yet been performed.

pamac update -a --force-refresh

I just fixed this (old) issue myself @Marsa :

Nuke the folder (I have an alias for that: rmdir! = sudo rm -vdrRR - it’s the heavy hitter with no confirmation).

❯ sudo rm -vdrRR /var/lib/pacman/sync/download-lYHlyC
❯ pamac upgrade --force-refresh --aur --devel

It bugged me, because yay was fine, and pamac was a few days behind…

A few days later it’s still working well, just did another update today without issue.

2 Likes

It surely fixes it, at least temporarily.
But this bug happens on a fresh install and after installing updates with pamac-manager and it shouldn’t.

But does the database keeps getting updated?
I did it a month ago on my install, and the modified date of /var/tmp/pamac/dbs/sync/packages-meta-ext-v1.json.gz is 2024-11-11.

Though http://aur.manjaro.org/packages-meta-ext-v1.json.gz returns

Date: Wed, 04 Dec 2024 14:08:14 GMT
Last-Modified: Wed, 04 Dec 2024 14:00:04 GMT

So a few minutes ago.

Yes, after nuking and refreshing it was all bang up to date… pamac mirrored yay.

❯ curl -sI https://aur.manjaro.org/packages-meta-ext-v1.json.gz
HTTP/2 200 
date: Wed, 04 Dec 2024 14:15:24 GMT
content-type: application/gzip
content-length: 11037831
last-modified: Wed, 04 Dec 2024 14:12:04 GMT

Downloading the AUR database is not part of a fresh installation and having to download it is not a bug.

AUR should not be enabled on stable branch.

2 Likes

I mean, does it stay updated or do we have to run that command every time?

It’s disabled by default, but there’s an option to enable it.
Before 2024-10-10, it worked without running a command before every AUR install.

True - even so you may need to use the refresh database option in the GUI.

There has been changes to the location of the database - moved from /var/tmp/pamac to same location as other databases.

As mentioned, updating the packages database through the menu doesn’t fix it.

Ok, so maybe the location hasn’t been updated everywhere in the code?

The code is writing the metadata the correct location and it works as expected on my systems.

Workaround to refresh the database has been explained and qualified several times. Continued banter on the topic seems ineffective.

Therefore closing.

1 Like