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

APTBEGINNERMEDIUMUpdated Dec 29, 2025· 242 views

This security notification appears when a package repository changes its Origin metadata. It requires explicit user acknowledgment before package updates can proceed. Learn how to safely accept these changes.

Quick fix

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

sudo apt update
  1. Accept changes interactively with apt
  2. Use non-interactive flag for automated environments
  3. Verify the change is legitimate
  4. Remove repositories with unexpected changes
apt — error
sudo apt update
N: Repository 'URL' changed its 'Origin' value

What this error means

APT (Advanced Package Tool) includes a security feature that validates repository metadata consistency. The "Origin" field in a repository's Release file identifies the organization publishing the repository. When a repository maintainer changes this metadata—such as when Google changed from "Google, Inc." to "Google LLC"—APT requires you to explicitly acknowledge the change before continuing. This is a security measure to protect against man-in-the-middle attacks and repository hijacking. Since APT version 1.5, users must confirm changes to important repository metadata fields like Origin, Label, Codename, and Version to ensure they intentionally accept significant changes.

Typical symptoms

  • apt update or apt-get update command fails with 'changed its Origin value' error
  • Package manager refuses to check for updates after a repository metadata change
  • Automated scripts fail during package update stages
  • Prompt appears asking 'Do you want to accept these changes?' but no input is accepted

Common causes

  1. Repository maintainer updated the Origin metadata (e.g., company renamed or restructured)
  2. Third-party repository changed organizational branding (common with Google, Grafana, NVIDIA)
  3. Repository migrated to a new organization or domain

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

1Accept changes interactively with apt

Run the update command without additional flags. APT will prompt you to accept the changes:

bash
sudo apt update

When prompted with:

bash
Do you want to accept these changes and continue updating from this repository? [y/N]

Type y and press Enter to accept the new Origin metadata. This tells APT you've reviewed and approved the repository changes.

Note: If using apt-get instead of apt, you may need to use apt for the interactive prompt to appear.

2Use non-interactive flag for automated environments

For scripts, CI/CD pipelines, or Docker builds where interactive input is impossible, add the --allow-releaseinfo-change flag:

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

This automatically accepts the repository metadata changes without prompting. If multiple repositories have changed, repeat for each:

bash
sudo apt-get update --allow-releaseinfo-change-origin
sudo apt-get update --allow-releaseinfo-change-label
sudo apt-get update --allow-releaseinfo-change-version

Use specific flags if only certain metadata fields changed.

3Verify the change is legitimate

Before accepting, verify the change comes from the actual repository maintainer:

1. Check the repository source: Examine your repository list:

bash
cat /etc/apt/sources.list
ls /etc/apt/sources.list.d/

2. Visit official website: Go to the official project website (e.g., Google, Grafana) and confirm the new Origin name matches their official branding changes.

3. Check repository documentation: Review the repository's official changelog or announcement to understand why the metadata changed.

4. Verify URL is correct: Ensure the repository URL in your sources hasn't been altered—only the Origin metadata changed.

4Remove repositories with unexpected changes

If you cannot verify the change is legitimate, remove the repository:

bash
# Remove by source list file
sudo rm /etc/apt/sources.list.d/repository-name.list

# Or disable it by commenting out in main sources list
sudo nano /etc/apt/sources.list

Then run:

bash
sudo apt update

Only re-add the repository after confirming the changes are legitimate from official sources.

Advanced notes

Why APT enforces this change: Repository metadata changes can indicate serious issues like man-in-the-middle attacks, DNS hijacking, or malicious repository redirects. By requiring explicit acknowledgment, APT ensures you've reviewed what changed.

Common repository changes: Google Chrome Remote Desktop, Google Linux repositories, Grafana OSS, NVIDIA Docker, and many third-party repositories have updated their Origin metadata over time. This is typically safe when verified through official channels.

aptitude compatibility: The text-based package manager aptitude has historically had issues handling Origin changes. If you use aptitude, switch to apt for the interactive prompt or use the flag-based approach.

Temporary vs. permanent acceptance: Using the flag (--allow-releaseinfo-change) is temporary—it only suppresses the check for that single run. The error will reappear on future updates. Interactive acceptance (y/N) also doesn't permanently suppress the check; it only confirms for that session. APT expects you to make a conscious decision each time significant metadata changes.

Frequently asked questions

What does "N: Repository 'URL' changed its 'Origin' value" mean?
APT (Advanced Package Tool) includes a security feature that validates repository metadata consistency. The "Origin" field in a repository's Release file identifies the organization publishing the repository. " to "Google LLC"—APT requires you to explicitly acknowledge the change before continuing.
How do I fix "N: Repository 'URL' changed its 'Origin' value"?
This security notification appears when a package repository changes its Origin metadata. It requires explicit user acknowledgment before package updates can proceed. Learn how to safely accept these changes.
What causes "N: Repository 'URL' changed its 'Origin' value"?
Repository maintainer updated the Origin metadata (e.g., company renamed or restructured) Third-party repository changed organizational branding (common with Google, Grafana, NVIDIA) Repository migrated to a new organization or domain
Is the "N: Repository 'URL' changed its 'Origin' 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