Something’s off with pamac (and the derivatives of it).
Upon upgrade, I get a ‘Failed to synchronize AUR database’ message, and new packages from AUR aren’t shown. This happens on issuing pamac upgrade --aur --force-refresh.
It doesn’t show packages that need to be updated, instead it shows them with their old version and thinks everything is alright. librewolf-bin for example shows up with their v132 version whereas v133 is already available. Upon issunig a rebuild from the pamac GTK UI, it installs v133.
That’s because the PKGBUILD has been updated to v133. So, even though Manjaro’s AUR database still shows v132, rebuilding librewolf-bin will install the newer version that’s in the librewolf-bin PKGBUILD:
Hi there karolyi - I noticed this earlier this week and mentioned it in an update thread - where I suggested that (for now) it suits me better to use yay.
Failed to read AUR data from /var/lib/pacman/sync/packages-meta-ext-v1.json.gz : Error opening file /var/lib/pacman/sync/packages-meta-ext-v1.json.gz: No such file or directory
Not really relevant as Manjaro mirrors the AUR database on their own servers (which haven’t mirrored the AUR since last week). The file is there and is downloading - it just isn’t up-to-date:
pamac upgrade --aur --force-refresh
Preparing...
==== AUTHENTICATING FOR org.manjaro.pamac.commit ====
Authentication is required to install, update, or remove packages
Authenticating as: Scott (scotty)
Password:
==== AUTHENTICATION COMPLETE ====
Synchronizing package databases...
Refreshing core.db...
Refreshing extra.db...
Refreshing core.files...
Refreshing extra.files...
Refreshing AUR...
Nothing to do.
Transaction successfully finished.
Seems I rebooted the repo server at some point when a sync of the AUR db was happening. I removed the blocker file and reran the script. Should be fine now.