How to fix Depends: package-name but it is not installable in APT

APTINTERMEDIATEMEDIUMUpdated Dec 29, 2025· 329 views

This error occurs when apt cannot find or install a required dependency. It typically happens due to missing repositories, version conflicts, held packages, or PPA issues. Fixing it involves updating your package lists, resolving conflicts, and sometimes removing problematic sources.

Quick fix

Fixes Depends: package-name but it is not installable

sudo apt update
  1. Update your package lists
  2. Use apt's automatic fix mechanism
  3. Check for held packages
  4. Review and remove conflicting PPAs
apt — error
sudo apt update
Depends: package-name but it is not installable

What this error means

When you run an apt command to install a package, apt performs dependency resolution—it checks what other packages (dependencies) are required for your installation to work. If apt cannot locate a specific required dependency in any of your configured repositories, or if the available version of that dependency doesn't satisfy the requirement, it displays this error. The "not installable" message means apt searched all enabled repositories and either couldn't find that package at all, or found versions that conflict with other installed packages or dependency constraints. This is common when using third-party PPAs (Personal Package Archives), when repositories become outdated, or when your system has held packages that prevent dependency resolution.

Typical symptoms

  • apt install command fails with dependency error message
  • Package installation gets blocked even though you have internet connectivity
  • Error message lists specific package name that 'is not installable'
  • Problem persists across multiple package installations
  • System appears to have broken packages that cannot be automatically fixed

Common causes

  1. Missing or disabled repositories containing the required dependency
  2. Version conflicts where the dependency version required doesn't exist in your repositories
  3. Incompatible PPAs (third-party repositories) with your current distribution version
  4. Held packages preventing apt from resolving the full dependency tree
  5. PPA conflicts where multiple repositories provide incompatible versions
  6. Outdated package cache requiring refresh

How to fix "Depends: package-name but it is not installable"

1Update your package lists

Start by refreshing apt's package cache to ensure you have the latest package information from all configured repositories.

bash
sudo apt update

This command downloads the latest package metadata from all your configured sources. Missing packages often appear because your cache is outdated.

2Use apt's automatic fix mechanism

Apt has a built-in feature to fix broken dependencies. This is the quickest solution for most cases.

bash
sudo apt install -f

Or use the older syntax:

bash
sudo apt-get --fix-broken install

This command attempts to correct a system with broken dependencies by automatically selecting package versions that satisfy constraints. It's non-destructive—it only removes packages if absolutely necessary.

3Check for held packages

Sometimes packages are manually marked as "held" (prevented from upgrade/change). These can block dependency resolution.

bash
sudo apt-mark showhold

If you see any packages listed, unhold them:

bash
sudo apt-mark unhold package-name

Then retry your original apt command. Holding is useful for preventing unwanted upgrades, but can create dependency conflicts.

4Review and remove conflicting PPAs

Third-party repositories (PPAs) are a common source of dependency issues. Check what you have enabled:

bash
sudo add-apt-repository --list

If you see PPAs that are outdated, for different Ubuntu versions, or no longer needed, remove them:

bash
sudo add-apt-repository --remove ppa:username/ppa-name

After removing a PPA, update your package lists:

bash
sudo apt update

PPAs are often built for specific Ubuntu releases. Using a PPA for Ubuntu 20.04 on Ubuntu 22.04, for example, can cause exactly this error.

5Install with Aptitude for smarter conflict resolution

Aptitude is a higher-level package manager that's smarter at resolving complex dependency conflicts. It can suggest alternative solutions.

bash
sudo apt install aptitude

Then try installing your package with aptitude instead of apt:

bash
sudo aptitude install package-name

Aptitude will present multiple solutions if conflicts exist, allowing you to choose the best approach. This is more powerful than apt for tricky situations.

6Clean cache and retry

Sometimes cached package information becomes corrupted. Clear it completely:

bash
sudo apt clean
sudo apt autoclean

Then update again:

bash
sudo apt update

After cleaning, the next apt update will re-download all package metadata, which can resolve indexing issues.

Advanced notes

Understanding Dependency Resolution: APT uses a sophisticated dependency solver. When you request a package, it must find versions of all dependencies that are compatible with each other AND with already-installed packages. This forms a "dependency graph." If no valid combination exists in your repositories, apt reports packages as "not installable."

PPA Best Practices: Always check a PPA's documentation to ensure it supports your Ubuntu version. PPAs built for Ubuntu 20.04 often won't work on 22.04 because of library version differences. Before adding a PPA, verify the supported versions.

Emergency Downgrade: If a recent upgrade broke dependencies, you can downgrade a specific package:

bash
sudo apt install package-name=version

Use apt search package-name to find available versions.

Using apt with -o Debug: For deeper troubleshooting, see apt's reasoning:

bash
sudo apt -o Debug::pkgProblemResolver=yes dist-upgrade

This shows apt's decision process when resolving conflicts.

Frequently asked questions

What does "Depends: package-name but it is not installable" mean?
When you run an apt command to install a package, apt performs dependency resolution—it checks what other packages (dependencies) are required for your installation to work. If apt cannot locate a specific required dependency in any of your configured repositories, or if the available version of that dependency doesn't satisfy the requirement, it displays this error. The "not installable" message means apt searched all enabled repositories and either couldn't find that package at all, or found versions that conflict with other installed packages or dependency constraints.
How do I fix "Depends: package-name but it is not installable"?
This error occurs when apt cannot find or install a required dependency. It typically happens due to missing repositories, version conflicts, held packages, or PPA issues. Fixing it involves updating your package lists, resolving conflicts, and sometimes removing problematic sources.
What causes "Depends: package-name but it is not installable"?
Missing or disabled repositories containing the required dependency Version conflicts where the dependency version required doesn't exist in your repositories Incompatible PPAs (third-party repositories) with your current distribution version
Is the "Depends: package-name but it is not installable" error serious?
It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Official resources & further reading