How to Fix ‘E: The Repository Does Not Have a Release File’ in Ubuntu

Updating package repositories in Ubuntu with sudo apt update only for the process to terminate with the error: “E: The repository ‘https://ppa.launchpadcontent.net/… Release’ does not have a Release file. N: Updating from such a repository can’t be done securely, and is therefore disabled by default” blocks package management and software upgrades. In Debian and Ubuntu’s Advanced Package Tool (APT) security architecture, every software repository must publish a signed Release or InRelease metadata file detailing package checksums and cryptographic signatures. When a third-party Personal Package Archive (PPA) is abandoned, lacks support for your newer Ubuntu release (such as Noble Numbat 24.04), or points to a decommissioned URL, APT halts update operations to protect system security. This tutorial explains how to identify offending repositories, remove broken PPAs, and restore clean package updates in Ubuntu.

Why Does APT Throw ‘Does Not Have a Release File’?

Because APT strictly enforces cryptographic authenticity before downloading packages, this error surfaces whenever repository metadata cannot be verified:

  • PPA Lacks Support for Your Ubuntu Release: Upgrading Ubuntu from an older version (e.g. 20.04 or 22.04 to 24.04) while retaining PPAs whose maintainers have not compiled builds for the new release codename.
  • Decommissioned or Typos in Repository URLs: A PPA being deleted by its maintainer on Launchpad, or a misspelled repository address added to package sources.
  • End-of-Life (EOL) Ubuntu Distribution: Running an obsolete release of Ubuntu that Canonical has moved from standard mirrors to old-releases.ubuntu.com.
  • Network Proxies Blocking Metadata Files: Corporate firewalls or transparent web proxies intercepting and returning 404/403 responses for repository metadata files.

Method 1: Identify the Failing PPA from Terminal Output

Carefully reading the error output reveals the exact repository name causing the update pipeline to fail.

  1. Execute a standard package update in your terminal:
    sudo apt update
  2. Review the final lines of output. Look for lines structured like:
    E: The repository 'https://ppa.launchpadcontent.net/dead-ppa/ppa/ubuntu noble Release' does not have a Release file.
  3. Note the maintainer and repository name (in this example, dead-ppa/ppa) and the target release codename (e.g. noble).

Method 2: Remove the Offending PPA via add-apt-repository

The cleanest and standard way to remove an obsolete PPA is using the built-in --remove flag.

  1. Execute the removal command, specifying the exact PPA identified in Method 1:
    sudo add-apt-repository --remove ppa:maintainer/ppa-name
  2. Press Enter to confirm the removal. The utility will automatically delete the repository file from /etc/apt/sources.list.d/ and remove its GPG key.
  3. Refresh your package lists to verify clean execution:
    sudo apt update

Method 3: Manually Remove Problematic Source Files in /etc/apt/sources.list.d/

If add-apt-repository cannot locate the PPA or if you added the source manually via modern .sources files, delete the file directly.

  1. Navigate to the third-party sources directory:
    cd /etc/apt/sources.list.d/
  2. List the configured repository files:
    ls -la
  3. Locate the file matching the broken repository (e.g. dead-ppa.list or dead-ppa.sources).
  4. Remove the offending file using administrative privileges:
    sudo rm /etc/apt/sources.list.d/problematic-file.list
  5. Clean the APT cache and update:
    sudo apt clean && sudo apt update

Method 4: Update Old-Releases Mirrors for EOL Ubuntu Installations

If you are running an unsupported, end-of-life Ubuntu release, standard archive mirrors will return 404 errors for all repositories.

  1. Check your current release codename:
    lsb_release -a
  2. If your version is officially End-of-Life, point your package sources to Canonical’s dedicated archive server:
    sudo sed -i -e 's/archive.ubuntu.com/old-releases.ubuntu.com/g' /etc/apt/sources.list
    sudo sed -i -e 's/security.ubuntu.com/old-releases.ubuntu.com/g' /etc/apt/sources.list
  3. Run sudo apt update. The package manager will now successfully download repository metadata from the legacy archive.

Overview of Release File Error Solutions

Root Cause Diagnostic Command Recommended Fix
Unsupported PPA Codename apt update error log sudo add-apt-repository --remove ppa:...
Custom .list or .sources file ls /etc/apt/sources.list.d/ Delete specific file with sudo rm
End-of-Life Ubuntu Release lsb_release -c Switch mirrors to old-releases.ubuntu.com
Stale Local Cache ls /var/lib/apt/lists/ sudo apt clean && sudo apt update

Removing unsupported PPAs and cleaning obsolete repository entries eliminates the Release file error, restoring seamless software updates in Ubuntu.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.