5

When ever I try to go to recommended updates I get the following error and I don't know how to fix it. I had a boot problem before I reinstalled the operating system. Thank you ahead of time for your assistance................................

 pi@raspberry:~ $ sudo apt-get update
Get:1 http://security.debian.org buster/updates InRelease [65.4 kB]
Get:2 http://ftp.debian.org/debian buster InRelease [122 kB]                   
Hit:3 http://archive.raspberrypi.org/debian buster InRelease                   
Get:4 http://ftp.debian.org/debian buster-updates InRelease [51.9 kB]          
Reading package lists... Done        
E: Repository 'http://security.debian.org buster/updates 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.
N: Repository 'http://ftp.debian.org/debian buster InRelease' changed its 'Version' value from '10.7' to '10.10'
E: Repository 'http://ftp.debian.org/debian 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.
E: Repository 'http://ftp.debian.org/debian buster-updates InRelease' changed its 'Suite' value from 'stable-updates' to 'oldstable-updates'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
pi@raspberry:~ $ 
1
  • I see the same thing. Issues like this come up when there's a version change - e.g. buster to bullseye. However, bullseye is not yet in official release for the RPi, and it's unclear (to me) why the maintainers have made these repo changes without also making an announcement. Then again, the last announcement in that forum was in Aug 2020 :( But what to do? The answer below may be correct, but as it amounts to a security bypass, I'll wait on more clarity before taking that step.
    – Seamus
    Aug 30, 2021 at 6:42

4 Answers 4

13

You've asked a good question - one that's a potential concern to all RPi users. I'm still working through this - I may not have a complete answer now, but I'll post what I've learned now, and update when I gather "the rest of the story". Feedback, corrections and comments are welcomed.

Some clarification on semantics is always useful when discussing Debian's Advanced Packaging Tool (APT):

  • APT is a generic term referring to the collection of tools used for package management.
  • apt-get is a 'command-line tool for handling packages, and may be considered the user's "back-end"'
  • apt is 'a high-level commandline interface for the package management system. It is intended as an end user interface and enables some options better suited for interactive usage by default compared to more specialized APT tools like apt-get(8) and apt-cache(8)'

This was not an "error" per se

It's simply information - some feedback from apt letting you know what happened as it attempted the update you requested. apt-get update ran successfully to completion, but it found some things that you should know. It declined to update because it found discrepancies, and it wants you to acknowledge the discrepancy before it performs the update.

Why did apt-get not perform the normal update process?

A lot of details behind this, but I'll summarize it as follows:

  1. RPi OS is a derivative of Debian

  2. Debian officially released bullseye on Aug 14, 2021

  3. As is typical, the official release of RPi's new version lags the release date of Debian by 2-4 months. This because some aspects of the RPi release are dependent upon having a stable Debian release.

  4. This "gap" between the Debian release and the RPi release creates discrepancies in the labels used to identify and segregate branches of the repositories. In particular, the stable label is now assigned to the newer, leading Debian bullseye version. Consequently, the buster branch must surrender the stable label; the RPi and/or Debian maintainers have decided to change the label to oldstable.

  5. apt doesn't know of this change. It wants to follow stable, but stable is now in bullseye - not in buster. Rather than panic, it simply throws the decision over to the user... "what do you want to do, boss?"

What should I do?

You have many options - here are a few to consider:

  1. You can ignore it, and forego updates for a while. This isn't as bad as it sounds... with RPi maintainers hard at work on the bullseye release, there is very little time for changes to buster. To learn when your last upgrade was performed, run less /var/log/apt/history.log. If it's been since Aug 14, you're likely not missing many updates.

  2. You could go ahead and upgrade to a pre-release version of bullseye using one of RonR's scripts.

  3. You can continue following buster. Debian releases are maintained for 3 years, and come under Long-Term-Support for an additional 2 years, so buster will be around for a while. And of course you may also choose to follow buster only until bullseye is released for RPi.

    Under this option, you will need to manipulate apt-get to continue tracking buster. One way to do this is to employ the option --allow-releaseinfo-change; see man apt-get for further details. N.B. that this option brings some risk with it as it essentially bypasses apt-secure. Reviewing the details in man apt-get informs us that it's possible to reduce that risk somewhat by additionally specifying one of the specialty options - in this case the suite label as that is the label that has been changed in buster, from stable to oldstable:

    $ sudo apt-get --allow-releaseinfo-change-suite update 
    
  4. You can try apt instead of apt-get. Some sources will state without reservation that using apt instead of apt-get will simply make this issue go away - i.e.:

    $ sudo apt update
    # as opposed to:
    $ sudo apt-get update
    

    I won't dispute that - all I can say is that on my systems (RPi OS Lite), I have not been able to verify this. I get no prompt from sudo apt update asking me to approve anything. AIUI, apt depends upon /etc/apt/preferences and/or /etc/apt/preferences.d to relieve the user from making decisions - but these files are absent on my system. Debian's man page for apt_preferences states:

    Preferences are a strong power in the hands of a system administrator but they can become also their biggest nightmare if used without care! APT will not question the preferences, so wrong settings can lead to uninstallable packages or wrong decisions while upgrading packages. Even more problems will arise if multiple distribution releases are mixed without a good understanding of the following paragraphs.

    That's enough information for me, thank you. But seriously, this may work beautifully for some - using apt instead of apt-get may work for you. It's certainly the easiest solution here.

  5. I don't presently know of other specific options within apt-get for doing this, but I'd have to guess there are as APT in general, and apt-get in particular is, uh... "full-featured" if nothing else. I also don't know what RPi's MO is for retaining the suite label beyond the official release date for RPi's version of bullseye. I'll update if I learn of their plans.

3
  • 2
    One very minor item: "the RPi maintainers have decided to change the label to oldstable" This decision was actually made by Debian, nor RPi. wiki.debian.org/DebianOldStable
    – SiKing
    Nov 19, 2021 at 21:07
  • @SiKing: Thanks for that item! I wonder though if it's actually decided by Debian & flows down to RPi OS as an edict, or if it's more like a recommendation?
    – Seamus
    Nov 19, 2021 at 21:34
  • My guess: Debian decides this. Everyone who wants to continue to depend on Debian must follow. But I do not know those details. I actually came here looking for answer to "What happens if I have unattended-upgrades turned on?"
    – SiKing
    Nov 19, 2021 at 23:20
0

apt should be prompting you to accept the changes. If not, you can run apt with the additional option apt-get --allow-releaseinfo-change update

This is due to the new release of Debian Bullsye which happened a couple of weeks back.

1
  • Could you elaborate on this a bit? Bullseye is not in "official release" on RPi now - AIUI, that may not happen for 2 or 3 months. Also, using the --allow-releaseinfo-change option seems to effectively bypass apt-secure according to man apt-get. Users should rightly be cautious about bypassing the security feature of the repo - particularly when the maintainer has made no announcement. Please don't misunderstand me - I am not disputing your answer; I am only asking you to elaborate - perhaps supply a reference to support it.
    – Seamus
    Aug 30, 2021 at 6:07
0

If you use apt rather than apt-get (apt-get is the command-line tool for handling packages, and may be considered the user's "back-end" to other tools using the APT library) you should be prompted.

1
  • I've heard that from another source, but haven't been able to confirm it - I get no prompt using apt. If apt does this, it would seem that it would have to be configured to do so; i.e. if the suite label is oldstable then prompt user for input. Do you know where this is configured - or otherwise how it's done?
    – Seamus
    Aug 31, 2021 at 11:46
0

Simple solution is to use sudo apt update followed by sudo apt upgrade.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.