Что такое stable updates
When I went to update my 3 x RPI-4s they all showed no updates, which is unusual in my experience even after a week between checks I usually get some updates, but now they all also display the message after the check:
N: Repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'What does this mean?
The full text from a check of one RPi is:
pi@octopi:~ $ sudo apt update Get:1 http://archive.raspberrypi.org/debian buster InRelease [32.6 kB] Get:2 http://archive.raspberrypi.org/debian buster/main armhf Packages [378 kB] Hit:3 https://repo.zabbix.com/zabbix/5.4/raspbian buster InRelease Get:4 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB] Get:5 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages [13.0 MB] Fetched 13.4 MB in 9s (1,513 kB/s) Reading package lists. Done Building dependency tree Reading state information. Done All packages are up to date. N: Repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'rpdom Posts: 22691 Joined: Sun May 06, 2012 5:17 am Location: Chelmsford, Essex, UK
Re: Repo changed from «stable» to «oldstable», what does this mean?
It’s nothing to worry about.
The main Raspbian repository tracks the Debian repositories. Debian has just upgraded from Buster to Bullseye. Bullseye is their new «stable» release and Buster has been relegated to «oldstable».
When Raspberry Pi are ready, they will release new install images that use Bullseye instead of Buster. That will be fairly soon.
There are some important differences between Buster and Bullseye, most notably the removal of Python 2.
Unreadable squiggle
Taomyn Posts: 4 Joined: Fri Feb 05, 2021 4:38 pm
Re: Repo changed from «stable» to «oldstable», what does this mean?
Tue Aug 24, 2021 8:08 am
It’s nothing to worry about.
Thanks for the prompt response and explanation, I’m glad it’s nothing to be concerned over, but my worry stemmed more from the fact that there were zero updates on all my devices which has never happened in the year or so of checking every week — yes I’m a bit thorough in this regard.
greatquux Posts: 17 Joined: Tue Aug 24, 2021 8:04 pm
Re: Repo changed from «stable» to «oldstable», what does this mean?
Will we be able to upgrade to the bullseye release when ready with a simple apt update and apt full-upgrade?
roydukkey Posts: 1 Joined: Wed Aug 25, 2021 2:00 am
Re: Repo changed from «stable» to «oldstable», what does this mean?
rpdom wrote: [. ] they will release new install images that use Bullseye instead of Buster.
Will these images seamlessly apply and install with these commands? Or, will systems currently on Buster diverge from active, regular updates?
sudo apt update sudo apt full-upgrade davidcoton Posts: 7236 Joined: Mon Sep 01, 2014 2:37 pm Location: Cambridge, UK
Re: Repo changed from «stable» to «oldstable», what does this mean?
Tue Aug 24, 2021 8:27 pm
Will we be able to upgrade to the bullseye release when ready with a simple apt update and apt full-upgrade?
roydukkey wrote:
rpdom wrote: [. ] they will release new install images that use Bullseye instead of Buster.
Will these images seamlessly apply and install with these commands? Or, will systems currently on Buster diverge from active, regular updates?
sudo apt update sudo apt full-upgrade From past history, it is unlikely that cross-version upgrades will be supported.
It is possible that upgrading basic systems will just be a matter of changing the apt sources, but it is also possible that *your* system will break.
The normal mantra will continue to update systems within the original version, but from past history RPT will not continue to provide updates, so only the Debian updates will apply.
Location: 345th cell on the right of the 210th row of L2 cache
electronix_tech Posts: 2 Joined: Mon Dec 09, 2019 11:41 pm
Re: Repo changed from «stable» to «oldstable», what does this mean?
I used Solution 1 from this web page and it fixed that problem.
Solution 1. sudo apt-get update —allow-releaseinfo-change
HawaiianPi Posts: 7862 Joined: Mon Apr 08, 2013 4:53 am Location: Aloha, Oregon USA
Re: Repo changed from «stable» to «oldstable», what does this mean?
Tue Aug 24, 2021 8:27 pm
Will we be able to upgrade to the bullseye release when ready with a simple apt update and apt full-upgrade?
By default update/full-upgrade only performs upgrades to the installed release (Buster will only get Buster updates).
Upgrading to a new major release has never been an approved procedure. Raspberry Pi OS is not a rolling release (meaning, it’s not designed to upgrade from one major release to another).
That doesn’t mean people won’t try it, and some may even be successful, but for others it will end badly. It’s always recommended to start fresh which each new major release. For some this may seem like a daunting task, but problems with in-place upgraded systems often cause far more headaches.
My mind is like a browser. 27 tabs are open, 9 aren’t responding,
lots of pop-ups, and where is that annoying music coming from?
pfletch101 Posts: 745 Joined: Sat Feb 24, 2018 4:09 am Location: Buffalo, NY, USA
Re: Repo changed from «stable» to «oldstable», what does this mean?
Wed Aug 25, 2021 2:04 pm
The normal mantra will continue to update systems within the original version, but from past history RPT will not continue to provide updates, so only the Debian updates will apply.
I share the OP’s surprise that there were no available updates after (in my case) 2 weeks since my last apt dist-upgrade. I won’t be moving to Bullseye for a couple of months (after it is released) on my ‘workhorse’ Pi, since I will have a fair amount of configuration and testing to do before I can do this. In the interim, will any Debian Buster updates (presumably largely security-related) be available from the Raspberry Pi Debian Buster repository, or will I need to go direct to the Debian repositories for these.
davidcoton Posts: 7236 Joined: Mon Sep 01, 2014 2:37 pm Location: Cambridge, UK
Re: Repo changed from «stable» to «oldstable», what does this mean?
Sat Aug 28, 2021 2:15 pm
Wed Aug 25, 2021 2:04 pm
The normal mantra will continue to update systems within the original version, but from past history RPT will not continue to provide updates, so only the Debian updates will apply.
I share the OP’s surprise that there were no available updates after (in my case) 2 weeks since my last apt dist-upgrade. I won’t be moving to Bullseye for a couple of months (after it is released) on my ‘workhorse’ Pi, since I will have a fair amount of configuration and testing to do before I can do this. In the interim, will any Debian Buster updates (presumably largely security-related) be available from the Raspberry Pi Debian Buster repository, or will I need to go direct to the Debian repositories for these.
Again, looking at the precedents, security (and other) updates from Debian will be echoed in the RPiOS repository. It is only the RPi specific updates that cease — RPT do not have the (human) bandwidth to support two versions.
It should not matter, but note that apt full-upgrade has replaced apt dist-upgrade. It’s just a name thing, dist-upgrade was misleading because the distribution (wheezy/jessie/stretch/buster/bullseye) actually remains the same, there is no automatic cross-distribution upgrade in apt.
Location: 345th cell on the right of the 210th row of L2 cache
craigevil Posts: 494 Joined: Wed Jan 27, 2021 5:22 am Location: heaven
Re: Repo changed from «stable» to «oldstable», what does this mean?
Upgrading to a new major release has never been an approved procedure. Raspberry Pi OS is not a rolling release (meaning, it’s not designed to upgrade from one major release to another).
That is too bad. With Debian you can pretty much go from release to release forever as long as you READ the Release docs.
What changes that rpios can’t be upgraded to a new release?
I added the Bullseye repos months ago and everything seems to be working without any problems.
Raspberry PI 400 Raspberry Pi OS Bookworm Kernel: 6.1.0-rpi4-rpi-v8 DE: XFCE
Debian — «If you can’t apt install something, it isn’t useful or doesn’t exist»
jamesh Raspberry Pi Engineer & Forum Moderator
Posts: 32710 Joined: Sat Jul 30, 2011 7:41 pm
Re: Repo changed from «stable» to «oldstable», what does this mean?
Sat Aug 28, 2021 3:41 pm
Upgrading to a new major release has never been an approved procedure. Raspberry Pi OS is not a rolling release (meaning, it’s not designed to upgrade from one major release to another).
That is too bad. With Debian you can pretty much go from release to release forever as long as you READ the Release docs.
What changes that rpios can’t be upgraded to a new release?
I added the Bullseye repos months ago and everything seems to be working without any problems.
You can certainly try it, but we don’t test it, and don’t put any effort in to making sure it works. So the choice is yours.
Principal Software Engineer at Raspberry Pi Ltd.
Working in the Applications Team.
dickon Posts: 2495 Joined: Sun Dec 09, 2012 3:54 pm Location: Home, in Tiffield
Re: Repo changed from «stable» to «oldstable», what does this mean?
Sat Aug 28, 2021 3:51 pm
You can certainly try it, but we don’t test it, and don’t put any effort in to making sure it works. So the choice is yours.
And that having finally been said, I can say without fear of being countered, that it’s been flawless every time I’ve done it. I will happily admit that my systems aren’t quite normal — netbooted, so /dev/mmcblk0p1 size is irrelevant; no desktop — but the usual Debian update dance has workd for me every time. Headless lite -> lite will probably just work. Desktops possibly not so much.
Snapshot and try it. If you can’t snapshot, well, that’s another discussion.
As it is apparently board policy to disallow any criticism of anything, as it appears to criticise something is to criticise all the users of that something, I will no longer be commenting in threads which are not directly relevant to my uses of the Pi.
Chivar Posts: 3 Joined: Wed Sep 11, 2019 8:31 am
Re: Repo changed from «stable» to «oldstable», what does this mean?
Sat Aug 28, 2021 3:41 pm
That is too bad. With Debian you can pretty much go from release to release forever as long as you READ the Release docs.
What changes that rpios can’t be upgraded to a new release?
I added the Bullseye repos months ago and everything seems to be working without any problems.
2: deb https://archive.raspberrypi.org/debian/ bullseye main
allpass Posts: 19 Joined: Sat Oct 26, 2019 3:10 pm
Re: Repo changed from «stable» to «oldstable», what does this mean?
This is a big problem for us. We run automatic updates in our product (running on CM3+) that runs apt-get update -y and this change basically breaks hundreds of end-user products in the field.
Is there a way to revert this so that updates will continue to work? Accepting returns of all these units because the update system is broken or having to explain to several hundred customers how to manually re-image their system is going to be a very expensive prospect for us.
jamesh Raspberry Pi Engineer & Forum Moderator
Posts: 32710 Joined: Sat Jul 30, 2011 7:41 pm
Re: Repo changed from «stable» to «oldstable», what does this mean?
I’ve asked around to see if there is anything that can be done. I don’t know enough about it to know where the change came from or what it affects or how to get round it.
However, I am quite concerned about you updating multiple products in the field automatically from the repos without testing first. Really you shouldn’t be doing this, as there is really no guarantee that it will work properly afterwards. This is a prime example! For products like this you should provide your own updates that are fully testing and you know will work, not rely on some third party system. Probably your own apt server where you control exactly what goes on, but I am no expert.
Principal Software Engineer at Raspberry Pi Ltd.
Working in the Applications Team.
PhilE Raspberry Pi Engineer & Forum Moderator
Posts: 5497 Joined: Mon Sep 29, 2014 1:07 pm Location: Cambridge
Re: Repo changed from «stable» to «oldstable», what does this mean?
We’ve never (in my memory) supported upgrades between major OS releases. From https://www.raspberrypi.org/documentati . rs/os.html (emphasis added):
Note that full-upgrade is used in preference to a simple upgrade, as it also picks up any dependency changes that may have been made.
Generally speaking, doing this regularly will keep your installation up to date for the particular major Raspberry Pi OS release you are using (e.g. Stretch). It will not update from one major release to another, for example, Stretch to Buster.
And further down, before the discussion of dust-upgrade, it says:
Upgrading from Operating System Versions
WARNING
Upgrading an existing image is possible, but is not guaranteed to work in every circumstance and we do not recommend it. If you do wish to try upgrading your operating system version, we strongly suggest making a backup first — we can accept no responsibility for loss of data from a failed update.
PhilE Raspberry Pi Engineer & Forum Moderator
Posts: 5497 Joined: Mon Sep 29, 2014 1:07 pm Location: Cambridge
Re: Repo changed from «stable» to «oldstable», what does this mean?
And it’s a bit much to say
this change basically breaks hundreds of end-user products in the field.
when what you mean is that they will no longer update.
allpass Posts: 19 Joined: Sat Oct 26, 2019 3:10 pm
Re: Repo changed from «stable» to «oldstable», what does this mean?
when what you mean is that they will no longer update.
Well sure, but users think it’s broken because our app reports an error.
We still had the raspi repos in the sources list but we’ve locked all package versions to the current ones except for the apt server that serves the latest version of our application. I never thought I had to remove those since I figured they wouldn’t change, or that the raspi servers being down wouldn’t cause the apt-get update to require user intervention. Indeed during testing we saw some servers down and the process still completed anyway without manual prodding. Obviously it’s my fault for not knowing the intricacies of this stuff. I wear many hats. But I don’t understand the purpose behind requiring manual changes. I’ve been using Linux on my desktop for years and never had this happen to me.
Does anyone know of a GUI-based tool that incorporates usbboot and an image writing tool into one program? If my users have to image their units I need something as straightforward as possible. Ideally they could plug in the USB bootloader port on the device, run a program and it would bootload and then update the image in one step. I wrote up instructions for my IT-minded users but a lot of folks don’t even know which end of the USB cable is which.
AkulaMD Posts: 256 Joined: Fri Jun 19, 2020 6:51 am
Re: Repo changed from «stable» to «oldstable», what does this mean?
Tue Aug 24, 2021 8:08 am
It’s nothing to worry about.
The main Raspbian repository tracks the Debian repositories. Debian has just upgraded from Buster to Bullseye. Bullseye is their new «stable» release and Buster has been relegated to «oldstable».
When Raspberry Pi are ready, they will release new install images that use Bullseye instead of Buster. That will be fairly soon.
There are some important differences between Buster and Bullseye, most notably the removal of Python 2.
Hi, newbie question here. What are the noticeable differences with the removal of Python 2 for a normal end user like me who use the Raspberry Pi 4 for watching YouTube, Netflix and browsing internet. Thank you in advance.
Raspberry Pi OS (32-bit) with desktop and recommended software
Raspberry Pi 4 Model B 8GB at stock speed (never overclock)
Never overclock your Pi.
Encourage optimization instead.
craigevil Posts: 494 Joined: Wed Jan 27, 2021 5:22 am Location: heaven
Re: Repo changed from «stable» to «oldstable», what does this mean?
Raspberry PI 400 Raspberry Pi OS Bookworm Kernel: 6.1.0-rpi4-rpi-v8 DE: XFCE
Debian — «If you can’t apt install something, it isn’t useful or doesn’t exist»
jojopi Posts: 3851 Joined: Tue Oct 11, 2011 8:38 pm
Re: Repo changed from «stable» to «oldstable», what does this mean?
Sat Sep 04, 2021 12:11 am
We still had the raspi repos in the sources list but we’ve locked all package versions to the current ones except for the apt server that serves the latest version of our application.
The error message from apt-get update (1.8.2.2) is:
E: Repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable' N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.This disables the Raspbian repository only, not the Raspberry Pi OS repo, nor any that you have added.
So, can you push a new version of your application with a postinst script to accept the Suite change or otherwise patch the problem? Re-imaging seems a rather extreme solution, and bear in mind Raspberry Pi are not recommending bullseye yet, so you probably want to stay on buster for a few months anyway.
Incidentally, apt 1.8.2.3 was released on April 19, with the only difference being that AllowReleaseInfoChange::Suite defaults to true. If your systems had done an unpinned upgrade between then and August 14, that would also have avoided the problem:
N: Repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'allpass Posts: 19 Joined: Sat Oct 26, 2019 3:10 pm
Re: Repo changed from «stable» to «oldstable», what does this mean?
Sat Sep 04, 2021 6:56 am
So, can you push a new version of your application with a postinst script to accept the Suite change or otherwise patch the problem? Re-imaging seems a rather extreme solution, and bear in mind Raspberry Pi are not recommending bullseye yet, so you probably want to stay on buster for a few months anyway.
I would love to push a new version of my application but the problem is that apt-get update fails before my update script (triggered by my user application) even has a change to actually upgrade any packages. So the problem is that there seems like no way to actually have any packages update (mine or anyone else’s) without console access which is not possible since there is no console accessible to the user.
beta-tester Posts: 1589 Joined: Fri Jan 04, 2013 1:57 pm Location: de_DE
Re: Repo changed from «stable» to «oldstable», what does this mean?
Sat Aug 28, 2021 3:41 pm
simply replacing buster by bullseye or adding an additional line for bullseye in
/etc/apt/sources.list and /etc/apt/sources.list.d/raspi.list
does not work for me.
when i try to full-upgrade it throws an error:
Reading package lists. Done Building dependency tree Reading state information. Done Calculating upgrade. Error! Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libc6-dev : Breaks: libgcc-8-dev (< 8.4.0-2~) but 8.3.0-6+rpi1 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. stable, stable/updates and stable-updates in the sources.list
Here is an explanation of the three source URIs you have listed.
This path will be used for updates which many users may wish to install on their systems before the next point release is made, such as updates to virus scanners and timezone data.
If you are asking why these have different forms, that is just how the people concerned choose how to have things set up. The / forward slash corresponds to the structure of the underlying URL, which in turn corresponds to the directory structure of the corresponding apt repository.
- the source URI deb http://http.debian.net/debian wheezy-updates main corresponds to the URL http://http.debian.net/debian/dists/wheezy-updates/
- the source URI deb http://security.debian.org/ testing/updates main contrib non-free corresponds to the URL http://security.debian.org/dists/testing/updates/
- the source URI deb http://debian.lcs.mit.edu/debian/ wheezy-updates main contrib non-free corresponds to the URL http://debian.lcs.mit.edu/debian/dists/wheezy-updates/
stable-updates
Некоторые пакеты из proposed-updates также могут быть доступны через механизм stable-updates. Этот путь будет использоваться для обновлений, которые многие пользователи могут захотеть установить в своих системах перед выпуском следующей версии, например, обновления для антивирусов и данные о часовых поясах. Все пакеты из stable-updates будут включены в точечные версии дистрибутива.
Для Debian 9 "Stretch", чтобы использовать пакеты из stretch-updates (aka stable-updates), вы должны добавить в ваш sources.list следующие. Пример:
deb http://httpredir.debian.org/debian stretch-updates main deb-src http://httpredir.debian.org/debian stretch-updates main
Для Debian 8 "Jessie", чтобы использовать пакеты из jessie-updates (aka oldstable-updates), вы должны добавить в ваш sources.list следующие. Пример:
deb http://httpredir.debian.org/debian jessie-updates main deb-src http://httpredir.debian.org/debian jessie-updates main
При следующем запуске apt-get update, система узнает о пакетах в секции (old)stable-updates и будет рассматривать их при поиске пакетов для обновления.
Заметим, что если APT::Default-Release установлен в вашем файле /etc/apt/apt.conf (или в любом из файлов /etc/apt/apt.conf.d/*), то чтобы автоматические обновления работали, необходимо добавить аналогичный блок конфигурации для /etc/apt/preferences (см. apt_preferences(5) для получения большей информации):
Package: * Pin: release o=Debian,n=stretch-updates Pin-Priority: 990
Когда новый пакет доступен через (old)stable-updates, это будет объявлено на почтовой рассылке debian-stable-announce.
stable-updates были введены в DebianSqueeze, чтобы заменить DebianLenny's Volatile (см. объявление).
Смотрите также
- DebianReleases
- StableProposedUpdates
- https://lists.debian.org/debian-stable-announce/ - Обновления для стабильных пакетов будут объявлены в этом списке.
- Bit from the SRMs: the "stable-updates" suite
stable-updates
Some packages from proposed-updates may also be made available via the stable-updates mechanism. This path will be used for updates which many users may wish to install on their systems before the next point release is made, such as updates to virus scanners and timezone data. All packages from stable-updates will be included in point releases.
For Debian 12.2 Bookworm, in order to use packages from bookworm-updates (aka stable-updates), you can add an entry to your sources.list. For example:
deb http://deb.debian.org/debian bookworm-updates main deb-src http://deb.debian.org/debian bookworm-updates main
For Debian 11.8 Bullseye, in order to use packages from bullseye-updates (aka oldstable-updates), you can add an entry to your sources.list. For example:
deb http://deb.debian.org/debian bullseye-updates main deb-src http://deb.debian.org/debian bullseye-updates main
For older Debian release *-updates no longer exists as those suites no longer receive updates.
The next time you run apt update, the system will become aware of the packages in the (old)stable-updates section and will consider them when looking for packages to upgrade.
Note that if APT::Default-Release is set in your apt configuration, then, in order for automatic upgrades to work, some apt pinning needs to be added (see apt_preferences(5) for more information):
Package: * Pin: release o=Debian,n=bookworm-updates Pin-Priority: 990
When a new package is made available via (old)stable-updates, this will be announced on the debian-stable-announce mailing list.
stable-updates were introduced in DebianSqueeze, to replace DebianLenny's Volatile (see announcement).
See also
- DebianReleases
- StableProposedUpdates
- https://lists.debian.org/debian-stable-announce/ - Updates to stable packages will be announced on this list.
- Bit from the SRMs: the "stable-updates" suite