Why does it say 'unstable' in apt update?

General Discussion
1

Hi!

apt list --upgradable generates the following output for me:

firmware-atheros/unstable 1:20210315-3+rpt1 all [aktualisierbar von: 20210315-3]
firmware-brcm80211/unstable 1:20210315-3+rpt1 all [aktualisierbar von: 20210315-3]
firmware-iwlwifi/unstable 1:20210315-3+rpt1 all [aktualisierbar von: 20210315-3]
firmware-misc-nonfree/unstable 1:20210315-3+rpt1 all [aktualisierbar von: 20210315-3]
firmware-realtek/unstable 1:20210315-3+rpt1 all [aktualisierbar von: 20210315-3]
libraspberrypi-bin/unstable 1:2+git20210928~141951+6e8f786-1 arm64 [aktualisierbar von: 1:2+git20210719~113532+97bc818-3]
libraspberrypi0/unstable 1:2+git20210928~141951+6e8f786-1 arm64 [aktualisierbar von: 1:2+git20210719~113532+97bc818-3]
linux-libc-dev/unstable 1:1.20210928-1 arm64 [aktualisierbar von: 1:1.20210831-1]
raspberrypi-bootloader/unstable 1:1.20210928-1 arm64 [aktualisierbar von: 1:1.20210831-1]
raspberrypi-kernel/unstable 1:1.20210928-1 arm64 [aktualisierbar von: 1:1.20210831-1]
raspberrypi-sys-mods/unstable 20210928 arm64 [aktualisierbar von: 20210901]
tzdata/stable-updates 2021a-1+deb11u1 all [aktualisierbar von: 2021a-1]

I’m wondering why it says “unstable” for like most of the packages? Shouldn’t it only use stable release repositories?

2

I guess it’s not relay a question for DietPi as it is related on how the Raspbian apt repository is used. But probably MichaIng would have some technical explanation.

3

Yes. At least I found out where “unstable” comes from.

The command apt policy reports:

Paketdateien:
100 /var/lib/dpkg/status
release a=now
500 > Index of /debian > bullseye/main arm64 Packages
release o=Raspberry Pi Foundation,a=unstable,n=bullseye,l=Raspberry Pi Foundation,c=main,b=arm64
origin archive.raspberrypi.org
100 > Index of /debian > bullseye-backports/non-free arm64 Packages
release o=Debian Backports,a=bullseye-backports,n=bullseye-backports,l=Debian Backports,c=non-free,b=arm64
origin deb.debian.org
100 > Index of /debian > bullseye-backports/main arm64 Packages
release o=Debian Backports,a=bullseye-backports,n=bullseye-backports,l=Debian Backports,c=main,b=arm64
origin deb.debian.org
500 > https://deb.debian.org/debian-security > bullseye-security/main arm64 Packages
release v=11,o=Debian,a=stable-security,n=bullseye-security,l=Debian-Security,c=main,b=arm64
origin deb.debian.org
500 > Index of /debian > bullseye-updates/main arm64 Packages
release v=11-updates,o=Debian,a=stable-updates,n=bullseye-updates,l=Debian,c=main,b=arm64
origin deb.debian.org
500 > Index of /debian > bullseye/non-free arm64 Packages
release v=11.0,o=Debian,a=stable,n=bullseye,l=Debian,c=non-free,b=arm64
origin deb.debian.org
500 > Index of /debian > bullseye/contrib arm64 Packages
release v=11.0,o=Debian,a=stable,n=bullseye,l=Debian,c=contrib,b=arm64
origin deb.debian.org
500 > Index of /debian > bullseye/main arm64 Packages
release v=11.0,o=Debian,a=stable,n=bullseye,l=Debian,c=main,b=arm64
origin deb.debian.org
Mit Pinning verwaltete Pakete:

The lines in red are the source of unstable, whereas green is the source for stable.

I don’t know. Is this “unstable” thing alright?

4

Both are complete different repositories. archive.raspberrypi.org would need to be kept as it’s providing the kernel for RPi devices.

But I guess this is how Raspberry Foundation labels the repository. https://www.raspberrypi.org/forums/viewtopic.php?t=264978#p1611326

probably Buster is called testing
and Bullseye unstable

5

Those will be updated when Raspberry Pi OS Bullseye is released: https://github.com/RPi-Distro/repo/issues/258