How to fix N: Repository 'URL' changed its 'Label' value in APT

APTBEGINNERMEDIUMUpdated Dec 29, 2025· 251 views

The "Repository changed its Label value" notification appears when apt detects that a package repository has modified its metadata, such as its Label, Origin, or Suite fields. This is a security feature that requires explicit acknowledgment. You can resolve this by running apt update with the --allow-releaseinfo-change flag to approve the changes.

Quick fix

Fixes N: Repository 'URL' changed its 'Label' value

# With apt (preferred on newer systems)
sudo apt update --allow-releaseinfo-change

# Or with apt-get
sudo apt-get update --allow-releaseinfo-change

# Then proceed with regular installations
sudo apt install package-name
  1. Allow the repository metadata change
  2. Review the repository change details
  3. Allow specific metadata field changes (optional)
  4. Make the change permanent (if needed)
apt — error
# With apt (preferred on newer systems)
sudo apt update --allow-releaseinfo-change
# Or with apt-get
sudo apt-get update --allow-releaseinfo-change
# Then proceed with regular installations
sudo apt install package-name
N: Repository 'URL' changed its 'Label' value

What this error means

APT (Debian/Ubuntu package manager) implements strict validation of repository metadata to protect against malicious or compromised mirrors. Each repository publishes metadata including fields like Label (the repository's name/description), Origin (the organization), and Suite (distribution version). When the maintainers modify these fields, APT detects the change and halts operations until you explicitly acknowledge and trust the change. This could happen when a repository is renamed, rebranded, or reorganized by its maintainers. The notification appears as a "N:" (notice) message rather than an error, but it prevents apt update and install operations from proceeding.

Typical symptoms

  • apt update or apt-get update shows 'N: Repository changed its Label value' message
  • apt install commands fail because the update step is blocked
  • The error shows the old Label value and the new Label value in the message
  • apt-get update exits without installing package lists
  • CI/CD pipelines fail at the apt update step with this notice
  • The message includes a reference to apt-secure(8) manpage

Common causes

  1. Repository maintainers intentionally renamed or rebranded the repository
  2. Repository migrated from one label (e.g., 'Docker CE') to another (e.g., 'Docker EE')
  3. Ubuntu/Debian repository metadata changed due to distribution name or version updates
  4. PPA (Personal Package Archive) was renamed or restructured by the maintainer
  5. Repository changed from experimental to stable or vice versa

How to fix "N: Repository 'URL' changed its 'Label' value"

1Allow the repository metadata change

The simplest solution is to tell apt that you trust and accept the repository's metadata changes. Run apt update with the --allow-releaseinfo-change flag:

bash
# With apt (preferred on newer systems)
sudo apt update --allow-releaseinfo-change

# Or with apt-get
sudo apt-get update --allow-releaseinfo-change

# Then proceed with regular installations
sudo apt install package-name

This single command allows the label change and updates your package lists. The change is applied only for this command execution.

2Review the repository change details

Before accepting the change, you may want to see exactly what changed. The error message shows:
- The repository URL
- The field that changed (Label, Origin, Suite, etc.)
- The old value
- The new value

Look at your apt sources to identify which repository is changing:

bash
# View all enabled repositories
cat /etc/apt/sources.list
ls /etc/apt/sources.list.d/

# Search for the repository URL mentioned in the error
grep -r "repository-url" /etc/apt/sources.list.d/

Verify that the repository is legitimate before proceeding. If you don't recognize it, it's best to remove it rather than accept unknown changes.

3Allow specific metadata field changes (optional)

If you want to allow only certain field changes (Label, Suite, Codename, Version), you can use more specific flags:

bash
# Allow only Label changes
sudo apt update --allow-releaseinfo-change-label

# Allow only Suite changes (e.g., focal to jammy)
sudo apt update --allow-releaseinfo-change-suite

# Allow only Codename changes
sudo apt update --allow-releaseinfo-change-codename

# Allow Version field changes
sudo apt update --allow-releaseinfo-change-version

These flags are more granular if you want to permit specific changes while being cautious about others.

4Make the change permanent (if needed)

If you want this change to be accepted permanently without needing the flag each time, create an apt configuration file:

bash
# Create a configuration file to always allow metadata changes
echo 'Apt::Get::AllowReleaseInfoChange "true";' | sudo tee /etc/apt/apt.conf.d/99allow-releaseinfo-change

# Verify it was created
cat /etc/apt/apt.conf.d/99allow-releaseinfo-change

# Test that apt update now works without flags
sudo apt update

Now apt commands will automatically accept repository metadata changes. This is safe if you trust your repository sources and keep them updated.

5Remove untrusted repositories

If the changing repository is unfamiliar or untrusted, it's safer to remove it entirely rather than accept unknown changes:

bash
# List all repositories with details
apt policy

# Remove a repository by disabling it
sudo nano /etc/apt/sources.list  # Edit and comment out or delete lines

# Or remove a PPA:
sudo add-apt-repository --remove ppa:username/ppaname

# Remove a repository added via sources.list.d:
sudo rm /etc/apt/sources.list.d/repository-name.list

# Update after removing
sudo apt update

Removing the repository is the most conservative approach if you don't recognize it or don't need it anymore.

Advanced notes

Why this security feature exists: APT validates repository metadata to prevent man-in-the-middle attacks and ensure you're downloading packages from the expected source. A compromised mirror could change the Label field to disguise itself. This strict validation protects system integrity.

Common repository changes: Docker changed from 'Docker CE' to 'Docker EE' (Community vs Enterprise), Ubuntu Pro repositories changed labeling when transitioning from 'UA Client' to 'Ubuntu Pro Client', and various PPAs rename themselves for clarity or branding updates.

In CI/CD pipelines: Docker containers and CI systems frequently encounter this error because repositories update their metadata. The --allow-releaseinfo-change flag is standard in many Dockerfile base images and CI configuration files.

GitHub Actions workaround: If you're using GitHub Actions, you may need to add this to your workflow:

yaml
- name: Update package lists
  run: sudo apt update --allow-releaseinfo-change

Container images: When building Docker containers with older base images, the parent image's repositories may have changed. This is why it's recommended to use recent base image tags (e.g., ubuntu:22.04 instead of ubuntu:16.04).

Frequently asked questions

What does "N: Repository 'URL' changed its 'Label' value" mean?
APT (Debian/Ubuntu package manager) implements strict validation of repository metadata to protect against malicious or compromised mirrors. Each repository publishes metadata including fields like Label (the repository's name/description), Origin (the organization), and Suite (distribution version). When the maintainers modify these fields, APT detects the change and halts operations until you explicitly acknowledge and trust the change.
How do I fix "N: Repository 'URL' changed its 'Label' value"?
The "Repository changed its Label value" notification appears when apt detects that a package repository has modified its metadata, such as its Label, Origin, or Suite fields. This is a security feature that requires explicit acknowledgment. You can resolve this by running apt update with the --allow-releaseinfo-change flag to approve the changes.
What causes "N: Repository 'URL' changed its 'Label' value"?
Repository maintainers intentionally renamed or rebranded the repository Repository migrated from one label (e.g., 'Docker CE') to another (e.g., 'Docker EE') Ubuntu/Debian repository metadata changed due to distribution name or version updates
Is the "N: Repository 'URL' changed its 'Label' value" error serious?
It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Official resources & further reading