Tell me more ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

How do I resolve unmet package dependencies?

Occasionally, when I'm installing stuff, I get an error like the following:

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 package1 : Depends: package2 (>= 1.8) but 1.7.5-1ubuntu1 is to be installed
E: Broken packages

How can I resolve this?

share|improve this question
9  
Forget the exact package name. It is irrelevant to this question. I'm attempting to create a canonical question. As such, the exact package isn't relevant in this specific instance. – jrg May 21 '12 at 14:35
11  
Actually "the exact package name", while not relevant in your question, is extremely relevant to any individual's issue in this regard. Usually the best 1st step to resolving this is to identify the source of pkg1 & pkg2. This seems to have been overlooked in the answers, most of which are quite good otherwise. Additionally not noted is that in many, if not most cases, "<whatever> is to be installed" really means "<whatever> is installed". This is something that tends to confuse many users facing this & should also be included in an answer below – doug May 25 '12 at 6:52
1  
@doug Add that as an answer and not a comment, it's pretty good! :) – jrg May 25 '12 at 11:17
Actually if you see every answer has more or less the same thing. Could they be merged into a community wiki? – Ashu May 27 '12 at 9:48

11 Answers

up vote 67 down vote accepted
+500

APT is a package management system for Debian and other Linux distributions based on it, such as Ubuntu. For the most part,APT is easy to use for installing, removing, and updating packages. In rare instances, often when you are mixing in third-party dependencies, there is a chance that apt-get may end up giving you an error telling you that a package installation could not be completed.

Solutions:

It is always a good idea to back up configuration files like /etc/apt/sources.list, so you can revert the changes if needed.

  • If the error shows something like this:

    <some-package>: Depends: <other-package> (= version) but this-version is to be installed

    Then make sure that the restricted and universe repositories are enabled. Hit Alt+F2, type software-properties-gtk and hit Enter.

    Under Ubuntu Software tab, enable all the repositories.

  • One possible cause of unmet dependencies could be corrupted package database, and/or some packages weren’t installed properly. To fix this problem, hit Alt+Ctrl+T to open terminal and try to run one of the following commands:

    sudo apt-get clean

    or,

    sudo apt-get autoclean

    apt-get clean clears out the local repository of retrieved package files (the .deb files). It removes everything but the lock file from /var/cache/apt/archives/ and /var/cache/apt/archives/partial/. apt-get autoclean clears out the local repository of retrieved package files, but unlike apt-get clean, it only removes package files that can no longer be downloaded, and are largely useless.

  • One of the most basic fixes to resolve dependencies problems is to run:

    sudo apt-get -f install

    The -f hare stands for “fix broken”. Apt will attempt to correct broken dependencies. If you manually installed a package that had unmet dependencies, apt-get will install those dependencies, if possible, otherwise it may simply remove the package that you installed in order to resolve the problem.

    Then run:

    sudo dpkg --configure -a

    Then run this again:

    sudo apt-get -f install

    If the output is:

    0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

    That means it failed.

  • Next solution is to run:

    sudo apt-get -u dist-upgrade

    If it shows any held packages, it is best to eliminate them. Packages are held because of dependency conflicts that apt cannot resolve. Try this command to find and repair the conflicts:

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

    If it cannot fix the conflicts, it will exit with:

    0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.

    Delete the held packages one by one, running dist-upgrade each time, until there are no more held packages. Then reinstall any needed packages. Be sure to use the --dry-run option, so that you are fully informed of consequences:

    sudo apt-get remove --dry-run package-name

    Since removing the package you are trying to install may not be ideal, you might also try finding a repository that has the packages you need to satisfy the dependencies.

Finally, if all else fails, you can attempt to satisfy the dependencies yourself, either by finding and installing the necessary packages, or by installing them from source and then creating “deb” packages for them.

Disable/Remove/Purge PPAs:

PPAs (Personal Package Archive) are repositories hosted on Launchpad. You can use PPAs to install or upgrade packages that are not available in the official Ubuntu repositories.

