Running on 18.04, when trying
sudo do-release-upgrade -d I get following error :
authenticate 'focal.tar.gz' against 'focal.tar.gz.gpg' Authentication failed Authenticating the upgrade failed. There may be a problem with the network or with the server.
I've seen numerous posts akgin to reinstall
sudo apt-get install --reinstall ubuntu-keyring
Which I did, with no result.
I manually downloaded focal.tar.gz and focal.tar.gz.gpg from http://mirrors.linode.com/ubuntu/dists/focal-proposed/main/dist-upgrader-all/20.04.18/
I did run a gpg check
gpg --receive-keys 871920D1991BC93C gpg --receive-keys 3B4FE6ACC0B21F32 gpg --verify focal.tar.gz.gpg focal.tar.gz
Looks succesful (with warnings, but at least it matches)
gpg: Signature made mer. 08 avril 2020 19:38:12 CEST gpg: using RSA key 3B4FE6ACC0B21F32 gpg: Good signature from "Ubuntu Archive Automatic Signing Key (2012) <email@example.com>" [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 790B C727 7767 219C 42C8 6F93 3B4F E6AC C0B2 1F32 gpg: Signature made mer. 08 avril 2020 19:38:12 CEST gpg: using RSA key 871920D1991BC93C gpg: Good signature from "Ubuntu Archive Automatic Signing Key (2018) <firstname.lastname@example.org>" [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: F6EC B376 2474 EDA9 D21B 7022 8719 20D1 991B C93C
No idea what I could try to make the upgrade accept the file, and the process to go on.
I do not wish to follow this suggestion : change manually the sources definition, https://stackoverflow.com/questions/62388015/authenticating-the-upgrade-failed-there-may-be-a-problem-with-the-network-or-wi
I'm running this ubuntu machine as a 'maintainability test for any user', so my challenge here is not to tweak around. For that, my main pc runs arch ;)
So, I'm looking for a way as easy to explain and reproduce as possible to solve this.
Thank you !
I could manually tinker with apt-key
gpg --receive-keys 3B4FE6ACC0B21F32 gpg --receive-keys 871920D1991BC93C gpg --export 790BC7277767219C42C86F933B4FE6ACC0B21F32 > 1.gpg gpg --export F6ECB3762474EDA9D21B7022871920D1991BC93C > 2.gpg sudo apt-key add 1.gpg sudo apt-key add 2.gpg
but that's not something I should do .... is it ? And even so, it fails later on with
Updating repository information Hit http://www-ftp.lip6.fr/pub/linux/distributions/Ubuntu/archive focal InRelease Hit http://www-ftp.lip6.fr/pub/linux/distributions/Ubuntu/archive focal-security InRelease Hit http://archive.canonical.com/ubuntu focal InRelease Fetched 0 B in 0s (0 B/s) (appstreamcli:1444): GLib-CRITICAL **: 19:08:37.593: g_variant_builder_end: assertion '!GVSB(builder)->uniform_item_types || GVSB(builder)->prev_item_type != NULL || g_variant_type_is_definite (GVSB(builder)->type)' failed (appstreamcli:1444): GLib-CRITICAL **: 19:08:37.593: g_variant_new_variant: assertion 'value != NULL' failed (appstreamcli:1444): GLib-ERROR **: 19:08:37.594: g_variant_new_parsed: 11-13:invalid GVariant format string Trace/breakpoint trap (core dumped)
I sure can wait for 20.04.1 release but... that's a weird behaviour.
Looks like repo info is not found see
Fetched 0 B in 0s (0 B/s) but when I manually browse the repo, things are there.