As @irvinewade kindly recommended in his post, please remove following:
sudo rm /etc/apt/sources.list.d/*
sudo apt update
Optionally:
sudo rm /etc/apt/sources.list.save*
sudo apt update
1 Like
The previous posts basically covered it but
Yes. You need to edit the file (or delete the file) as root. For many commands, by prefixing the command with sudo you will execute the command as root.
I think you’ve understood the issue. This can be a problem when giving instructions in a forum. The person who gave you those instructions enclosed the text in quote marks but did not intend the quote marks themselves to go into the file.
If Brave didn’t ever get installed, due to the erroneous quote marks, then just delete the file as root, do all the operating system upgrades, and then attempt to install Brave after the upgrade.
2 Likes
Just a remark:
https://pureos.net/download/
Has instructions on upgrade, but apparently you’re still on green?
Not so sure this will go smoothly.
As @irvinewade said, first remove the brave file.
Then backup your full home diectory, e.g.
cp -a /home/poorme /media/myexternaldrive
Then, drop to a real (non-graphical) terminal, e.g. with Ctrl+Alt+F3 and attempt the upgrade. If it goes wrong or you rather want a clean install, follow normal installation procedure after that.
Finally, restore your home. Best way to do that is, again, on a real terminal, copy back your backup, then rename the current profile and swap in the backup. Reboot.
sudo cp -a /media/mydrive/poorme /home/poorme.temp
sudo mv /home/poorme /home/poorme.old
sudo mv /home/poorme.temp /home/poorme
ls -lah /home/ # check if poorme is owned by poorme. If not, use chown poorme:poorme
reboot
Warning. Didn’t test the above 
Thanks everyone!
I’ve successfully removed the problematic files with sudo rm, but sudo apt update resulted in this:
~$ sudo apt update
Ign:1 https://repo.puri.sm/pureos amber InRelease
Err:2 https://repo.puri.sm/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]
Ign:3 https://repo.pureos.net/pureos amber InRelease
Err:4 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]
Reading package lists… Done
E: The repository ‘https://repo.puri.sm/pureos amber 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’ 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.
Sorry, @irvinewade, I don’t know how to quote my text with backquotes. 
Can you please advise?
It seems I should now go with @Dwaff’s suggestion…
@Caliga, thanks for your helpful guidance in this similar direction. I just want to make sure that I understand your instructions before I proceed, so…
I should plug in an external drive, then replace all instances of “poorme” with my own user name, and “myexternaldrive” with the name of the external drive, yes?
I appreciate your added warning. I’ll be the guinea pig, haha! 
1 Like
Good move! Therefore reminding here to:
The following is approximately the documentation for the features supported by the forum software in the subcategory of Markdown. https://commonmark.org/help/
Look at the last two features (those involving the backquote character).
The forum software is complicated though because it allows you to mix and match features from Markdown, features from BBCode and features from HTML (and with generally incomplete documentation).
More comprehensive discussion: https://meta.discourse.org/t/post-format-reference-documentation/19197
1 Like
Yes. If you open your external drive in the file browser and then press Ctrl+L (location) it should show you the exact path in the address bar.
Oh, and of course I assumed all your important data is in your home directory. That’s usually the case.
1 Like
Thanks, @Quarnero!
I’ve read through that post a few times, but am not quite sure if I understand how it pertains to my situation. Isn’t the issue in my case an expired certificate and not a missing gpg or apt-key error?
I checked /etc/apt/trusted.gpg.d and a file named pureos-archive-keyring.gpg is definitely in there.
When I ran apt list pureos-archive-keyring, it said
Listing... Done pureos-archive-keyring/now 2016.09 all [installed,local]
So, is 2016.09 the date of its creation? I.e., is it old and in need of replacement by following your instructions to sudo apt reinstall pureos-archive-keyring, etc?
Or should I instead try the temporarily “switch https to http” workaround that @irvinewade and @Dwaff both suggested?
Or simply jump to a clean install of Byzantium as per the advising of @Dwaff, @Gavaudan and @Caliga?
1 Like
Yes, you need replacement for sure (sorry for not making this clear, the one from 2016 is just some obsolete key, not useful any more):
Grateful for the clarification, @Quarnero! I really appreciate you taking the time and effort to walk me through this. 
I just tried this…
sudo dpkg --install pureos-archive-keyring_2021.11.0_all.deb
but got this…
dpkg: error: cannot access archive 'pureos-archive-keyring_2021.11.0_all.deb': No such file or directory
Was I supposed to run all of the additional commands? I.e., downloading the related package, and:
cd Downloads
sudo dpkg --install pureos-archive-keyring_2021.11.0_all.deb
sudo apt update
sudo apt upgrade
Thanks!
1 Like
Yes. dpkg works on a deb file you already have.
1 Like
Thanks! But now please read (study) carefully:
Ok, I downloaded pureos-archive-keyring_2021.11.0_all.deb.
Then, proceeded with cd Downloads and…
~/Downloads$ sudo dpkg --install pureos-archive-keyring_2021.11.0_all.deb (Reading database ... 265712 files and directories currently installed.) Preparing to unpack pureos-archive-keyring_2021.11.0_all.deb ... Unpacking pureos-archive-keyring (2021.11.0) over (2021.11.0) ... Setting up pureos-archive-keyring (2021.11.0) ...
Is that correct? It seems stuck at “Setting up…” ???
And, when I run sudo apt-key list, the new key isn’t listed and the old one is still there. I also tried installing it via Software & Updates, but got this popup…
Should I try removing the old key via Software & Updates?
1 Like
Might help:
sudo apt purge pureos-archive-keyring
And afterwards:
Ok, done… but not certain that it worked!
~$ sudo apt purge pureos-archive-keyring
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
pureos-archive-keyring* pureos-desktop* pureos-gnome* pureos-minimal* pureos-standard*
0 upgraded, 0 newly installed, 5 to remove and 0 not upgraded.
After this operation, 57.3 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 265711 files and directories currently installed.)
Removing pureos-desktop (0.9.4) ...
Removing pureos-gnome (0.9.4) ...
Removing pureos-standard (0.9.4) ...
Removing pureos-minimal (0.9.4) ...
Removing pureos-archive-keyring (2021.11.0) ...
Odd. Doesn’t that last line indicate that the new key had been installed correctly after all?
However, when I check `apt-key list’ as well as Software & Updates again, they both still list keys that have been removed or purged and not the freshly installed one. 
Ploughing ahead in case the new key did actually replace the old one, I tried sudo apt update, but got the same errors as before. I.e., Certificate verification failed.... does not have a Release file.... Updating from such a repository can't be done securely, and is therefore disabled by default.
Should I just try the temporarily “switch https to http” workaround in Post#16 now?
1 Like
I’d like to know what is output of: apt list pureos-archive-keyring?
And please install removed packages back:
sudo apt install pureos-desktop pureos-gnome pureos-standard pureos-minimal
I’m not sure if you are using https, you should use https.
Yes, please. Take the PureOS GNOME image from yesterday.
EDIT: @rootapoottoot, I also see that you are having a lot of packages installed over there (probably including local ones) Please follow this post and put packages.list file aside (including all other backups as @Caliga kindly recommended here) right away, and certainly before you reformat your current drive (if not replacing it with the brand new one), as described here: New Post: App Showcase: Backups. Also, please do not expect that all (especially obsolete) packages will get back and expect that you’ll need to remove “few” packages, by editing this file within gedit, saving it as new one, and retrying to restore what possible, in order to restore packages that are still available within byzantium repo.
1 Like
Thanks for the tip!
I just tried to backup my home directory and got an avalanche of these:
Operation not permitted
cp: cannot create hard link
Operation not permitted
cp: cannot create symbolic link
Invalid argument
cp: cannot create regular file
So, I’m assuming it failed… quite a few times. 
~$ apt list pureos-archive-keyring
Listing... Done
pureos-archive-keyring/now 2021.11.0 all [installed,local]
~$ sudo apt install pureos-desktop pureos-gnome pureos-standard pureos-minimal
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package pureos-desktop
E: Unable to locate package pureos-gnome
E: Unable to locate package pureos-standard
E: Unable to locate package pureos-minimal
Yes, as far as I know, I am using https.