bullseye changed from stable to oldstable, buster not updating anymore [SOLVED]

[Ashpool]

Just noticed that sudo apt update|install xxx on my buster desktopsystem failed connect to/download anything. And on my bullseye Install, it reported that its suite changed from "stable" to "oldstable".
The Download Site for the OS still shows bullseye as current and buster as legacy, but maybe we are on the verge to see a new bookworm image anytime soon?
And does this has any consequences for the (buster based) retropie image installs?

[Lolonois]

@Ashpool said in bullseye changed from stable to oldstable:

The Download Site for the OS still shows bullseye as current and buster as legacy, but maybe we are on the verge to see a new bookworm image anytime soon?

I doubt there will be a Bookworm PiOS soon. For example: After release of Debian Bullseye it took ~4 months for the first Bullseye based PiOS.

The legacy concept ("Raspberry Pi OS Legacy") introduced by the foundation is an improvement as they now maintain also the PiOS release before current. As long as there is no bookworm PiOS there will be (security) updates to buster (bc. buster is the release before the current bullseye).

@Ashpool said in bullseye changed from stable to oldstable:

And does this has any consequences for the (buster based) retropie image installs?

Nope. The RetroPie Image uses the distro names in /etc/apt/sources.list (e.g. buster) and not the floating/relative names (oldoldstable, oldstable, stable, ...)

[Ashpool]

@Lolonois said in bullseye changed from stable to oldstable:

The legacy concept ("Raspberry Pi OS Legacy") introduced by the foundation is an improvement as they now maintain also the PiOS release before current. As long as there is no bookworm PiOS there will be (security) updates to buster (bc. buster is the release before the current bullseye).

And that was the "problem" i encountered - on my buster install calling "sudo apt update" just reported many times a "cannot initiate the connection to archive.raspberrypi.org:80", and then as one of the last error messages "The repository 'https://Archive.raspberry.org/debian buster Release" no longer has a Release File".
And I just imaged that buster OS on a SD card 2 days ago (for testing purposes).
And on Raspberry OS (bullseye) sudo apt update mentioned that it was changed from the stable to the oldstable branche (and apparently raspi OS knows no oldoldstable).

[Lolonois]

@Ashpool seems like a temporary outage. Mine update runs as follows:

# apt update
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://archive.raspberrypi.org/debian buster/main armhf Packages [400 kB]
Hit:4 https://www.linux-projects.org/listing/uv4l_repo/raspbian/stretch stretch InRelease  # <--- ignore in this context
Get:5 http://archive.raspberrypi.org/debian buster/main armhf Contents (deb) [1909 kB]
Get:6 http://raspbian.raspberrypi.org/raspbian buster/non-free Sources [140 kB]
Get:7 http://raspbian.raspberrypi.org/raspbian buster/main Sources [11.4 MB]
Get:8 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages [13.0 MB]
Get:9 http://raspbian.raspberrypi.org/raspbian buster/main armhf Contents (deb) [40.5 MB]
Get:10 http://raspbian.raspberrypi.org/raspbian buster/non-free armhf Packages [110 kB]
Get:11 http://raspbian.raspberrypi.org/raspbian buster/non-free armhf Contents (deb) [787 kB]
Fetched 68.3 MB in 24s (2813 kB/s)                                             
Reading package lists... Done
Building dependency tree       
Reading state information... Done
12 packages can be upgraded. Run 'apt list --upgradable' to see them.
N: Repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' changed its 'Suite' value from 'oldstable' to 'oldoldstable'

N: is for notice level, thus no action to be done.

Does the issue still persist? Can you share the contents of /etc/apt/sources.list and /etc/apt/sources.list.d/raspi.list?

[Ashpool]

@Lolonois said in bullseye changed from stable to oldstable:

Does the issue still persist? Can you share the contents of /etc/apt/sources.list and /etc/apt/sources.list.d/raspi.list?

Sadly it still fails for me (bullseye is fine) & sure...
here is the log of my 'sudo apt update' a few minutes ago.

/etc/apt/sources.list

deb http://raspbian.raspberrypi.org/raspbian/ buster main contrib non-free rpi
# Uncomment line below then 'apt-get update' to enable 'apt-get source'
#deb-src http://raspbian.raspberrypi.org/raspbian/ buster main contrib non-free rpi

/etc/apt/sources.list.d/raspi.list

deb http://archive.raspberrypi.org/debian/ buster main
# Uncomment line below then 'apt-get update' to enable 'apt-get source'
#deb-src http://archive.raspberrypi.org/debian/ buster main

Ok - as it was just a test install I will see now what a fresh image will do
Edit: Nope, strange is that the "update"-bar on the first boot (after resize one) into the desktop had the update bar filling up slow but constantly, a 'sudo apt update' right after the OOBE steps where done resulted again in: log on fresh buster imager

[Ashpool]

Ok,
never had to do this before (and if i had previously known about that command, i simply forgot it) -> sudo apt update --allow-releaseinfo-change solved the issue.

@Lolonois btw. glad to see that the raspberry os branches do have an oldoldstable one ;] Still it sounds like bookworm is on its way. Though I never went there before, so I don't know since when the [bookworm/-staging]-folders appeared on http://raspbian.raspberrypi.org/raspbian/dists/

[windg]

I saw a today similar topic in the Raspberrypi forum: https://forums.raspberrypi.com/viewtopic.php?p=2134267&sid=7308121de26156ac990edaa9cb2fdef5#p2134267.
I updated a fresh downloaded RetroPie image without issues, maybe it was something temporary.

[Lolonois]

@Ashpool said in bullseye changed from stable to oldstable, buster not updating anymore [SOLVED]:

Still it sounds like bookworm is on its way. Though I never went there before, so I don't know since when the [bookworm/-staging]-folders appeared on http://raspbian.raspberrypi.org/raspbian/dists/

They showed up as early as 2022-01-24 according to archive.org. But from that there can no forecast be deduced when there will be a first general public release of Bookworm.

Anyhow, glad you could fix your issue.

[GoPackGo]

https://www.raspberrypi.com/news/bookworm-the-new-version-of-raspberry-pi-os/

Bookworm PiOS came out in October