Pamac fails to synchronise due unacceptable TLS certificate

First thought was “oh no, not again” but on closer inspection, the certificate in question has not expired, and is still current for some months yet. I can also visit the offending address with my browser no worries, its just pamac that thinks its unacceptable.

Is this a pamac bug, or is there some reason this certificate is unacceptable to pamac but not firefox? How do I troubleshoot this?

$ pamac upgrade
Preparing...
Synchronizing package databases...
https://aur.manjaro.org/packages-meta-ext-v1.json.gz: Unacceptable TLS certificate
Failed to synchronize AUR database
Cloning jellyfin build files...
Generating jellyfin-web information...
==> ERROR: PKGBUILD does not exist.
Error: Failed to prepare transaction: Failed to generate jellyfin-web information

Pamac and pacman both report all normal packages are just up to date, so its just a handful of AUR packages this affects for me. Per the tag, this is on the unstable branch.

Hello @Blu3wolf :wink:

Had the same problem… a second run solved it. :man_shrugging:

Sadly no such luck at my end, including through a couple restarts.

The problem is maybe your location and the CDN behind it.

Maybe curl offers a hint?

curl --verbose https://aur.manjaro.org/packages-meta-ext-v1.json.gz >/dev/null

Curl reckons its fine.

As far as location, Ive tried this both locally (without VPN) and with a VPN elsewhere, with the same result. Ill try the curl without the vpn also.

So the top link is with the VPN, the bottom one, without the VPN.

pamac upgrade --force-refresh

:question:

The verbose output is pretty normal.

I think the force refresh fixed it!

$ pamac upgrade --force-refresh
Preparing...
Synchronizing package databases...
Refreshing core.db...                                                                                                                                                                                               
Refreshing extra.db...                                                                                                                                                                                              
Refreshing community.db...                                                                                                                                                                                          
Refreshing multilib.db...                                                                                                                                                                                           
Refreshing core.files...                                                                                                                                                                                            
Refreshing extra.files...                                                                                                                                                                                           
Refreshing community.files...                                                                                                                                                                                       
Refreshing multilib.files...                                                                                                                                                                                        
Refreshing AUR...                                                                                                                                                                                                   
Cloning jellyfin build files...                                                                                                                                                                                     
Generating jellyfin-web information...
==> ERROR: PKGBUILD does not exist.
Error: Failed to prepare transaction: Failed to generate jellyfin-web information

Not sure why the PKGBUILD isnt getting found, but we solved the unacceptable TLS certificate error, so. QED.

Thanks very much for the help. I feel a little silly, as I thought Id already done a force-refresh, but I guess not. Troubleshooting much appreciated.

1 Like

Had the issue too today, did a force-refresh as suggested, nothing changed. Waited a few hours, tried again, failed again. Then, like @megavolt, tried for a second time and it finished normally. Not getting any PKGBUILD errors like you are, though.

Tried to run it again (third time) just to check and the error is back. No clue what’s going on here and not sure if it’s on my end if it sometimes works?

Try regenerating your mirror-pool:

sudo pacman-mirrors -f 5 && sudo pacman -Syyu

If that doesn’t work, please start a new thread providing the output of above command.

Nah… there is only one URL to the AUR database. :wink:

Good point. My bad.

:bowing_man:

I suspect the PKGBUILD error is an unrelated bug in Pamac. Off topic, but its discussed here: Pamac can’t find PKGBUILD while yay can (#1259) · Issues · Applications / pamac · GitLab

That package is build from a base, so its one PKGBUILD for multiple packages, and that seems to confuse Pamac. It was happy enough to install it in the first place, but not to update it. Workaround is straightforward, git clone and makepkg -si as per normal.

And, the issue is back again. Im starting to wonder whether it was truly fixed, or if it is simply intermittent for some odd reason. For that reason Ive removed the “solution” marking.

1 Like