Sudo apt-get update not working

Hello,

I cannot update packages on either Raspberry Pi 3B+ or 4B (two separate microSD’s, clean installs)

-Navio2
-2020-09-22 issue
-4.19.127-emlid-v7+ #1 SMP PREEMPT Mon Aug 24 19:50:57 MSK 2020 armv7l

pi@DinhDrone:~ $ sudo apt-get update
Hit:1 http://files.emlid.com/navio2/debian buster InRelease
Get:2 http://packages.ros.org/ros/ubuntu buster InRelease [4,671 B]
Hit:3 http://archive.raspberrypi.org/debian buster InRelease
Get:4 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]
Err:2 http://packages.ros.org/ros/ubuntu buster InRelease
The following signatures were invalid: EXPKEYSIG F42ED6FBAB17C654 Open Robotics info@osrfoundation.org
Reading package lists… Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://packages.ros.org/ros/ubuntu buster InRelease: The following signatures were invalid: EXPKEYSIG F42ED6FBAB17C654 Open Robotics info@osrfoundation.org
E: Repository ‘http://raspbian.raspberrypi.org/raspbian buster InRelease’ changed its ‘Suite’ value from ‘stable’ to ‘oldstable’
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

Tried these and did not work:


Any pointers is greatly appreciated.

Thanks,
Vegeta

Hi Vegeta,

I suggest following the instructions from this article. The main point is that you need to find this exact expired key and renew it using the apt-key command.

Let me know whether it worked out for you.

Liudmila, thank you and got it to work with an additional step, for anyone who would find this:

E: Repository ‘http://raspbian.raspberrypi.org/raspbian buster InRelease’ changed its ‘Suite’ value from ‘stable’ to 'oldstable’
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

Solution:

Hi Vegeta,

Glad to hear that you found a complete solution for your case! I hope it will work for the users that faced the same issue too.