+- Linux Lite Forums (https://www.freecinema2022.gq/forums)
+-- Forum: Software - Support (https://www.freecinema2022.gq/forums/forumdisplay.php?fid=5)
+--- Forum: Other (https://www.freecinema2022.gq/forums/forumdisplay.php?fid=20)
+--- Thread: Help NEWBIE Screwed up repositories (/showthread.php?tid=9129)
Help NEWBIE Screwed up repositories - Dan Brown - 04-26-2024
Hi There
I have been distro hopping for a long time but finally settled on LL.
I keep using timeshift to make restore points but I think I screwed up my Repositories
and need to fix it or start from scratch again. I have googled and searched but never
certain I won't make it worse. I am hoping for a quick fix.
Here's the problem when I try and run updates
===========================
Install Updates Error log
===========================
Install Updates could not fetch the package cache information lists.
Go to https://www.freecinema2022.gq/forums/ and paste the log below into the Software - Support - Updates section for assistance.
============ Log ===========
Hit:1 http://repo.linuxliteos.com/linuxlite fluorite InRelease
Err:1 http://repo.linuxliteos.com/linuxlite fluorite InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 22AAEA0A86A02625
Get:2 http://archive.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Get:3 http://archive.canonical.com jammy InRelease [11.4 kB]
Err:3 http://archive.canonical.com jammy InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Hit:4 https://ppa.launchpadcontent.net/alessandro-strada/ppa/ubuntu jammy InRelease
Err:4 https://ppa.launchpadcontent.net/alessandro-strada/ppa/ubuntu jammy InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY AD5F235DF639B041
Hit:5 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy InRelease
Err:5 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9BDB3D89CE49EC21
Err:2 http://archive.ubuntu.com/ubuntu jammy-security InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Hit:6 https://ppa.launchpadcontent.net/teejee2008/foss/ubuntu jammy InRelease
Get:7 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]
Err:6 https://ppa.launchpadcontent.net/teejee2008/foss/ubuntu jammy InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B5B116B72D0F61F0
Hit:8 https://ppa.launchpadcontent.net/tomtomtom/conky-manager/ubuntu jammy InRelease
Err:8 https://ppa.launchpadcontent.net/tomtomtom/conky-manager/ubuntu jammy InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B90E9186F0E836FB
Err:7 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Get:9 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB]
Err:9 http://archive.ubuntu.com/ubuntu jammy InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Get:10 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [109 kB]
Err:10 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
Reading package lists...
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://repo.linuxliteos.com/linuxlite fluorite InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 22AAEA0A86A02625
W: GPG error: http://archive.canonical.com jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://archive.canonical.com jammy InRelease' is not signed.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://ppa.launchpadcontent.net/alessandro-strada/ppa/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY AD5F235DF639B041
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9BDB3D89CE49EC21
W: GPG error: http://archive.ubuntu.com/ubuntu jammy-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://archive.ubuntu.com/ubuntu jammy-security InRelease' is not signed.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://ppa.launchpadcontent.net/teejee2008/foss/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B5B116B72D0F61F0
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://ppa.launchpadcontent.net/tomtomtom/conky-manager/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B90E9186F0E836FB
W: GPG error: http://archive.ubuntu.com/ubuntu jammy-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://archive.ubuntu.com/ubuntu jammy-updates InRelease' is not signed.
W: GPG error: http://archive.ubuntu.com/ubuntu jammy InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://archive.ubuntu.com/ubuntu jammy InRelease' is not signed.
W: GPG error: http://archive.ubuntu.com/ubuntu jammy-backports InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 871920D1991BC93C
E: The repository 'http://archive.ubuntu.com/ubuntu jammy-backports InRelease' is not signed.
Lenovo M73 Thinkcentre mini - i5-4690K Intel CPU - Onboard Intel GPU - 256Gb SSD - 16Gb DDR3 RAM
Re: Help NEWBIE Screwed up repositories - stevef - 04-26-2024
There's an inbuilt utility which is a quick fix attempt but it may not be able to undone what you've done.
It is rated with caution as it involves changing system files.
Click Menu and begin typing 'Lite Tweaks' into the search box.
When you see 'Lite Tweaks' offered, click on it.
In the window that opens scroll down to find and check 'Package System Repair' then click begin and follow the instructions.
If that doesn't work, we could try to debug, but starting from scratch may be quickest.
Help NEWBIE Screwed up repositories - Dan Brown - 04-27-2024
Hi Steve
Thanks for responding.
I did try that, but It didn't work. I don't know if TimeShift willl do it as I kept snapshots everytime I got something working.
My Needs are simple
1. Keepass2 via Google Drive or Samba for my Passwords
2. Samba to my Windows server
3. TOR Browser (Testing for Customers Dodgy links etc)
4. Firefox in Sync with Windows system
5. Teamviewer 12 (Later)
6. Thunderbird (Later)
I still have to keep my Windows 11 box for customer support and Server 2019 for Customer backups,
so I got the Separate Lenovo to start working on Linux and learning.
I am going to try Timeshift hoping it's like Windows system Restore. I do have a Clonezilla Image
to fall back on as well.
DB
Re: Help NEWBIE Screwed up repositories - stevef - 04-27-2024
Timeshift (with default settings) will include the system files which update/grade uses.
So if you have a snapshot from when the repositories were still good deploying it should restore the relevant files as it will revert your system to the point the snapshot was taken.