Is dead for good?

Hi. I just tried to update my system and got:

error: failed retrieving file 'mesa-nonfree.db' from : Failed to connect to port 443 after 11 ms: Couldn't connect to server

I hope it’ll soon get up but if was down for good, where would I find that information? I see nothing here in Notices section.

Works for me. It is just you:

It’s live now for me as well… although pacman complains about the key being unknown:

error: mesa-nonfree: key "86412CE3A5C73C6CDD2F5B11B728DB23B92CB01B" is unknown
:: Import PGP key 86412CE3A5C73C6CDD2F5B11B728DB23B92CB01B? [Y/n] 
error: key "86412CE3A5C73C6CDD2F5B11B728DB23B92CB01B" could not be imported
error: failed to synchronize all databases (unexpected error)
 -> error refreshing databases - exit status 1

and pacman-key complains about invalid packet:

sudo pacman-key --recv-keys B728DB23B92CB01B && \
  sudo pacman-key --lsign-key B728DB23B92CB01B
gpg: [don't know]: invalid packet (ctb=00)
gpg: keydb_get_keyblock failed: Value not found
gpg: [don't know]: invalid packet (ctb=00)
gpg: /etc/pacman.d/gnupg/pubring.gpg: copy to '/etc/pacman.d/gnupg/pubring.gpg.tmp' failed: Invalid packet
gpg: error writing keyring '/etc/pacman.d/gnupg/pubring.gpg': Invalid packet
gpg: error reading '[stream]': Invalid packet
gpg: Total number processed: 0
==> ERROR: Remote key not fetched correctly from keyserver.

(pasted for easier googling)

Turns out trying to update while was down somehow broke my pubring.gpg but fortunately there was a backup available so all I had to do to fix this issue was:

cd /etc/pacman.d/gnupg
sudo cp  pubring.gpg~ pubring.gpg

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.