I tried asking this earlier, but my problem still persists.
I'm running Brave Version 1.2.43 Chromium: 79.0.3945.130 (Official Build) (64-bit) on my 19.10 Ubuntu laptop.
If I run sudo apt-get update
I get the following failures:
Get:13 https://brave-browser-apt-release.s3.brave.com eoan InRelease [3,162 B]
Hit:14 http://ppa.launchpad.net/system76/pop/ubuntu eoan InRelease
Err:15 http://ppa.launchpad.net/ian-berke/ppa-drawers/ubuntu eoan Release
404 Not Found [IP: 2001:67c:1560:8008::15 80]
Err:13 https://brave-browser-apt-release.s3.brave.com eoan InRelease
The following signatures were invalid: EXPKEYSIG A8580BDC82D3DC6C Brave Software <support@brave.com>
Reading package lists... Done
E: The repository 'http://ppa.launchpad.net/ian-berke/ppa-drawers/ubuntu eoan 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: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://brave-browser-apt-release.s3.brave.com eoan InRelease: The following signatures were invalid: EXPKEYSIG A8580BDC82D3DC6C Brave Software <support@brave.com>
If I click on the link, I don't see an eoan
release, but I do see the xenial
release on 2016-May-04. What file should I edit to tell Ubuntu to use that release?
One of the references to my previous attempt suggested that I install ppa-purge. I did, but no joy.
I'm lost on how to solve my specific problem. I'd like to update Brave. I'm sorry to not know better, but I'd appreciate advice on a specific corrective action to take.
i tried removing Brave completely:
sudo apt remove brave-browser
sudo apt purge brave-browser
rm -rf ~/.config/BraveSoftware
rm -rf ~/.cache/BraveSoftware
I thought this would solve the problem. But I still get that same error when I execute sudo apt-get update
.
I see that Ubuntu 19.10 reaches the end of its life next month. Is the answer to upgrade to 20.10 and try again?