Manjaro Unstable 32.1.0 Cinnamon DE
If the AUR update is enabled in the settings, this error message appears when updating the system:
Message: 09:46:48.887: aur_plugin.vala:317: downloading AUR data
Failed to read AUR data from /var/tmp/pamac/packages-meta-ext-v1.json.gz : Error opening file /var/tmp/pamac/packages-meta-ext-v1.json.gz: No such file or directory
https://aur.manjaro.org/packages-meta-ext-v1.json.gz: Socket I/O timed out
Firefox can find the above compressed file in the above link.
But I had several repair attempts, but the error message remained.
If I disable (turn off) the AUR updater, the system update runs without problems.
Can it be fixed somehow?
Thanks for the answer!
Replacing the mirrors (best United States) and updating the database did not help.
Nor that I copied the compressed file downloaded with Firefox to its location in the path.
But I’ve been trying to fix it one way or another for more than a month.
Essentially, Manjaro has no control over packages installed from the AUR; or how long you might have to wait for an update. Manjaro’s official updates are expected to come from the usual Arch/Manjaro repos. Frankly, if you must use an application from the AUR, you’re generally on your own.
This is a falsehood. Using the AUR in combination with the Unstable branch leaves the door open for all kinds of unsupported configurations; all kinds of trouble; in my opinion. If you want Arch, use Arch.
I disagree. Manjaro unstable is pretty stable and if a lot of AUR packages shall be used it’s in general a good idea to change to the Unstable branch as this is often more in line with the configs of the AUR packages. The number of cases there are issues is pretty limited an can be usually easily fixed when timeshift snaps have been created upfront.
I suppose it would depend on the application, and the availability of AUR publishers to correct issues. Timeshift certainly can be a useful tool to overcome unexpected issues when no immediate fix is available; I agree.
Use yay instead of pamac, yay connects directly to Arch AUR repo instead of using Manjaro repo, I suffered from this bug for months and didn’t find any solution because the problem surely lies in Manjaro repo configuration and connectivity.
And one comment.
I started a Manjaro 23.0.1 installation flashdive.
I saved the unstable branch, enabled the AUR and its update.
I updated the database and ran:
command. Neither this nor the database update gave an error message.
Unlike the installed system.
Thank you so much for everyone’s comments!
I think I’ll wait for the next Manjaro Cinnamon snapshot - I went to a file called the package list of the installed system and I’m deleting this “damaged” (?) system.
After installing the new snapshot, I will also list its packages. I use the difference between the two lists as the previous (damaged) system
install the applications I installed on the new system with a suitable command.
The necessary commands are there.
I hope it will work like this - if not, then you can manually install the applications one by one.
No, this is a falsehood.
You can use the AUR with Manjaro - and you will get qualitatively and quantitatively less issues from that combination than you would with say the Stable branch, if only for the fact of having newer packages (‘closer to Arch’) … one can also take a look at any of the numerous posts from Manjaro Stable users finding that out for themselves on the forum.
Sure Arch is more Arch period.
But thats not the dichotomy being set up here - in the question of “Does Manjaro work better with the AUR while using the Unstable Branch?” The answer is “yes”.
To your own added contrivance of “Does the combination of Manjaro Unstable Branch and the AUR in particular open the door for unsupported configurations and trouble?” The answer is “no”, at least in comparison to using the AUR on some other Manjaro branch.
All warnings and caveats about the Arch User Repository still withstanding, including it being unsupported and the users responsibility.