On 4/13/20 12:45 PM, Dennis Clarke wrote:> > After installing Jessie ( 8.7 ) on a G5 I think tr yto update > /etc/apt/sources.list :
You will likely run into problems updating from Debian Jessie to unstable as you are skipping more than one release. Also, you are installing a 32-bit userland on a 64-bit capable machine. I'm not sure why people have such a hard time installing one of the older Yaboot images I created: > https://cdimage.debian.org/cdimage/ports/10.0/ Just skip the part where the debian-installer wants to download and install extra software. That won't work as the keyring shipped on the installation image is too old for the release file on the server. The moment you will have rebooted the machine, you can install the updated keyring and update your installation > However : > > enceladus# > enceladus# apt-get update > Get:1 http://deb.debian.org sid InRelease [55.3 kB] > Get:2 http://deb.debian.org sid InRelease [146 kB] > Ign http://deb.debian.org sid InRelease > Ign http://deb.debian.org sid InRelease > Get:3 http://deb.debian.org unreleased InRelease [56.6 kB] > Ign http://deb.debian.org unreleased InRelease > Get:4 http://deb.debian.org sid/main powerpc Packages [21.2 MB] > Get:5 http://deb.debian.org sid/main Sources [8604 kB] > Get:6 http://deb.debian.org unreleased/main Sources [64 B] > Get:7 http://deb.debian.org unreleased/main powerpc Packages [3008 B] > Ign http://deb.debian.org sid/main Translation-en > Ign http://deb.debian.org unreleased/main Translation-en > Fetched 30.1 MB in 21s (1406 kB/s) > Reading package lists... Done > W: GPG error: http://deb.debian.org sid InRelease: The following signatures > couldn't be verified because the public key is not available: NO_PUBKEY > 84C573CD4E1AFD6C > W: GPG error: http://deb.debian.org sid InRelease: The following signatures > couldn't be verified because the public key is not available: NO_PUBKEY > 04EE7237B7D453EC NO_PUBKEY 648ACFD622F3D138 > W: GPG error: http://deb.debian.org unreleased InRelease: The following > signatures couldn't be verified because the public key is not available: > NO_PUBKEY 84C573CD4E1AFD6C > > > So this is a mystery. # gpg --keyserver keyserver.ubuntu.com --recv-keys 04EE7237B7D453EC # gpg --export --armor 04EE7237B7D453EC | apt-key add - # apt update # apt upgrade # apt dist-upgrade or: # wget http://ftp.ports.debian.org/debian-ports/pool/main/d/debian-ports-archive-keyring/debian-ports-archive-keyring_2019.11.05_all.deb # dpkg -i debian-ports-archive-keyring_2019.11.05_all.deb > I see https://ftp-master.debian.org/keys.html but there are no obvious docs > to update > these GPG keys with apt-key adv --keyserver keyring.debian.org --recv-keys > ????totalmystery??? Wrong place to look for documentation. Right one: https://wiki.debian.org/SecureApt#How_to_find_and_add_a_key > A bit of help would be awesome. > > Anyone that knows the magic incantations? I don't consider reading documentation "magic" :P. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