One of the most common causes of unmet dependencies are PPAs, specially when used to upgrade the existing package in Ubuntu repositories. To solve the problem you have tree options, disable, purge (revert back to original package in Ubuntu repositories) or remove PPA.

  • Disable:

    Disabling a PPA means no more updates for the packages installed from that PPA. To disable a PPA: Open Software Center > Edit > Software Sources Or,

    Hit Alt+F2 and run software-properties-gtk.

    Click on Other Software tab, you'll see that each PPA have two lines here, one for the compiled packages and one for the source, Uncheck both lines to disable a PPA. Hare you can also add and remove PPAs.

  • Purge:

    Purging a PPA means, downgrading the packages in the selected PPA to the version in the official Ubuntu repositories and disabling that PPA. PPA Purge does exactly that. To install PPA Purge run the following command:

    sudo apt-get install ppa-purge

But, Considering the question apt is broken so the above command will fail. So use this command

mkdir ppa-purge && cd ppa-purge && wget http://mirror.pnl.gov/ubuntu/pool/universe/p/ppa-purge/ppa-purge_0.2.8+bzr56_all.deb && wget http://mirror.pnl.gov/ubuntu//pool/main/a/aptitude/aptitude_0.6.6-1ubuntu1_i386.deb && sudo dpkg -i ./*.deb

To use PPA Purge:

sudo ppa-purge ppa:someppa/ppa

If 'ppa-purge' command fails for some reason, you can't run 'ppa-purge' again unless you re-enable the PPA (To enable the PPA follow the same steps as disabling a PPA and Check the both lines of a particular PPA to enable it).

Note: PPA Purge doesn't remove PPAs (may be in future), So you'll have to manually remove the PPA.

  • Remove:

    If the package installed from a PPA doesn't exist in official Ubuntu repositories then using PPA Purge is not recommended, because there's nothing to be downgraded and PPA Purge wouldn't delete it either. To remove a PPA and installed packages run the following commands: (Ignore the first command if you don't want to remove the installed packages)

    sudo apt-get autoremove --purege package-name
    sudo add-apt-repository --remove ppa:someppa/ppa
    sudo apt-get autoclean
    

Alternatively you can use Y PPA Manager to disable/remove/purge PPA's (Details at the end of answer).

Preventive Measures:

So how can we avoid this from happening in the first place?

  • Keep Ubuntu Up to date. Ubuntu automatically notifies when updates are available, you can also check for available updates by clicking on Session Indicator in Unity panel:

    Or, Hit Alt+Ctrl+T to open terminal and run following commands:

    sudo apt-get update
    sudo apt-get upgrade

    Update: Synchronizes your list of available packages with the servers in source repositories. Upgrade: Downloads & installs any newer versions of your installed packages.

  • If you decide to add other repositories to sources.list, make sure that the repository is meant to work (and known to work) with Ubuntu. Repositories that are not designed to work with your version of Ubuntu can introduce inconsistencies in your system and might force you to re-install. Also, make sure that you really need to add external repositories as the software package(s) you are looking for may already have been introduced into the official repositories! Source
  • Remove duplicate PPAs. Y PPA Manager (installation guide at the end of answer) can easily scan and remove duplicate PPAs.

    • Hit Alt+F2 and run y-ppa-manager to open Y PPA Manager.
    • Once open, double click or hit Enter on Advanced.
    • In resulting window select Scan and remove duplicate PPAs and click OK.

Getting Help:

