[tde-users] Re: Stupid key question

said Dan Youngquist via tde-users: | I'm seeing both keyrings there on packages.debian.org. You have to | manually download from there and install, per the instructions on that | page. That may not be clear if you're not accustomed to the process. Problem is . . . code/ dep@dep-desktop:~$ sudo apt install debian-keyring Reading package lists... Done Building dependency tree Reading state information... Done debian-keyring is already the newest version (2020.03.24). 0 upgraded, 0 newly installed, 0 to remove and 80 not upgraded. /code Same thing with keyring archive. But . . . code/ W: GPG error: http://deb.debian.org/debian bookworm-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131 E: The repository 'http://deb.debian.org/debian bookworm-updates InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://deb.debian.org/debian bookwormmain Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://deb.debian.org/debian-security bookwormsecurity Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. /code Trying to dig out of it. -- dep Pictures: http://www.ipernity.com/doc/depscribe/album Column: https://ofb.biz/author/dep/