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

buster InRelease' changed its 'Suite' value from 'testing' to 'stable' #309

Closed
bzuelly opened this issue Jul 8, 2019 · 6 comments
Closed

Comments

@bzuelly
Copy link

bzuelly commented Jul 8, 2019

I'm building on a physical box running 32-bit ubuntu server.

Its been working all day until just a little bit ago. It now stops shortly after starting and says "buster InRelease' changed its 'Suite' value from 'testing' to 'stable'"

Anyone else seeing this error?

@hhromic
Copy link
Contributor

hhromic commented Jul 8, 2019

I just built a test image without any issues using a Docker build based on i386/debian:buster.
While is true this is not the same setup as yours, it still means pi-gen itself is probably okay,

Debian Buster this weekend was promoted from testing to stable, perhaps you should clean your work directories (sysroots) and start the build 100% from scratch?

@hhromic
Copy link
Contributor

hhromic commented Jul 8, 2019

I just got the mentioned error on a running Buster image that I previously built (before this weekend) while doing apt-get update:

# apt-get update
Hit:1 http://archive.raspberrypi.org/debian buster InRelease
Get:2 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 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.

This StackExchange answer provides an easy fix (and explanation): https://superuser.com/a/1457007

What happens here, is that the local apt database remembered your package-sources "release-information" to be "busterAsTesting", and when updating now "busterAsStable" is returned.

This further makes me think that you just need to start your builds from scratch so you invalidate your old cache containing testing as suite.

In the running image, after doing apt-get update --allow-releaseinfo-change once, the cache gets updated and the error goes away for good.

@bzuelly
Copy link
Author

bzuelly commented Jul 8, 2019

whats the best way to clean my work directories? purge "work/"?

@hhromic
Copy link
Contributor

hhromic commented Jul 10, 2019

@bzuelly yes probably cleaning the work directory should be enough.

@XECDesign
Copy link
Member

ok to close?

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

No branches or pull requests

3 participants