Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

apt update error: debian buster suite changed to oldstable #163

Open
meonkeys opened this issue Mar 31, 2022 · 1 comment
Open

apt update error: debian buster suite changed to oldstable #163

meonkeys opened this issue Mar 31, 2022 · 1 comment
Labels

Comments

@meonkeys
Copy link

meonkeys commented Mar 31, 2022

sudo apt update from a shell on the latest picroft emits an error about a repository:

Get:1 http://archive.raspberrypi.org/debian buster InRelease [32.6 kB]
Get:2 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]
Get:3 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages [13.0 MB]
E: Repository 'http://archive.raspberrypi.org/debian buster InRelease' changed its 'Suite' value from 'testing' to 'oldstable'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N] 
Fetched 13.1 MB in 12s (1,045 kB/s)                                                                                                  
Reading package lists... Done
E: Failed to fetch http://archive.raspberrypi.org/debian/dists/buster/InRelease  
E: Some index files failed to download. They have been ignored, or old ones used instead.

Environment (please complete the following information):

  • Device type: Raspberry Pi 3B
  • OS: Picroft
  • Mycroft-core version: 21.2.2
  • Other versions: Jabra 410 USB speaker+mic

Workaround
This seems to work. Running it once clears the error from happening on future executions of sudo apt update. I'm not clear on exactly what it does, though.

sudo apt update --allow-releaseinfo-change

See also

@meonkeys meonkeys added the bug label Mar 31, 2022
@krisgesling
Copy link
Contributor

Thanks for this - I'm sure others will be hitting the same issue.

Because we don't manage updates to Picroft like we do the Mark II I'm not sure there's much we can do beyond updating the downloadable Picroft image.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants