search

RPi-Distro / pi-gen

Tool used to create the official Raspberry Pi OS images
BSD 3-Clause "New" or "Revised" License
2.63k stars 1.64k forks source link

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

Closed bzuelly closed 5 years ago

bzuelly commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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

hhromic commented 5 years ago

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

XECDesign commented 5 years ago

ok to close?

bzuelly commented 5 years ago

Yes thanks for your help

Sent from my iPhone

On Jul 23, 2019, at 8:33 AM, XECDesign notifications@github.com<mailto:notifications@github.com> wrote:

ok to close?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FRPi-Distro%2Fpi-gen%2Fissues%2F309%3Femail_source%3Dnotifications%26email_token%3DADTYMTRSWDQJDJN3JD5X4FTQA4CB7A5CNFSM4H6XE7MKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2TD7FA%23issuecomment-514211732&data=02%7C01%7C%7Cd269f525f3a140d0e86808d70f72536b%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636994856002322107&sdata=cbFR3oQeSVpi46LXDYpiV%2FX%2FlpfDCG0EwVE2HYadQ%2Fg%3D&reserved=0, or mute the threadhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADTYMTS5AKHUHSFPLF4A4W3QA4CB7ANCNFSM4H6XE7MA&data=02%7C01%7C%7Cd269f525f3a140d0e86808d70f72536b%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636994856002342123&sdata=2Rn8Fqp5003m7WyyUMXZkliSgtI0l7vMrBUD06Z0IVk%3D&reserved=0.