How to fix N: This must be accepted explicitly before updates for this repository can be applied in APT

APTBEGINNERLOWUpdated Dec 29, 2025· 230 views

APT refuses to update repositories when release metadata changes unexpectedly. Use --allow-releaseinfo-change flag or the apt command to accept these changes and resume updating.

Quick fix

Fixes N: This must be accepted explicitly before updates for this repository can be applied

sudo apt-get update --allow-releaseinfo-change
  1. Accept changes using --allow-releaseinfo-change flag
  2. Use apt command for interactive confirmation
  3. Configure persistent acceptance (optional)
  4. Verify updates work after accepting changes
apt — error
sudo apt-get update --allow-releaseinfo-change
N: This must be accepted explicitly before updates for this repository can be applied

What this error means

This error occurs when a repository's release information changes, typically when a Debian or Ubuntu distribution is moved to a different status. For example, when Debian 11 Bullseye became the stable release, Debian 10 Buster was moved to "oldstable" status, causing its Suite value to change from "stable" to "oldstable". APT enforces this security check to ensure users are aware of important distribution changes before automatically updating.

Typical symptoms

  • apt-get update command fails with "This must be accepted explicitly" message
  • Cannot install or upgrade packages until the repository change is acknowledged
  • Error mentions repository URL followed by "changed its 'Suite' value from 'stable' to 'oldstable'"
  • System is unable to fetch package updates from affected repositories

Common causes

  1. A Debian/Ubuntu distribution moved from stable to oldstable status (most common when a new major version is released)
  2. Repository metadata fields changed (Suite, Origin, Label, Codename, or Version)
  3. APT security safeguard preventing automatic updates when release information changes
  4. Using apt-get with strict release validation enabled

How to fix "N: This must be accepted explicitly before updates for this repository can be applied"

1Accept changes using --allow-releaseinfo-change flag

The quickest solution is to run apt-get update with the --allow-releaseinfo-change flag:

bash
sudo apt-get update --allow-releaseinfo-change

This command explicitly accepts the changed repository metadata and proceeds with the update. Run it once, and subsequent apt-get update commands will work normally.

2Use apt command for interactive confirmation

For a more interactive approach, use the apt command instead of apt-get:

bash
sudo apt update

The apt command will prompt you with "Do you want to accept these changes and continue updating from this repository? [y/N]". Type "y" and press Enter to accept the changes. This is the preferred method for interactive use in recent Ubuntu versions.

3Configure persistent acceptance (optional)

If you want to permanently accept all release information changes, add this line to your APT configuration:

bash
sudo nano /etc/apt/apt.conf.d/99-allow-release-changes

Add the following content:

bash
Acquire::AllowReleaseInfoChange::Suite "true";

Save and exit (Ctrl+X, then Y, then Enter). This configuration allows suite changes without requiring the flag each time. Use with caution and only if you understand the implications.

4Verify updates work after accepting changes

After accepting the release changes, verify that package updates work correctly:

bash
sudo apt-get update
sudo apt-get upgrade

You should no longer see the "This must be accepted explicitly" error. The upgrade command shows you what packages will be updated before proceeding.

Advanced notes

For automated environments like Ansible or Docker, you may want to use apt-get update --allow-releaseinfo-change in your automation scripts. You can also use specialized flags like --allow-releaseinfo-change-suite to allow only Suite changes, or --allow-releaseinfo-change-field for specific fields. The AllowReleaseInfoChange configuration option was added to APT 1.8.2.3 and can default certain field changes to true on newer systems. This is a security feature designed to notify administrators of distribution changes; ignoring it may result in unintended upgrades to different distribution versions.

Frequently asked questions

What does "N: This must be accepted explicitly before updates for this repository" mean?
This error occurs when a repository's release information changes, typically when a Debian or Ubuntu distribution is moved to a different status. For example, when Debian 11 Bullseye became the stable release, Debian 10 Buster was moved to "oldstable" status, causing its Suite value to change from "stable" to "oldstable". APT enforces this security check to ensure users are aware of important distribution changes before automatically updating.
How do I fix "N: This must be accepted explicitly before updates for this repository"?
APT refuses to update repositories when release metadata changes unexpectedly. Use --allow-releaseinfo-change flag or the apt command to accept these changes and resume updating.
What causes "N: This must be accepted explicitly before updates for this repository"?
A Debian/Ubuntu distribution moved from stable to oldstable status (most common when a new major version is released) Repository metadata fields changed (Suite, Origin, Label, Codename, or Version) APT security safeguard preventing automatic updates when release information changes
Is the "N: This must be accepted explicitly before updates for this repository" error serious?
It is a low-severity error — more of a blocker than a risk. The steps above resolve it.

Official resources & further reading