"Repository changed its Suite value from stable to oldstable"
The Error
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.
A plain sudo apt update refuses to proceed. Nothing is broken — apt is doing exactly what it was designed to do.
The reason for the refusal is that a repository's metadata is being signed, and a change in the Suite field means the repository is now describing itself differently than last time. Since apt uses this metadata to decide what to install, an unexplained change is treated as a possible attack rather than an update.
In this case the explanation is mundane: Debian released a newer version, so stable moved on and your release became oldstable. Your Pi (or server) did not change; the label attached to it did.

The Immediate Fix
Acknowledge the change once:
sudo apt-get update --allow-releaseinfo-change
sudo apt-get update
On older apt versions the flag is more specific:
sudo apt-get update --allow-releaseinfo-change-suite
Some very old releases (pre-2019) do not have either flag. There, the workaround is to accept interactively — run apt update in a terminal rather than a script and answer y at the prompt — or add Acquire::AllowReleaseInfoChange "true"; to a file under /etc/apt/apt.conf.d/.
After a successful run the new metadata is cached and future updates proceed normally. You should not need the flag again until the next Debian release moves the labels.
The Part You Should Actually Read
The flag silences the warning. It does not solve the underlying problem, which is that your release is end-of-life.
buster is Debian 10. It stopped receiving security updates years ago. Once a release moves to oldstable and then to oldoldstable, the archive is eventually removed from the main mirrors entirely, and apt update starts failing with 404 on every line.
So two different situations look the same from the error message:
You are mid-upgrade and about to move to the new release. The flag is all you need, and you should proceed with the upgrade.
You are still running an EOL release with no plan to move. The flag lets you keep updating package lists, but you are installing software that has not had a security patch in years. That is a genuine risk on anything internet-facing.
Check which you are on:
lsb_release -a
cat /etc/os-release
If VERSION_CODENAME says buster, you are on Debian 10. bullseye is 11, bookworm is 12.
Upgrading, Honestly
On a Raspberry Pi this is not a trivial operation. Raspberry Pi OS does not officially support in-place major upgrades, and the community guidance is to reinstall on a fresh SD card and migrate your data. That is genuinely the lower-risk path, even though it sounds like more work.
For a Pi running one service, the procedure is:
- Take an image of the current card (so you can go back)
- Write the current Raspberry Pi OS to a new card
- Install your packages and restore
/etcconfig and your data - Swap cards and verify
For a Debian server or VM, the supported path exists:
sudo apt update && sudo apt full-upgrade
sudo sed -i 's/buster/bullseye/g' /etc/apt/sources.list
sudo apt update && sudo apt full-upgrade
sudo apt --purge autoremove
That is the shape of it, and every upgrade guide adds steps for the specific packages you have installed. Read one before you start, take a snapshot, and do not do it at 11pm on a machine you need tomorrow.

Preventing The Surprise
Pin the codename, not the suite name. A sources list that says buster never changes label. One that says stable follows the release and will surprise you eventually:
# good - explicit codename
deb http://raspbian.raspberrypi.org/raspbian buster main contrib non-free
# avoid - follows whatever is current
deb http://raspbian.raspberrypi.org/raspbian stable main contrib non-free
Note the date you installed. A Pi set up in 2021 and never touched is running an EOL release by now. That is worth a calendar entry, because the failure mode is silent: everything works until a package you need has no installable version.
Do not blindly add the flag to a cron job. If --allow-releaseinfo-change is baked into your automation, you have disabled the warning permanently — including the time it would have told you something was actually wrong.

The Short Version
sudo apt-get update --allow-releaseinfo-change clears the error.
Then check whether your release is still supported, and if it is not, decide when you are moving — because the next occurrence of this error is not the problem, it is the notification.
Don't trust the download button. Trust the hash.
If this was useful, More hands-on tech guides at TechGeek. No pressure — read it whenever it's useful.