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

When running sudo apt update on Ubuntu, encountering the error message E: The repository 'http://ppa.launchpad.net/.../ubuntu [release-codename] Release' does not have a Release file followed by N: Updating from such a repository can't be done securely, and is therefore disabled by default halts software synchronization. Because modern Debian and Ubuntu distributions enforce strict cryptographic verification, APT refuses to download package lists from repositories that lack a signed Release or InRelease manifest. This error occurs most frequently after upgrading Ubuntu to a newer release version (e.g., upgrading from 22.04 Jammy to 24.04 Noble) when third-party Personal Package Archives (PPAs) have not yet built packages for the new release, or when an abandoned repository is taken offline. Resolving this issue involves removing or disabling the incompatible repository definitions.

Why APT Flags Repositories Without Release Files

The Advanced Package Tool (APT) requires every repository defined in /etc/apt/sources.list and /etc/apt/sources.list.d/ to provide an authoritative Release file detailing package checksums, architecture trees, and GPG cryptographic signatures. When an author creates a PPA on Launchpad, they must explicitly build packages for each Ubuntu release codename (such as focal, jammy, or noble). If you attempt to update a system configured with a codename that the PPA maintainer never targeted, Launchpad returns an HTTP 404 Not Found error for the requested Release file. Because unsigned repositories could expose users to compromised packages, APT disables the archive and exits with an error code.

Common technical reasons for missing release files include:

• Ubuntu Distribution Upgrades: Upgrading the operating system while third-party PPAs remain pointed at old or non-existent release codenames. For cdrom errors, see our guide on fixing Failed to Fetch cdrom:// in Ubuntu.
• Abandoned or Deprecated PPAs: Developers deleting or deprecating experimental Launchpad archives. For locale warnings, see our guide on fixing Failed to Set Locale in Ubuntu.
• Typographical Errors in Repository URLs: Manually typing repository URLs with incorrect distribution codenames or misspelled architecture flags. For GPG key errors, check our guide on fixing GPG error NO_PUBKEY in Ubuntu.

Component / Error Line	Root Cause	Status	Recommended Resolution
ppa.launchpad.net/... noble Release 404	PPA maintainer hasn’t built for Ubuntu 24.04	Fatal APT error	Remove PPA via add-apt-repository --remove
Deprecated third-party archive	Domain or repository removed by author	Fatal APT error	Delete .list file in /etc/apt/sources.list.d/
Mistyped codename	Typo in manual sources definition	Fatal APT error	Correct codename to valid LTS release name

Method 1: Remove the Incompatible PPA via add-apt-repository

If the error identifies a specific Personal Package Archive hosted on Launchpad, using the official add-apt-repository command with the --remove flag cleanly purges the broken repository.

1. Observe the exact PPA name from the terminal error (for example: http://ppa.launchpad.net/user/ppa-name/ubuntu).
2. Open your terminal by pressing Ctrl + Alt + T.
3. Remove the PPA by executing:
   sudo add-apt-repository --remove ppa:user/ppa-name
   (Replace user/ppa-name with the actual developer and archive name from the error message).
4. Press Enter to confirm the removal.
5. Run sudo apt update. The error will no longer appear, allowing standard package updates to continue.

Method 2: Delete the Corresponding .list or .sources File Manually

If the failing repository was added manually or via a third-party script, deleting its definition file from the sources.list.d directory permanently eliminates the error.

1. Navigate to the directory housing third-party repository definitions:
   cd /etc/apt/sources.list.d/
2. List all active repository configuration files:
   ls -la
3. Locate the .list or .sources file matching the domain or application throwing the Release file error (e.g. broken-repo.list).
4. Remove the problematic file with administrative privileges:
   sudo rm broken-repo.list
5. If a corresponding GPG key file exists (e.g. broken-repo.gpg or in /etc/apt/trusted.gpg.d/), remove it as well.
6. Update your package lists:
   sudo apt update

Method 3: Revert Repository Codename to a Previous Supported LTS Release

If the software from the PPA is critical to your workflow and the developer has not yet updated it for your current Ubuntu release, you can temporarily edit the repository to pull binaries built for the preceding LTS release.

1. Open the specific repository file in nano:
   sudo nano /etc/apt/sources.list.d/[repository-name].list
2. Locate the release codename in the line (e.g., noble for 24.04).
3. Change the codename to the preceding supported LTS release (e.g., change noble to jammy for 22.04 packages).
4. Press Ctrl + O and Enter to save, then press Ctrl + X to exit.
5. Run sudo apt update. Because Launchpad contains a valid Release file for the earlier release, the update will succeed.

Method 4: Purge Installed PPA Packages via ppa-purge

If you previously installed software from the broken PPA and want to cleanly downgrade those packages to official Ubuntu versions before removing the archive, use ppa-purge.

1. Install the ppa-purge utility:
   sudo apt install -y ppa-purge
2. Execute ppa-purge against the affected PPA:
   sudo ppa-purge ppa:user/ppa-name
3. The utility will automatically downgrade any modified packages back to stock Ubuntu versions and remove the PPA configuration file.
4. Rerun sudo apt update.

Method 5: Check and Correct the System Master sources.list

If the missing Release file error references official Ubuntu archives (such as archive.ubuntu.com), your core release codename is misspelled.

1. Check your current official distribution codename:
   lsb_release -cs (e.g. jammy or noble).
2. Open your master sources file:
   sudo nano /etc/apt/sources.list
3. Ensure all lines reference your exact system codename without typographical errors.
4. Save the file and run sudo apt update to confirm smooth package indexing.