E: The repository '...' does not have a Release file
apt can’t find index files for a source — the repo doesn’t support your Ubuntu/Debian release, the URL is wrong, or the release reached end of life.
Seen on:
Linux
Meaning
PPAs and vendor repos publish per release codename (jammy, noble, bookworm). Adding one for a codename it doesn’t support, or running an EOL release whose mirrors moved to old-releases, produces this.
Common causes
- Repo/PPA has no build for your release codename
- EOL release moved to old-releases.ubuntu.com
- Typo in the source URL
- Release file “not valid yet” due to wrong system clock
⚡ Quick fix
- Remove or fix the source in /etc/apt/sources.list.d/
- Upgrade the OS, or point an EOL release at old-releases
- Fix the clock (timedatectl) for “not valid yet”
Detailed fix by platform
Ubuntu
- bash
grep -r ^deb /etc/apt/sources.list /etc/apt/sources.list.d/ sudo add-apt-repository --remove ppa:someone/ppa timedatectl
How to diagnose
- Source — Which line fails?
- Codename — lsb_release -cs supported by the repo?
- Clock — Correct date?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- dpkg lock E: Could not get lock /var/lib/dpkg/lock-frontend — is another process using it?
- dpkg was interrupted E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem
- Failed to download metadata for repo Error: Failed to download metadata for repo 'appstream' (dnf / yum)
Most viewed in Linux
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026