SparkyLinux Forums

Installation & Upgrade => System upgrading => Topic started by: dennie75 on July 26, 2023, 08:52:34 PM

Title: Old custom recover
Post by: dennie75 on July 26, 2023, 08:52:34 PM
Translated by google translate


I have been using Sparky for a while but came across an old custom iso that I would like to use again but am having trouble updating. k wanted Po-Tolo 6.7. Me error message looks like this:



live@live:~$ sudo apt update
Get:1 http://deb.debian.org/debian testing InRelease [168 kB]
Ign:2 https://sparkylinux.org/repo core InRelease                             
Get:3 http://www.deb-multimedia.org testing InRelease [16.5 kB]               
Get:4 http://deb.debian.org/debian-security testing-security/updates InRelease [48.0 kB]
Ign:5 https://sparkylinux.org/repo testing InRelease                           
Ign:6 https://sparkylinux.org/repo unstable InRelease
Err:7 https://sparkylinux.org/repo core Release
  Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate.  Could not handshake: Error in the certificate verification. [IP: 185.249.225.163 443]
Err:8 https://sparkylinux.org/repo testing Release
  Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate.  Could not handshake: Error in the certificate verification. [IP: 185.249.225.163 443]
Err:1 http://deb.debian.org/debian testing InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131
Err:9 https://sparkylinux.org/repo unstable Release
  Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate.  Could not handshake: Error in the certificate verification. [IP: 185.249.225.163 443]
Get:10 http://www.deb-multimedia.org testing/main amd64 Packages [128 kB]
Err:4 http://deb.debian.org/debian-security testing-security/updates InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 54404762BBB6E853 NO_PUBKEY BDE6D2B9216EC7A8
Get:11 http://www.deb-multimedia.org testing/main Translation-en [82.6 kB]
Get:12 http://www.deb-multimedia.org testing/non-free amd64 Packages [1,508 B]
Get:13 http://www.deb-multimedia.org testing/non-free Translation-en [1,376 B]
Reading package lists... Done               
E: The repository 'https://sparkylinux.org/repo core 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 'https://sparkylinux.org/repo testing 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.
W: GPG error: http://deb.debian.org/debian testing 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 testing 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 'https://sparkylinux.org/repo unstable 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.
W: GPG error: http://deb.debian.org/debian-security testing-security/updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 54404762BBB6E853 NO_PUBKEY BDE6D2B9216EC7A8
E: The repository 'http://deb.debian.org/debian-security testing-security/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.
live@live:~$ lsb_release -a
No LSB modules are available.
Distributor ID:   Sparky
Description:   SparkyLinux 6 (Po-Tolo)
Release:   6
Codename:   n/a
live@live:~$


If I change the sources list after 6.7 it doesn't work either. anyone have an idea?

I have a lot of work put into this cinnamon custom


Title: Re: Old custom recover
Post by: pavroo on July 26, 2023, 09:28:48 PM
Change Debian repo from 'testing' to 'bullseye' and Sparky repo from 'testing' to 'potolo' and try again.
Title: Re: Old custom recover
Post by: dennie75 on July 26, 2023, 10:54:18 PM
Distributor ID:   Sparky
Description:   SparkyLinux 6 (Po-Tolo)
Release:   6
Codename:   bullseye

live@live:~$ uname -a

everything else is working well now

A donation is coming for appreciation thanks  Pavroo