APT prompts this when a repository changes metadata like Suite or Origin, typically during major Debian releases. Accept the changes to continue updates.
APT prevents automatic updates when repository metadata changes significantly. This safety feature, introduced in APT 1.5, requires you to confirm that you understand and accept changes like a distribution moving from "stable" to "oldstable" or a company name change in the Origin field. This protects you from unknowingly applying major version changes without awareness.
If you are using the apt command (not apt-get), the prompt will appear directly:
sudo apt updateWhen prompted "Do you want to accept these changes and continue updating from this repository? [y/N]", type y and press Enter. This is the safest approach as you review what is changing.
If apt update isn't available or you need to automate the update, use the --allow-releaseinfo-change flag:
sudo apt-get update --allow-releaseinfo-changeThis flag tells APT to automatically accept repository metadata changes. You only need to run this once; future updates will succeed.
To make this change persistent across all future updates, create or edit /etc/apt/apt.conf.d/99-allow-release-changes and add:
sudo nano /etc/apt/apt.conf.d/99-allow-release-changesAdd this line (replace Suite with the field that changed: Origin, Label, Codename, Suite, Version, or DefaultPin):
Acquire::AllowReleaseInfoChange::Suite "true";Save and exit (Ctrl+X, then Y for yes). Now apt update will work without prompts.
If you want to know which field changed before accepting, look at the full error output. It will show something like:
Repository 'http://deb.debian.org/debian bullseye InRelease' changed its 'Suite' value from 'stable' to 'oldstable'The field name appears in quotes. You can then use the specific flag:
sudo apt-get update --allow-releaseinfo-change-suiteOther options: --allow-releaseinfo-change-origin, --allow-releaseinfo-change-label, --allow-releaseinfo-change-version, --allow-releaseinfo-change-codename.
This prompt is a deliberate security feature. Repository metadata changes indicate significant updates (like major Debian releases), and APT requires confirmation to ensure you are aware. If you see this prompt frequently from the official Debian repositories, it usually means a new stable release has been published and your system is transitioning to the previous release's branch. This is normal and safe to accept. For third-party repositories that change metadata unexpectedly, investigate the repository before accepting—it could indicate a compromise or migration. You can reset or review APT's configuration in /etc/apt/apt.conf.d/ if needed.
E: Cannot set to hold: package 'package-name' is not installed
How to fix "Cannot set to hold" error when package is not installed in APT
debconf: unable to initialize frontend: Dialog
How to fix "debconf: unable to initialize frontend: Dialog" in APT
E: Could not connect to proxy server
Could not connect to proxy server
dpkg: serious warning: files list file for package 'package-name' contains empty filename
How to fix "files list file contains empty filename" in APT
E: Package 'package:i386' has no installation candidate
How to fix "Package package:i386 has no installation candidate" in apt