When asking for help on Askubuntu or any other help forum, you should include the output of the following commands in your question:

  • sudo apt-get install package-name
    Output of actual error.
  • cat /etc/apt/sources.list
    This will show your sources.list
  • cat /etc/apt/sources.list.d/*
    This will show the list of PPAs (If any).

Additional Sources:


Y PPA Manager: Y PPA Manager is an one stop shop for all of your PPA needs.

Hare are some of it's features:

  • search packages in all Launchpad PPAs
  • list and download packages in a PPA
  • add / remove / purge a PPA
  • backup and restore PPA sources
  • remove duplicate PPA sources

To install Y PPA Manager, open terminal by hitting Alt+Ctrl+T and run following commands:

sudo add-apt-repository ppa:webupd8team/y-ppa-manager
sudo apt-get update
sudo apt-get install y-ppa-manager

Considering the question, apt is broken so, use these command instead

sudo su

and

32 Bit:

mkdir y-ppa-manager && cd y-ppa-manager && wget https://launchpad.net/~webupd8team/+archive/y-ppa-manager/+files/launchpad-getkeys_0.3.2-1~webupd8~oneiric_all.deb && wget https://launchpad.net/~webupd8team/+archive/y-ppa-manager/+files/y-ppa-manager_0.0.8.6-1~webupd8~precise_all.deb && wget https://launchpad.net/~webupd8team/+archive/y-ppa-manager/+files/yad_0.17.1.1-1~webupd8~precise_i386.deb && dpkg -i ./*.deb

64 Bit:

mkdir y-ppa-manager && cd y-ppa-manager && wget https://launchpad.net/~webupd8team/+archive/y-ppa-manager/+files/launchpad-getkeys_0.3.2-1~webupd8~oneiric_all.deb && wget https://launchpad.net/~webupd8team/+archive/y-ppa-manager/+files/y-ppa-manager_0.0.8.6-1~webupd8~precise_all.deb && wget https://launchpad.net/~webupd8team/+archive/y-ppa-manager/+files/yad_0.17.1.1-1~webupd8~precise_amd64.deb && dpkg -i ./*.deb
share|improve this answer
How to install unmet depandancies if apt is broken? – Tachyons May 28 '12 at 1:17
This was a huge help for me... fresh install of Lubuntu 12.04 and couldn't install basic things such as gvim (vim-gtk) or openssh-server. I had tried all sorts of command line options, including literally doing a diff of /etc/apt/sources.list from this machine and another (that worked correctly, running Xubuntu). After following this guide, I found that somehow in software-properties-gtk, the box for the 'main' repos had been unchecked! Problem solved! – memilanuk Jun 1 '12 at 1:11

Note: All commands asked to be run must be run in the terminal, which can be opened by either Ctrl+Alt+T or searching for terminal in the dash.

Is it really broken?

Try running the following command and try to reinstall the software you were trying to install

sudo apt-get update

Pre-Perfomance Steps

Backing up

Back up the following files:

  • /etc/apt/sources.list
  • /var/lib/dpkg/status

To do so, use these commands

sudo cp /etc/apt/sources.list /etc/apt/sources.list.original

and

sudo cp /var/lib/dpkg/status /var/lib/dpkg/status.original

Clearing your apt-cache

apt keeps a cache of recently downloaded packages to save bandwidth when it is required to be installed. This can be counter-productive in some cases

Now, to clean it, you have two options

sudo apt-get clean 

This will remove all cached packages belonging to the folder /var/cache/apt/archives/ and /var/cache/apt/archives/partial except the .lock files. This is recommended

sudo apt-get autoclean

This scans the folders /var/cache/apt/archives/ and /var/cache/apt/archives/partial and checks if the package is still in the repositories and removes the ones that aren't


Fixing dependencies

Using apt's fix-broken mode

sudo apt-get -f install

This will cause apt to scan for missing dependencies and fix them from the repositories

If the output states that nothing new was installed or upgraded, it has failed.


Checking if all required sources are enabled

Type gksu software-properties-gtk and you'll get this window

Make sure all sources are enabled.

next, go to the Other software tab and check if the required PPAs for the software to be installed are there and are enabled. Also, try disabling some PPAs which might be having broken packages

now, run sudo apt-get update

Try installing the software now

Selecting a better server to download from

Type gksu software-properties-gtk and you'll get this window

Click the Download from the Dropdown box and select other

Click Select Best Server

Run sudo apt-get update

Try installing the software

also, try using sudo apt-get install -f


PPA Purge

This is a tool used to purge broken/unwanted ppa's and their applications along with it

To install it, run

sudo apt-get install ppa-purge

But, Considering the question apt is broken so the above command will fail. So use this command

mkdir ppa-purge && cd ppa-purge && wget http://mirror.pnl.gov/ubuntu/pool/universe/p/ppa-purge/ppa-purge_0.2.8+bzr56_all.deb && wget http://mirror.pnl.gov/ubuntu//pool/main/a/aptitude/aptitude_0.6.6-1ubuntu1_i386.deb && sudo dpkg -i ./*.deb

Now use ppa purge

sudo ppa-purge ppa:someppa/ppa  

Y-PPA Manager

Y-PPA Manager is a gui app that helps you manage PPA's and various problems assosiated with it

To install it

sudo add-apt-repository ppa:webupd8team/y-ppa-manager

and

sudo apt-get update

and

sudo apt-get install y-ppa-manager

Considering the question, apt is broken so, use these command instead

sudo su

and

32 Bit:

mkdir y-ppa-manager && cd y-ppa-manager && wget https://launchpad.net/~webupd8team/+archive/y-ppa-manager/+files/launchpad-getkeys_0.3.2-1~webupd8~oneiric_all.deb && wget https://launchpad.net/~webupd8team/+archive/y-ppa-manager/+files/y-ppa-manager_0.0.8.6-1~webupd8~precise_all.deb && wget https://launchpad.net/~webupd8team/+archive/y-ppa-manager/+files/yad_0.17.1.1-1~webupd8~precise_i386.deb && dpkg -i ./*.deb

64 Bit:

mkdir y-ppa-manager && cd y-ppa-manager && wget https://launchpad.net/~webupd8team/+archive/y-ppa-manager/+files/launchpad-getkeys_0.3.2-1~webupd8~oneiric_all.deb && wget https://launchpad.net/~webupd8team/+archive/y-ppa-manager/+files/y-ppa-manager_0.0.8.6-1~webupd8~precise_all.deb && wget https://launchpad.net/~webupd8team/+archive/y-ppa-manager/+files/yad_0.17.1.1-1~webupd8~precise_amd64.deb && dpkg -i ./*.deb

Now type in y-ppa-manager

You'll be presented with this window

Double click on advanced, and you'll get this window

Do the following Tasks outlined in black


Prevention is better than cure

It is better to prevent than to search for this question on AskUbuntu :D

So, here are the guidelines to keep you safe

Keep your system up-to-date

always run the following command regularly

sudo apt-get update&&sudo apt-get upgrade

or, you can always use Update Manager with this command

gksu update-manager

Using only trusted PPA's

Only use PPA's meant to be used on Ubuntu also, only use PPA's with trusted sources. Infact, the package might already be in the ubuntu repositories

Backing up when things are good and restoring it later

For this you need Y-PPA-Manager. The steps to install it are given above.

Run this command to open Y-PPA-Manager

y-ppa-manager

You'll be presented with this window

Double click on advanced, and you'll get this window

Run this:

You'll be asked to save a tar.gz file with a dialog similar to the one below. Save it in another partition or a safe place

Later, when you need to restore it again, follow similar steps and when you get to the advanced dialog,Click on this:

You'll be asked to restore from the previous backup which you saved before with a dialog similar to the one below


All In one Script

Coming soon


Still not working?

Package dependency errors are not always generic and depends on the package to be installed.

If following all the steps given to fix the error does not work for you, you can always ask on Ask Ubuntu

Here are some commands which you need to post the output of

sudo apt-get install packagename

and

cat /etc/apt/sources.list

and

cat /etc/apt/sources.list.d/*

(Thanks to Basharat Sial)

There are also other files/commands that you need the output of that might be error specific, and users will probably prompt you in the comments to post the file/command.

share|improve this answer
   
I would put apt-get update near the top of the list. Sometimes your system has done an update where one newer package has been updated remotely, but one it depends on hasn't finished building yet. Or the version you have in your local cache has been updated. In those cases a simple apt-get update will update your local cache and you can carry on. – Hamish Downer May 27 '12 at 9:45
1  
Top notch answer! It just makes me wish apt and or dpkg had better protections to make sure they didn't get into these stuck broken states, or were better at resolving them. I've had this problem before and was quite frustrated when apt-get install -f didn't fix it. – Jeff Welling May 30 '12 at 3:11
You may also want to include this warning: "Never ever upgrade your system while PPA is enabled, disable them first and then upgrade" Because, if you upgrade to a PPA version and then that PPA becomes dead, it eventually means you're dead. You can't downgrade the whole system to the lower version numbers and can't install something from a standard repo cause the package from std repo has conflicts with the PPA package installed. – Anwar Sep 14 '12 at 3:39

These methods need to be followed whenever you get eror regarding Unmet Dependencies
After following the instructions try installing the software. Atleast one of these methods should work for you

1.Before trying any new command or adding any new ppa try this

> Cleaning up of the apt cache:
sudo apt-get clean
Cleaning up of any unused dependencies:
sudo apt-get autoremove
Updating apt-cache
Sudo apt-get update

This will remove all the cache and will download a fresh cache. This should be done to get fresh cache packages and newer updates.

2.Try sudo apt-get install -f.
It will probably give some suggestions about removing and installing packages, do what seems reasonable.

3.Change the Download Server from Software Sources Because sometimes the files on a server are corrupted.
enter image description here
enter image description here
enter image description here

4.This also happens if you before added an external ppa for the broken dependency.Try removing that ppa by
either typing sudo add-apt-repository --remove ppa:someppa/ppa and then manually removing the ppa installed files/libraries
or
Purging a ppa(this removes the installed files also)

sudo apt-get install ppa-purge   "(a one time install) dont copy this"  
sudo ppa-purge ppa:someppa/ppa  

5.If no 4 is not your case then atleast try to remove the package that is being shown as a broken dependency.Then try again installing.This is reported to have workeed for quite a few people.

6.Always add the stable version of a repository/PPA.
enter image description here

7 Also make sure you have all the official repositories enabled (In Software Sources)

enter image description here
Please do not enable the Proposed Updates as they are meant for testing/developers.
enter image description here


As told by doug

Usually the best 1st step to resolving this is to identify the source of & .
Additionally not noted is that in many, if not most cases, " is to be installed" really means " is installed" and should be tried to be removed if nothing else works. (as in point 5).


Ill keep adding more things ill find to fix unmet dependencies

share|improve this answer
@Ashu One thing you may want to fix--apt-get update does not update the apt cache (which consists of downloaded .deb files and a file that stores information about which .deb files you have stored). It updates the package index files (which consist of information about what packages are available to be downloaded and installed from each available software source). As I said before, apt-get clean does not clean out the same thing that apt-get update updates. See man apt-get for details. – Eliah Kagan May 30 '12 at 19:07

These answers so far are focused on how to automagically resolve such an issue, mostly hoping that it resolves itself, but not focused on understanding how to investigate dependencies. Its important to try things like making sure your package lists are up to date, for you need to make sure a simple update or clearing of the cache doesn't resolve the issue before digging deeper. If everything behind the scenes is working as it should, however, its paramount to learn how to understand dependencies. Sometimes the layers of dependencies can seem overwhelming, but the concept is simple, and key to understanding how software is installed/uninstalled in an Ubuntu system.

I highly recommend aptitude to anyone using a .deb based system like Ubuntu. Its tree structure allows you to easily browse dependencies including recommended and suggested packages, as well as visualize conflicts and unmet dependencies. It is an invaluable tool for when apt-get doesn't offer a simple solution, and for visualizing dependencies in general. (Synaptic is also available in Ubuntu, but I don't find it as intuitive.)

Aptitude also offers a conflict resolver that will walk you through all the possible combinations of installed/removed/upgraded/etc packages to satisfy all requirements without conflict or issue. This can be successful even when apt is unable to find a solution. As a Ubuntu user, situations don't normally arise that require you to investigate why that particular package is being installed, but its almost inevitable as you use the system more.

share|improve this answer
Voted up for mention of Aptitude conflict resolver. There are times when it is essential to use advanced tools like this to determine what the possibilities are and to pinpoint the core conflict. – John S Gruber Jun 1 '12 at 4:34

what is unmet dependencies Error

On Ubuntu packages are the primary way that software is built, deployed, and installed. Very simply, packages are an alternative to downloading, building, and installing software from scratch. They offer a host of advantages in terms of installation, removal, monitoring, and handling interactions between pieces of software over the standard "build from source" model. Ubuntu uses centralized packaging system ,Ie Every package is depends to some other packages .When we installs a package it's dependencies will be installed ,The unmet dependencies error occurs when the the dependencies of the package is not available for installation

Possible causes

1.Computer is not connected to the Internet
2.The repository containing the depandancy package is not enabled
3.Package catalog is not updated
4.The version of the depandancy in the current repository is old
5.Software index is broken
6.The depandancy is not available for ubuntu

Let's TRy to solve it

  1. Connect to the internet :D
  2. Make sure that all the default repositories are enabled

    ->You can easily add them in the Software Center->Edit->Software Sources->Other Sources->Add"

    -> Start the Software Center.

    ->. In the panel go to Edit and select Software Sources.

    edit-software-sources

    ->Make sure all the repositories are checked enter image description here

  3. Update the software catalog

    click on the top right icon and chose update-available Entry in the menu
    enter image description here

and press check button enter image description here

4.type ctrl+alt+t to open terminal and type sudo apt-get install -f

5.Purge the recently added ppa using ppa-purge ppa-purge Install ppa-purge

This program disables a PPA from your Software Sources and reverts your system back to the official Ubuntu packages. You can use this to return your system to normal after testing a new version from a PPA.

Syntax

sudo ppa-purge ppa:<repository-name>/<subdirectory>

Example

sudo ppa-purge ppa:ubuntu-mozilla-daily/ppa
  1. open software center ,and try to install any software , If the following dialog box appeared ,press on the repair button ,and wait

enter image description here

Else type ctrl+alt+t to open terminal and type sudo apt-get install -f and follow the onscreen instructions

If still error occurs, Feel free to to ask it in askbuntu

share|improve this answer
@jrg I already have that in my answer... does every answer need to have the same thing? – Ashu May 24 '12 at 13:14
1  
@Ashu I'm trying to help people to make a canonical answer - and I have to tell everyone, since there is a 500 rep bounty at stake and I don't want to play favorites with helping certain people with their answers but ignoring others. :s – jrg May 24 '12 at 13:18
@jrg ok thanks for letting me know – Ashu May 24 '12 at 13:19

There's a good possibility that my answer might get underrated or something like that, given the number of answers already posted and that bounty set.

However, I am not answering this for the bounty.

I just want to help here, and I wanted to point towards this post in howtogeek sometime ago and it was very helpful to me in solving a similar problem.

Take a look at that, and one of the tools outlined there might be of some help to you:

http://www.howtogeek.com/106526/how-to-resolve-dependencies-while-compiling-software-on-ubuntu/

share|improve this answer

package1 : Depends: package2 (>= 1.8) but 1.7.5-1ubuntu1 is to be installed

Explanation of the message:

  1. In order for your installation to be completed, package1 needs package2.
  2. package2 has to be available in version >= 1.8
  3. The package manager checked all repositories and only found version 1.7.5-1ubuntu1 that could be installed, which it won't do because it is < 1.8

Fix

There is NO single right answer for this question and there is NO simple answer.

There are many scenarios why this can happen and one has to investigate all options and try to solve the preconditions that lead to this error.

Scenario A:

All the repositories that you have access to don't have package2 in version >= 1.8, so you will have to find a repository that does. If you are not able to find a repository with versions >=1.8 then you might have to build and install package2 from source. And then try to install package1.

If you want to know how to build a package from source, check other questions/answers or post a new one.

Scenario B:

The repositories do include package2 in a version >= 1.8 but the package manager still wants to install an older version (1.7.5).

The reason for this may be that the later versions of package2 where built by some newer technology that is not supported by other packages that you already have installed.

This might not be possible to fix at all. You can try to use apt or synaptic and look for all versions of the package2 that are available in the repositories, and try to install a specific version >= 1.8

If you have other incompatible packages and you do this, you will get a list of similar error messages for all the other packages that prevent the installation of package2>=1.8.

In this case, you have a bigger problem. You wanted to install package1, which needs package2 to be >= 1.8, but package2 in version >=1.8 requires package3 to be in version >= 6.7 and you have package3 version 6.3

The thing is that the package manager (APT) tries to solve all these dependencies automatically if it is possible. When it says that it is not possible (and issues a message like in the question), then you should trust it.

If you decide not to trust the package manager and if you are sure that you will not have problems, then you can try to force install the specific needed versions of all packages, one by one, and hope to be OK.

Beware, doing this for system packages can create serious problems. You can lock yourself out of the system, block critical services etc.

Scenario C:

No matter the reasons for the problem, you can always setup for manual compilation and build the needed package and all of it's dependencies in the exact needed versions from source. With this option you can keep what you built in a separate directory and out of the system path so that it will not create conflicts with the system. This is probably the cleanest solution, and sometimes can be faster to do.

Scenario D:

Package manager has access to out-dated information about packages and therefor cannot find a solution. Look in the other answers.

Scenario E:

Package manager has a bug in the dependency resolution code.

You have to investigate that this is really the case, and then issue a bug request.

...

Scenario Z:

There might be other scenarios.

For example package maintainers could have been wrong and did not check that package1 would work even with version of package2 < 1.8 and in the specification they set wrong dependencies.

share|improve this answer

Excellent answers! But today my case seems different from yours. Here's my advice.

Problem:

I failed to install apache2 in ubuntu 10.10.

rick@wen-VirtualBox:~$ sudo apt-get install apache2

Reading package lists... Done

Building dependency tree      

Reading state information... Done

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.

The following information may help to resolve the situation:

The following packages have unmet dependencies:

 apache2 : Depends: apache2-mpm-worker (= 2.2.16-1ubuntu3) but it is not going to be installed or

                    apache2-mpm-prefork (= 2.2.16-1ubuntu3) but it is not going to be installed or

                    apache2-mpm-event (= 2.2.16-1ubuntu3) but it is not going to be installed or

                    apache2-mpm-itk (= 2.2.16-1ubuntu3) but it is not going to be installed

           Depends: apache2.2-common (= 2.2.16-1ubuntu3) but it is not going to be installed

E: Broken packages

Solution:

My way is add the depended package into install list.

If 'sudo apt-get install apache2' failed, try 'sudo apt-get install apache2 apache2.2-common'.

See? apache2.2-common comes from error log of previous step.

At last I found there's a dependency chain like this:

 apache2.2-common <-- apache2.2-bin <-- libaprutil1-ldap <-- libaprutil1

For the first 3 packages, apt-get log told me ' is not going to be installed',

but for the last package, it shows 'libaprutil1-ldap : Depends: libaprutil1 (= 1.3.9+dfsg-3build1) but 1.3.9+dfsg-3ubuntu0.10.10.1 is to be installed'

I have a different version existing in my lib, so:

sudo apt-get remove libaprutil1

sudo apt-get install apache2

Now it's ok.

share|improve this answer

My answer is similar to rick's above.

Using apt-get clean, apt-get autoclean, apt-get autoremove, apt-get upgrade, apt-get update, apt-get -u dist-upgrade, etc. all didn't work for me.

I finally resolved this issue by descending into the dependency tree via apt-get install, illustrated with an example below. In my case, I wanted to install libmagickwand-dev:

apt-get install libmagickwand-dev

I got this error:

The following packages have unmet dependencies:
 libmagickwand-dev : Depends: libmagickcore4-extra (= 8:6.6.9.7-5ubuntu3.2) but it is not going to be installed
                     Depends: libmagickcore-dev (= 8:6.6.9.7-5ubuntu3.2) but it is not going to be installed

So, I ran apt-get install for one of the failing dependencies:

apt-get install libmagickcore-dev

The following packages have unmet dependencies:
 libmagickcore-dev : Depends: libmagickcore4-extra (= 8:6.6.9.7-5ubuntu3.2) but it is not going to be installed
                     Depends: libgraphviz-dev but it is not going to be installed

I descended further down the tree:

apt-get install libgraphviz-dev

with another error:

The following packages have unmet dependencies:
 libgraphviz-dev : Depends: libgvc5 (= 2.26.3-10ubuntu1) but it is not going to be installed

Once more deeper down the tree:

apt-get install libgvc5

Fore some strange reason, this succeeded, and I was able to install the original package I wanted with apt-get install libmagickwand-dev:

Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
  libcdt4 libgd2-xpm libgraph4 libpathplan4
Suggested packages:
  libgd-tools
The following NEW packages will be installed:
  libcdt4 libgd2-xpm libgraph4 libgvc5 libpathplan4
0 upgraded, 5 newly installed, 0 to remove and 2 not upgraded.
Need to get 808 kB of archives.
After this operation, 2,320 kB of additional disk space will be used.
Do you want to continue [Y/n]?
share|improve this answer

After having tried close to every method mentioned in this thread (and others) I was close to giving up. I'd upgraded my Debian Lenny to Squeeze, and I couldn't for the life of me figure out why PHP5, Apache, MySQL etc. didn't want to install. In the end I tried to use

sudo apt-get purge apache2
sudo apt-get purge php5
sudo apt-get purge mysql-server
sudo apt-get clean
sudo apt-get autoremove
sudo apt-get install apache2 php5 mysql-server

..and it worked flawlessly! (Beware, it might destroy your config files, so back them up!)

share|improve this answer

I was getting this error and found that my source of repository is not main, change it to main source resolved this issue.

share|improve this answer
Can you explain in more detail what you did and how you did it? Was the issue that Main was disabled in Software Sources, and you had to enable it? – Eliah Kagan Mar 29 at 12:21

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.