[SOLVED] Buster 'apt-get update' issue

[hippy]

Code: Select all

pi@Pi3B:~ $ sudo apt-get update
Get:1 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]
Get:2 http://archive.raspberrypi.org/debian buster InRelease [25.1 kB]
Get:3 http://archive.raspberrypi.org/debian buster/main armhf Packages [205 kB]
Reading package lists... Done    
E: Repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' changed its 'Suite' value from 'testing' to 'stable'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

Nothing in 'man apt-secure' seemed to tell me what to do - So what exactly do I have to do to make things work ?

[trejan]

Debian Buster was released so it changed to stable.

Run "sudo apt update --allow-releaseinfo-change" and it'll update it.

[MrEngman]

Take a look here https://www.raspberrypi.org/forums/view ... 1&t=245022


MrEngman

[hippy]

Thanks. "sudo apt-get update --allow-releaseinfo-change" fixed it for me.

I hadn't seen an Unread Post mentioning it, and a search found nothing obvious. I guess Sod's Law, or Search Fu Failure, given searching now finds a number of threads referencing the issue.

[uilfut]

I was stuck too, and found the answer here - so thanks for asking!

[Dan1jel]

Debian Buster was released so it changed to stable.

Run "sudo apt update --allow-releaseinfo-change" and it'll update it.

I too had problem with this and was stuck. Thank you for the solution. And thank you OP for starting this thread.

[hardwaremack-orginal]

would of been nice if inside the app it would have said something like type * sudo apt update * if you would like to continue. Thank goodness for this forum.

[ibshar]

Debian Buster was released so it changed to stable.

Run "sudo apt update --allow-releaseinfo-change" and it'll update it.

Thank You

[Juanca]

Hi!

Thanks Trejan for your answer

Rgrds

[Ireneos]

Thanks. Resolved it on pi 4 (that had new noobs card!)

[miaran]

Thanks!
Running sudo apt-get update --allow-releaseinfo-change in the terminal solved it for Raspberry pi 4

[thorstenhirsch]

I also (soft) bricked mine when upgrading from stretch to buster, probably because /boot was only ~65MB. Later I figured out that /boot only contained 3 files after the failed upgrade, so I couldn't boot anymore. Here's what one can do in situations like these:

- resize partitions with gparted (or whatever tool you prefer); I shrinked the ext4 root partition by 200MB at its beginning, so that I could enlarge the fat /boot partition by 200 MB
- mount sd card's /boot on /mnt/sd
- download the latest raspbian image
- check the contents of the image: fdisk -l *.img
- mount the image's boot partition with the offset that fdisk just told you: sudo mount -o loop,offset=$((8192*512)) *img /mnt/image
- copy all files from the image to the sd card: sudo cp -a /mnt/image/* /mnt/sd/
- edit /mnt/sd/cmdline.txt, you need to fix "root=..." with something that works, e.g. "root=/dev/mmcblk0p2"

Finished. Now umount everything and try booting. If there's no video signal and green/red LEDs are on, but don't flash, the kernel isn't found, so you still have a problem with /boot. If the video signal is there, but you only see 3 or 4 images of raspberries, then the kernel is being loaded, but "root=..." is wrong and you need to fix cmdline.txt.