Updating PureOS amber

Software PureOS
1

I am trying to update and get all these certificate errors. See below

~$ sudo apt update
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian buster InRelease
Ign:3 https://repo.pureos.net/pureos byzantium InRelease
Ign:4 https://repo.pureos.net/pureos byzantium-security InRelease
Ign:5 https://repo.pureos.net/pureos byzantium-updates InRelease
Ign:6 https://repo.pureos.net/pureos amber InRelease
Ign:7 https://repo.pureos.net/pureos amber-security InRelease
Ign:8 https://repo.pureos.net/pureos amber-updates InRelease
Err:9 https://repo.pureos.net/pureos byzantium Release
Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the certificate verification. [IP: 138.201.228.45 443]
Err:10 https://repo.pureos.net/pureos byzantium-security Release
Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the certificate verification. [IP: 138.201.228.45 443]
Err:11 https://repo.pureos.net/pureos byzantium-updates Release
Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the certificate verification. [IP: 138.201.228.45 443]
Err:12 https://repo.pureos.net/pureos amber Release
Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the certificate verification. [IP: 138.201.228.45 443]
Err:13 https://repo.pureos.net/pureos amber-security Release
Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the certificate verification. [IP: 138.201.228.45 443]
Err:14 https://repo.pureos.net/pureos amber-updates Release
Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the certificate verification. [IP: 138.201.228.45 443]
Reading package lists… Done
E: The repository ‘https://repo.pureos.net/pureos byzantium 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://repo.pureos.net/pureos byzantium-security 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://repo.pureos.net/pureos byzantium-updates 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://repo.pureos.net/pureos amber Release’ no longer has 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://repo.pureos.net/pureos amber-security Release’ no longer has 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://repo.pureos.net/pureos amber-updates Release’ no longer has 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.

What is going on?

2
3

I read the thread and got the update done by changing in my source list the https to http.

But I am sure that this is not the normal.

The strange thing is that I have another MacBook with amber installed and it does the updates as supposed to.

But this MacBook on which I just installed amber today will not update with https. Even when I update it with http only, reboot, than change the source list back to https, I get the certificate error again.
What is going on?

1 Like
4

Certificate verification issues have popped up recently from a root certificate with the common name DST Root CA that expired recently. That CA was used by Let’s Encrypt to cross-sign intermediate certificates. We use Let’s Encrypt certificates in PureOS repos.

The workaround is to move to http to do an update to get updated CA certificates. This is a normal approach and does little to reduce security because all PureOS packages are signed with a PureOS key so you know they’re authentic. Moving to http may decrease your confidentiality but you can switch back to https after the update.

1 Like
5

I recommend upgrading to PureOS 10 Byzantium when you get an opportunity;

https://tracker.pureos.net/w/recommendations/upgrade_from_amber_to_byzantium./

1 Like
6

If you’re recommending this generally for users now, you may want to edit this language in your post:

Byzantium is the bleeding edge of PureOS and is not really the type of operating system that you use when you want to ensure that your machine is always ‘production’ ready. Things may break. Caveat Emptor.

That has so far made me cautious of upgrading my Librem 13 v4 from amber to byzantium. Is it safe to say that I should go for it now?

1 Like
7

Yes. PureOS 10 (Byzantium) has gone through a couple years of stabilization and is installed by default on our hardware. It is safe to upgrade from Amber to Byzantium.

1 Like
8

Jeremiah, you recommended upgrading to PureOS10.
And I did, because you said so.

Dwaff and Quarnero helped me to get this obnoxious wifi to go and we succeeded.

But now my printer will not print anymore and I cannot play a DVD anymore.

Do I have to revert back to PureOS 9 ???

9

Best to keep that in its topic: Printer not printing