Unable to correct problems, you have held broken packages
up vote
184
down vote
favorite
After upgrading from 10.04 to 12.04 I am trying to install different packages.
For instance ia32-libs and skype (4.0).
When trying to install these, I am getting the 'Unable to correct problems, you have held broken packages' error message.
Output of commands:
sudo apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
After running this:
sudo dpkg --configure -a
foo@foo:~$ sudo apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
apt
edited Aug 23 '14 at 2:30
Braiam
51.1k20134218
asked Nov 28 '12 at 23:48
trond
927273
add a comment |
up vote
184
down vote
favorite
After upgrading from 10.04 to 12.04 I am trying to install different packages.
For instance ia32-libs and skype (4.0).
When trying to install these, I am getting the 'Unable to correct problems, you have held broken packages' error message.
Output of commands:
sudo apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
After running this:
sudo dpkg --configure -a
foo@foo:~$ sudo apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
apt
edited Aug 23 '14 at 2:30
Braiam
51.1k20134218
asked Nov 28 '12 at 23:48
trond
927273
3
It may help if you showed us the command you are actually trying (such assudo apt-get install ia32-libs) and the output from that command. Also, doessudo apt-get dist-upgradeshow any available updates?
– thomasrutter
Nov 29 '12 at 1:59
3
I don't know what's wrong with your question, I don't see any actual error, nor the one you describe in your title.
– Braiam
Sep 10 '14 at 14:20
possible duplicate of How do I resolve unmet dependencies?
– Eliah Kagan
Sep 14 '14 at 15:45
Related: E: Unable to correct problems, you have held broken packages
– Melebius
Jul 25 at 11:18
add a comment |
up vote
184
down vote
favorite
up vote
184
down vote
favorite
After upgrading from 10.04 to 12.04 I am trying to install different packages.
For instance ia32-libs and skype (4.0).
When trying to install these, I am getting the 'Unable to correct problems, you have held broken packages' error message.
Output of commands:
sudo apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
After running this:
sudo dpkg --configure -a
foo@foo:~$ sudo apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
apt
edited Aug 23 '14 at 2:30
Braiam
51.1k20134218
asked Nov 28 '12 at 23:48
trond
927273
After upgrading from 10.04 to 12.04 I am trying to install different packages.
For instance ia32-libs and skype (4.0).
When trying to install these, I am getting the 'Unable to correct problems, you have held broken packages' error message.
Output of commands:
sudo apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
After running this:
sudo dpkg --configure -a
foo@foo:~$ sudo apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
apt
apt
edited Aug 23 '14 at 2:30
Braiam
51.1k20134218
asked Nov 28 '12 at 23:48
trond
927273
edited Aug 23 '14 at 2:30
Braiam
51.1k20134218
asked Nov 28 '12 at 23:48
trond
927273
edited Aug 23 '14 at 2:30
Braiam
51.1k20134218
edited Aug 23 '14 at 2:30
Braiam
51.1k20134218
edited Aug 23 '14 at 2:30
Braiam
51.1k20134218
51.1k20134218
asked Nov 28 '12 at 23:48
trond
927273
asked Nov 28 '12 at 23:48
trond
927273
asked Nov 28 '12 at 23:48
trond
927273
927273
3
It may help if you showed us the command you are actually trying (such assudo apt-get install ia32-libs) and the output from that command. Also, doessudo apt-get dist-upgradeshow any available updates?
– thomasrutter
Nov 29 '12 at 1:59
3
I don't know what's wrong with your question, I don't see any actual error, nor the one you describe in your title.
– Braiam
Sep 10 '14 at 14:20
possible duplicate of How do I resolve unmet dependencies?
– Eliah Kagan
Sep 14 '14 at 15:45
Related: E: Unable to correct problems, you have held broken packages
– Melebius
Jul 25 at 11:18
add a comment |
3
It may help if you showed us the command you are actually trying (such assudo apt-get install ia32-libs) and the output from that command. Also, doessudo apt-get dist-upgradeshow any available updates?
– thomasrutter
Nov 29 '12 at 1:59
3
I don't know what's wrong with your question, I don't see any actual error, nor the one you describe in your title.
– Braiam
Sep 10 '14 at 14:20
possible duplicate of How do I resolve unmet dependencies?
– Eliah Kagan
Sep 14 '14 at 15:45
Related: E: Unable to correct problems, you have held broken packages
– Melebius
Jul 25 at 11:18
3
3
It may help if you showed us the command you are actually trying (such as
sudo apt-get install ia32-libs) and the output from that command. Also, does sudo apt-get dist-upgrade show any available updates?– thomasrutter
Nov 29 '12 at 1:59
It may help if you showed us the command you are actually trying (such as
sudo apt-get install ia32-libs) and the output from that command. Also, does sudo apt-get dist-upgrade show any available updates?– thomasrutter
Nov 29 '12 at 1:59
3
3
I don't know what's wrong with your question, I don't see any actual error, nor the one you describe in your title.
– Braiam
Sep 10 '14 at 14:20
I don't know what's wrong with your question, I don't see any actual error, nor the one you describe in your title.
– Braiam
Sep 10 '14 at 14:20
possible duplicate of How do I resolve unmet dependencies?
– Eliah Kagan
Sep 14 '14 at 15:45
possible duplicate of How do I resolve unmet dependencies?
– Eliah Kagan
Sep 14 '14 at 15:45
Related: E: Unable to correct problems, you have held broken packages
– Melebius
Jul 25 at 11:18
Related: E: Unable to correct problems, you have held broken packages
– Melebius
Jul 25 at 11:18
add a comment |
7 Answers
7
active
oldest
votes
up vote
203
down vote
That particular error message may indicate that you have held packages, but it may also indicate a different problem.
You can get a list of actual held packages with:
dpkg --get-selections | grep hold
If there are none, or none look related, then it's probably something else. Check carefully the output of the command you were trying when you got the error message, as there may be other clues in the full output from that command, aside from the error message.
Another method of troubleshooting may be to use aptitude rather than apt-get to try to install your package:
sudo aptitude install <packagename>
Aptitude will give up less easily, and will attempt to find solutions which may involve modifying other packages. It may give you more explanation of the problem and options for fixing it.
Occasionally aptitude will be too eager to remove or downgrade large numbers of packages to satisfy your request, in which case retrying with -f changes its priorities and helps it come up with solutions that involve removing/downgrading fewer packages even if it means not all changes you requested can go ahead:
sudo aptitude -f install <packagename>
answered Nov 29 '12 at 1:58
thomasrutter
26.3k46288
5
Any idea how to unhold a package? :-)
– Eugene van der Merwe
Apr 17 '13 at 14:24
6
That is a separate question.
– thomasrutter
Apr 20 '13 at 13:58
52
Aptitude was more helpful to me than apt-get, thanks for the hint.
– szx
Oct 27 '13 at 15:20
7
One thing to note is that aptitude may make it easier to do more damage to your system. For example, if apt-get fails to install something because of conflicting dependencies it will give up. However, aptitude might offer to go ahead, but uninstall a whole bunch of other packages in order to satisfy those conflicts - or even downgrade packages. You simply have to be aware of what it's suggesting and proceed only if it is a good idea.
– thomasrutter
Mar 12 '14 at 3:23
4
The "on hold" packages has nothing to do with the message, just that the conflict was avoided by holding them down (not installing, upgrading, downgrading, or removing).
– Braiam
Aug 23 '14 at 2:50
|
show 6 more comments
up vote
25
down vote
That happened to me too. All I did was sudo apt-get update and that fixed my issue. Good luck.
answered Aug 27 '13 at 2:43
user2292711
37532
add a comment |
up vote
8
down vote
I had a similar scenario in a fresh install of 14.04, with no files listed in dpkg --get-selections | grep hold, and no joy after sudo apt-get update.
What did fix it for me was a simple
sudo apt-get autoremove
When I tried to reinstall the failing package it worked fine. Yay!
answered Jul 27 '15 at 13:41
yochannah
240511
add a comment |
up vote
7
down vote
I ran into a similar scenario regarding missing dependencies. In my case I was trying to install curl on ubuntu saucy salamander 13.10...
The error stated that the dependency required an earlier version of the curl3 library.
I was able to degrade to the earlier version by trying to install curl using aptitude.
When it noted the missing dependency, and the reason (required an earlier version of the library file), it gave me several options in how to respond... y//n/q
Y would have aborted the install, N would look for another option, and Q would simply quit and do nothing more, leaving a broken package.
I selected N, and it gave me the option to downgrade the library file to an earlier version. So that's what I did, and curl finished installing with no more errors.
- I may look into upgrading the library file again after the install, but hey, so far so good.
edited Mar 2 '14 at 9:29
v2r
6,161113848
answered Mar 2 '14 at 6:53
Peopleunit
8711
add a comment |
up vote
4
down vote
Had the same problem, I ran that package check command from the other answer (dpkg --get-selections | grep hold)
and saw
tomcat7 deinstall
tomcat7-common install
so I used "apt-get remove tomcat7-common"
Then I could install Tomcat 6 (I was removing Tomcat 7 and installing Tomcat 6 as you do).
edited Aug 17 '14 at 20:57
belacqua
15.6k1472103
answered Oct 3 '13 at 11:03
Nollaig
6511
The "on hold" packages has nothing to do with the message, just that the conflict was avoided by holding them down (not installing, upgrading, downgrading, or removing)
– Braiam
Aug 23 '14 at 2:51
add the flag purge: apt-get remove --purge packet
– Sergio Abreu
Jan 5 '17 at 11:22
add a comment |
up vote
0
down vote
For me, none of the above worked because my system wasn't updated. I did
Home Key > Software Updater > Install
and updated my system; afterwards, I could install my package normally with apt.
answered May 25 at 14:01
nathangeorge1
132
add a comment |
up vote
0
down vote
These are some fast and easy ways to fix the you have held broken packages error.
Open your sources.list file in
/etc/apt/sources.listand check that there aren't any software sources for a different Ubuntu release than the Ubuntu release that you are currently using. If you find any incorrect release lines in sources.list, open the sources.list file withsudoedit /etc/apt/sources.list, comment out the incorrect lines in sources.list by preceding them with a#character, save the sources.list file, and runsudo apt updateto update the list of available software packages.
Select the Fix Broken Packages option in Synaptic package manager. Run the following command to install Synaptic.
sudo apt install synaptic
Open Synaptic and in Synaptic select Edit -> Fix Broken Packages and then repeat Edit -> Fix Broken Packages a second time.
If you get this error message:
Try 'apt-get -f install' with no packages (or specify a solution)
Run the following command:
sudo apt-get -f install
answered Oct 8 at 11:13
karel
55.6k11124141
add a comment |
protected by Braiam Aug 23 '14 at 3:05
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
7 Answers
7
active
oldest
votes
7 Answers
7
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
203
down vote
That particular error message may indicate that you have held packages, but it may also indicate a different problem.
You can get a list of actual held packages with:
dpkg --get-selections | grep hold
If there are none, or none look related, then it's probably something else. Check carefully the output of the command you were trying when you got the error message, as there may be other clues in the full output from that command, aside from the error message.
Another method of troubleshooting may be to use aptitude rather than apt-get to try to install your package:
sudo aptitude install <packagename>
Aptitude will give up less easily, and will attempt to find solutions which may involve modifying other packages. It may give you more explanation of the problem and options for fixing it.
Occasionally aptitude will be too eager to remove or downgrade large numbers of packages to satisfy your request, in which case retrying with -f changes its priorities and helps it come up with solutions that involve removing/downgrading fewer packages even if it means not all changes you requested can go ahead:
sudo aptitude -f install <packagename>
answered Nov 29 '12 at 1:58
thomasrutter
26.3k46288
5
Any idea how to unhold a package? :-)
– Eugene van der Merwe
Apr 17 '13 at 14:24
6
That is a separate question.
– thomasrutter
Apr 20 '13 at 13:58
52
Aptitude was more helpful to me than apt-get, thanks for the hint.
– szx
Oct 27 '13 at 15:20
7
One thing to note is that aptitude may make it easier to do more damage to your system. For example, if apt-get fails to install something because of conflicting dependencies it will give up. However, aptitude might offer to go ahead, but uninstall a whole bunch of other packages in order to satisfy those conflicts - or even downgrade packages. You simply have to be aware of what it's suggesting and proceed only if it is a good idea.
– thomasrutter
Mar 12 '14 at 3:23
4
The "on hold" packages has nothing to do with the message, just that the conflict was avoided by holding them down (not installing, upgrading, downgrading, or removing).
– Braiam
Aug 23 '14 at 2:50
|
show 6 more comments
up vote
203
down vote
That particular error message may indicate that you have held packages, but it may also indicate a different problem.
You can get a list of actual held packages with:
dpkg --get-selections | grep hold
If there are none, or none look related, then it's probably something else. Check carefully the output of the command you were trying when you got the error message, as there may be other clues in the full output from that command, aside from the error message.
Another method of troubleshooting may be to use aptitude rather than apt-get to try to install your package:
sudo aptitude install <packagename>
Aptitude will give up less easily, and will attempt to find solutions which may involve modifying other packages. It may give you more explanation of the problem and options for fixing it.
Occasionally aptitude will be too eager to remove or downgrade large numbers of packages to satisfy your request, in which case retrying with -f changes its priorities and helps it come up with solutions that involve removing/downgrading fewer packages even if it means not all changes you requested can go ahead:
sudo aptitude -f install <packagename>
answered Nov 29 '12 at 1:58
thomasrutter
26.3k46288
5
Any idea how to unhold a package? :-)
– Eugene van der Merwe
Apr 17 '13 at 14:24
6
That is a separate question.
– thomasrutter
Apr 20 '13 at 13:58
52
Aptitude was more helpful to me than apt-get, thanks for the hint.
– szx
Oct 27 '13 at 15:20
7
One thing to note is that aptitude may make it easier to do more damage to your system. For example, if apt-get fails to install something because of conflicting dependencies it will give up. However, aptitude might offer to go ahead, but uninstall a whole bunch of other packages in order to satisfy those conflicts - or even downgrade packages. You simply have to be aware of what it's suggesting and proceed only if it is a good idea.
– thomasrutter
Mar 12 '14 at 3:23
4
The "on hold" packages has nothing to do with the message, just that the conflict was avoided by holding them down (not installing, upgrading, downgrading, or removing).
– Braiam
Aug 23 '14 at 2:50
|
show 6 more comments
up vote
203
down vote
up vote
203
down vote
That particular error message may indicate that you have held packages, but it may also indicate a different problem.
You can get a list of actual held packages with:
dpkg --get-selections | grep hold
If there are none, or none look related, then it's probably something else. Check carefully the output of the command you were trying when you got the error message, as there may be other clues in the full output from that command, aside from the error message.
Another method of troubleshooting may be to use aptitude rather than apt-get to try to install your package:
sudo aptitude install <packagename>
Aptitude will give up less easily, and will attempt to find solutions which may involve modifying other packages. It may give you more explanation of the problem and options for fixing it.
Occasionally aptitude will be too eager to remove or downgrade large numbers of packages to satisfy your request, in which case retrying with -f changes its priorities and helps it come up with solutions that involve removing/downgrading fewer packages even if it means not all changes you requested can go ahead:
sudo aptitude -f install <packagename>
answered Nov 29 '12 at 1:58
thomasrutter
26.3k46288
That particular error message may indicate that you have held packages, but it may also indicate a different problem.
You can get a list of actual held packages with:
dpkg --get-selections | grep hold
If there are none, or none look related, then it's probably something else. Check carefully the output of the command you were trying when you got the error message, as there may be other clues in the full output from that command, aside from the error message.
Another method of troubleshooting may be to use aptitude rather than apt-get to try to install your package:
sudo aptitude install <packagename>
Aptitude will give up less easily, and will attempt to find solutions which may involve modifying other packages. It may give you more explanation of the problem and options for fixing it.
Occasionally aptitude will be too eager to remove or downgrade large numbers of packages to satisfy your request, in which case retrying with -f changes its priorities and helps it come up with solutions that involve removing/downgrading fewer packages even if it means not all changes you requested can go ahead:
sudo aptitude -f install <packagename>
answered Nov 29 '12 at 1:58
thomasrutter
26.3k46288
edited Feb 10 at 12:09
answered Nov 29 '12 at 1:58
thomasrutter
26.3k46288
answered Nov 29 '12 at 1:58
thomasrutter
26.3k46288
answered Nov 29 '12 at 1:58
thomasrutter
26.3k46288
26.3k46288
5
Any idea how to unhold a package? :-)
– Eugene van der Merwe
Apr 17 '13 at 14:24
6
That is a separate question.
– thomasrutter
Apr 20 '13 at 13:58
52
Aptitude was more helpful to me than apt-get, thanks for the hint.
– szx
Oct 27 '13 at 15:20
7
One thing to note is that aptitude may make it easier to do more damage to your system. For example, if apt-get fails to install something because of conflicting dependencies it will give up. However, aptitude might offer to go ahead, but uninstall a whole bunch of other packages in order to satisfy those conflicts - or even downgrade packages. You simply have to be aware of what it's suggesting and proceed only if it is a good idea.
– thomasrutter
Mar 12 '14 at 3:23
4
The "on hold" packages has nothing to do with the message, just that the conflict was avoided by holding them down (not installing, upgrading, downgrading, or removing).
– Braiam
Aug 23 '14 at 2:50
|
show 6 more comments
5
Any idea how to unhold a package? :-)
– Eugene van der Merwe
Apr 17 '13 at 14:24
6
That is a separate question.
– thomasrutter
Apr 20 '13 at 13:58
52
Aptitude was more helpful to me than apt-get, thanks for the hint.
– szx
Oct 27 '13 at 15:20
7
One thing to note is that aptitude may make it easier to do more damage to your system. For example, if apt-get fails to install something because of conflicting dependencies it will give up. However, aptitude might offer to go ahead, but uninstall a whole bunch of other packages in order to satisfy those conflicts - or even downgrade packages. You simply have to be aware of what it's suggesting and proceed only if it is a good idea.
– thomasrutter
Mar 12 '14 at 3:23
4
The "on hold" packages has nothing to do with the message, just that the conflict was avoided by holding them down (not installing, upgrading, downgrading, or removing).
– Braiam
Aug 23 '14 at 2:50
5
5
Any idea how to unhold a package? :-)
– Eugene van der Merwe
Apr 17 '13 at 14:24
Any idea how to unhold a package? :-)
– Eugene van der Merwe
Apr 17 '13 at 14:24
6
6
That is a separate question.
– thomasrutter
Apr 20 '13 at 13:58
That is a separate question.
– thomasrutter
Apr 20 '13 at 13:58
52
52
Aptitude was more helpful to me than apt-get, thanks for the hint.
– szx
Oct 27 '13 at 15:20
Aptitude was more helpful to me than apt-get, thanks for the hint.
– szx
Oct 27 '13 at 15:20
7
7
One thing to note is that aptitude may make it easier to do more damage to your system. For example, if apt-get fails to install something because of conflicting dependencies it will give up. However, aptitude might offer to go ahead, but uninstall a whole bunch of other packages in order to satisfy those conflicts - or even downgrade packages. You simply have to be aware of what it's suggesting and proceed only if it is a good idea.
– thomasrutter
Mar 12 '14 at 3:23
One thing to note is that aptitude may make it easier to do more damage to your system. For example, if apt-get fails to install something because of conflicting dependencies it will give up. However, aptitude might offer to go ahead, but uninstall a whole bunch of other packages in order to satisfy those conflicts - or even downgrade packages. You simply have to be aware of what it's suggesting and proceed only if it is a good idea.
– thomasrutter
Mar 12 '14 at 3:23
4
4
The "on hold" packages has nothing to do with the message, just that the conflict was avoided by holding them down (not installing, upgrading, downgrading, or removing).
– Braiam
Aug 23 '14 at 2:50
The "on hold" packages has nothing to do with the message, just that the conflict was avoided by holding them down (not installing, upgrading, downgrading, or removing).
– Braiam
Aug 23 '14 at 2:50
|
show 6 more comments
up vote
25
down vote
That happened to me too. All I did was sudo apt-get update and that fixed my issue. Good luck.
answered Aug 27 '13 at 2:43
user2292711
37532
add a comment |
up vote
25
down vote
That happened to me too. All I did was sudo apt-get update and that fixed my issue. Good luck.
answered Aug 27 '13 at 2:43
user2292711
37532
add a comment |
up vote
25
down vote
up vote
25
down vote
That happened to me too. All I did was sudo apt-get update and that fixed my issue. Good luck.
answered Aug 27 '13 at 2:43
user2292711
37532
That happened to me too. All I did was sudo apt-get update and that fixed my issue. Good luck.
answered Aug 27 '13 at 2:43
user2292711
37532
answered Aug 27 '13 at 2:43
user2292711
37532
answered Aug 27 '13 at 2:43
user2292711
37532
answered Aug 27 '13 at 2:43
user2292711
37532
37532
add a comment |
add a comment |
up vote
8
down vote
I had a similar scenario in a fresh install of 14.04, with no files listed in dpkg --get-selections | grep hold, and no joy after sudo apt-get update.
What did fix it for me was a simple
sudo apt-get autoremove
When I tried to reinstall the failing package it worked fine. Yay!
answered Jul 27 '15 at 13:41
yochannah
240511
add a comment |
up vote
8
down vote
I had a similar scenario in a fresh install of 14.04, with no files listed in dpkg --get-selections | grep hold, and no joy after sudo apt-get update.
What did fix it for me was a simple
sudo apt-get autoremove
When I tried to reinstall the failing package it worked fine. Yay!
answered Jul 27 '15 at 13:41
yochannah
240511
add a comment |
up vote
8
down vote
up vote
8
down vote
I had a similar scenario in a fresh install of 14.04, with no files listed in dpkg --get-selections | grep hold, and no joy after sudo apt-get update.
What did fix it for me was a simple
sudo apt-get autoremove
When I tried to reinstall the failing package it worked fine. Yay!
answered Jul 27 '15 at 13:41
yochannah
240511
I had a similar scenario in a fresh install of 14.04, with no files listed in dpkg --get-selections | grep hold, and no joy after sudo apt-get update.
What did fix it for me was a simple
sudo apt-get autoremove
When I tried to reinstall the failing package it worked fine. Yay!
answered Jul 27 '15 at 13:41
yochannah
240511
answered Jul 27 '15 at 13:41
yochannah
240511
answered Jul 27 '15 at 13:41
yochannah
240511
answered Jul 27 '15 at 13:41
yochannah
240511
240511
add a comment |
add a comment |
up vote
7
down vote
I ran into a similar scenario regarding missing dependencies. In my case I was trying to install curl on ubuntu saucy salamander 13.10...
The error stated that the dependency required an earlier version of the curl3 library.
I was able to degrade to the earlier version by trying to install curl using aptitude.
When it noted the missing dependency, and the reason (required an earlier version of the library file), it gave me several options in how to respond... y//n/q
Y would have aborted the install, N would look for another option, and Q would simply quit and do nothing more, leaving a broken package.
I selected N, and it gave me the option to downgrade the library file to an earlier version. So that's what I did, and curl finished installing with no more errors.
- I may look into upgrading the library file again after the install, but hey, so far so good.
edited Mar 2 '14 at 9:29
v2r
6,161113848
answered Mar 2 '14 at 6:53
Peopleunit
8711
add a comment |
up vote
7
down vote
I ran into a similar scenario regarding missing dependencies. In my case I was trying to install curl on ubuntu saucy salamander 13.10...
The error stated that the dependency required an earlier version of the curl3 library.
I was able to degrade to the earlier version by trying to install curl using aptitude.
When it noted the missing dependency, and the reason (required an earlier version of the library file), it gave me several options in how to respond... y//n/q
Y would have aborted the install, N would look for another option, and Q would simply quit and do nothing more, leaving a broken package.
I selected N, and it gave me the option to downgrade the library file to an earlier version. So that's what I did, and curl finished installing with no more errors.
- I may look into upgrading the library file again after the install, but hey, so far so good.
edited Mar 2 '14 at 9:29
v2r
6,161113848
answered Mar 2 '14 at 6:53
Peopleunit
8711
add a comment |
up vote
7
down vote
up vote
7
down vote
I ran into a similar scenario regarding missing dependencies. In my case I was trying to install curl on ubuntu saucy salamander 13.10...
The error stated that the dependency required an earlier version of the curl3 library.
I was able to degrade to the earlier version by trying to install curl using aptitude.
When it noted the missing dependency, and the reason (required an earlier version of the library file), it gave me several options in how to respond... y//n/q
Y would have aborted the install, N would look for another option, and Q would simply quit and do nothing more, leaving a broken package.
I selected N, and it gave me the option to downgrade the library file to an earlier version. So that's what I did, and curl finished installing with no more errors.
- I may look into upgrading the library file again after the install, but hey, so far so good.
edited Mar 2 '14 at 9:29
v2r
6,161113848
answered Mar 2 '14 at 6:53
Peopleunit
8711
I ran into a similar scenario regarding missing dependencies. In my case I was trying to install curl on ubuntu saucy salamander 13.10...
The error stated that the dependency required an earlier version of the curl3 library.
I was able to degrade to the earlier version by trying to install curl using aptitude.
When it noted the missing dependency, and the reason (required an earlier version of the library file), it gave me several options in how to respond... y//n/q
Y would have aborted the install, N would look for another option, and Q would simply quit and do nothing more, leaving a broken package.
I selected N, and it gave me the option to downgrade the library file to an earlier version. So that's what I did, and curl finished installing with no more errors.
- I may look into upgrading the library file again after the install, but hey, so far so good.
edited Mar 2 '14 at 9:29
v2r
6,161113848
answered Mar 2 '14 at 6:53
Peopleunit
8711
edited Mar 2 '14 at 9:29
v2r
6,161113848
edited Mar 2 '14 at 9:29
v2r
6,161113848
edited Mar 2 '14 at 9:29
v2r
6,161113848
6,161113848
answered Mar 2 '14 at 6:53
Peopleunit
8711
answered Mar 2 '14 at 6:53
Peopleunit
8711
answered Mar 2 '14 at 6:53
Peopleunit
8711
8711
add a comment |
add a comment |
up vote
4
down vote
Had the same problem, I ran that package check command from the other answer (dpkg --get-selections | grep hold)
and saw
tomcat7 deinstall
tomcat7-common install
so I used "apt-get remove tomcat7-common"
Then I could install Tomcat 6 (I was removing Tomcat 7 and installing Tomcat 6 as you do).
edited Aug 17 '14 at 20:57
belacqua
15.6k1472103
answered Oct 3 '13 at 11:03
Nollaig
6511
The "on hold" packages has nothing to do with the message, just that the conflict was avoided by holding them down (not installing, upgrading, downgrading, or removing)
– Braiam
Aug 23 '14 at 2:51
add the flag purge: apt-get remove --purge packet
– Sergio Abreu
Jan 5 '17 at 11:22
add a comment |
up vote
4
down vote
Had the same problem, I ran that package check command from the other answer (dpkg --get-selections | grep hold)
and saw
tomcat7 deinstall
tomcat7-common install
so I used "apt-get remove tomcat7-common"
Then I could install Tomcat 6 (I was removing Tomcat 7 and installing Tomcat 6 as you do).
edited Aug 17 '14 at 20:57
belacqua
15.6k1472103
answered Oct 3 '13 at 11:03
Nollaig
6511
The "on hold" packages has nothing to do with the message, just that the conflict was avoided by holding them down (not installing, upgrading, downgrading, or removing)
– Braiam
Aug 23 '14 at 2:51
add the flag purge: apt-get remove --purge packet
– Sergio Abreu
Jan 5 '17 at 11:22
add a comment |
up vote
4
down vote
up vote
4
down vote
Had the same problem, I ran that package check command from the other answer (dpkg --get-selections | grep hold)
and saw
tomcat7 deinstall
tomcat7-common install
so I used "apt-get remove tomcat7-common"
Then I could install Tomcat 6 (I was removing Tomcat 7 and installing Tomcat 6 as you do).
edited Aug 17 '14 at 20:57
belacqua
15.6k1472103
answered Oct 3 '13 at 11:03
Nollaig
6511
Had the same problem, I ran that package check command from the other answer (dpkg --get-selections | grep hold)
and saw
tomcat7 deinstall
tomcat7-common install
so I used "apt-get remove tomcat7-common"
Then I could install Tomcat 6 (I was removing Tomcat 7 and installing Tomcat 6 as you do).
edited Aug 17 '14 at 20:57
belacqua
15.6k1472103
answered Oct 3 '13 at 11:03
Nollaig
6511
edited Aug 17 '14 at 20:57
belacqua
15.6k1472103
edited Aug 17 '14 at 20:57
belacqua
15.6k1472103
edited Aug 17 '14 at 20:57
belacqua
15.6k1472103
15.6k1472103
answered Oct 3 '13 at 11:03
Nollaig
6511
answered Oct 3 '13 at 11:03
Nollaig
6511
answered Oct 3 '13 at 11:03
Nollaig
6511
6511
The "on hold" packages has nothing to do with the message, just that the conflict was avoided by holding them down (not installing, upgrading, downgrading, or removing)
– Braiam
Aug 23 '14 at 2:51
add the flag purge: apt-get remove --purge packet
– Sergio Abreu
Jan 5 '17 at 11:22
add a comment |
The "on hold" packages has nothing to do with the message, just that the conflict was avoided by holding them down (not installing, upgrading, downgrading, or removing)
– Braiam
Aug 23 '14 at 2:51
add the flag purge: apt-get remove --purge packet
– Sergio Abreu
Jan 5 '17 at 11:22
The "on hold" packages has nothing to do with the message, just that the conflict was avoided by holding them down (not installing, upgrading, downgrading, or removing)
– Braiam
Aug 23 '14 at 2:51
The "on hold" packages has nothing to do with the message, just that the conflict was avoided by holding them down (not installing, upgrading, downgrading, or removing)
– Braiam
Aug 23 '14 at 2:51
add the flag purge: apt-get remove --purge packet
– Sergio Abreu
Jan 5 '17 at 11:22
add the flag purge: apt-get remove --purge packet
– Sergio Abreu
Jan 5 '17 at 11:22
add a comment |
up vote
0
down vote
For me, none of the above worked because my system wasn't updated. I did
Home Key > Software Updater > Install
and updated my system; afterwards, I could install my package normally with apt.
answered May 25 at 14:01
nathangeorge1
132
add a comment |
up vote
0
down vote
For me, none of the above worked because my system wasn't updated. I did
Home Key > Software Updater > Install
and updated my system; afterwards, I could install my package normally with apt.
answered May 25 at 14:01
nathangeorge1
132
add a comment |
up vote
0
down vote
up vote
0
down vote
For me, none of the above worked because my system wasn't updated. I did
Home Key > Software Updater > Install
and updated my system; afterwards, I could install my package normally with apt.
answered May 25 at 14:01
nathangeorge1
132
For me, none of the above worked because my system wasn't updated. I did
Home Key > Software Updater > Install
and updated my system; afterwards, I could install my package normally with apt.
answered May 25 at 14:01
nathangeorge1
132
answered May 25 at 14:01
nathangeorge1
132
answered May 25 at 14:01
nathangeorge1
132
answered May 25 at 14:01
nathangeorge1
132
132
add a comment |
add a comment |
up vote
0
down vote
These are some fast and easy ways to fix the you have held broken packages error.
Open your sources.list file in
/etc/apt/sources.listand check that there aren't any software sources for a different Ubuntu release than the Ubuntu release that you are currently using. If you find any incorrect release lines in sources.list, open the sources.list file withsudoedit /etc/apt/sources.list, comment out the incorrect lines in sources.list by preceding them with a#character, save the sources.list file, and runsudo apt updateto update the list of available software packages.
Select the Fix Broken Packages option in Synaptic package manager. Run the following command to install Synaptic.
sudo apt install synaptic
Open Synaptic and in Synaptic select Edit -> Fix Broken Packages and then repeat Edit -> Fix Broken Packages a second time.
If you get this error message:
Try 'apt-get -f install' with no packages (or specify a solution)
Run the following command:
sudo apt-get -f install
answered Oct 8 at 11:13
karel
55.6k11124141
add a comment |
up vote
0
down vote
These are some fast and easy ways to fix the you have held broken packages error.
Open your sources.list file in
/etc/apt/sources.listand check that there aren't any software sources for a different Ubuntu release than the Ubuntu release that you are currently using. If you find any incorrect release lines in sources.list, open the sources.list file withsudoedit /etc/apt/sources.list, comment out the incorrect lines in sources.list by preceding them with a#character, save the sources.list file, and runsudo apt updateto update the list of available software packages.
Select the Fix Broken Packages option in Synaptic package manager. Run the following command to install Synaptic.
sudo apt install synaptic
Open Synaptic and in Synaptic select Edit -> Fix Broken Packages and then repeat Edit -> Fix Broken Packages a second time.
If you get this error message:
Try 'apt-get -f install' with no packages (or specify a solution)
Run the following command:
sudo apt-get -f install
answered Oct 8 at 11:13
karel
55.6k11124141
add a comment |
up vote
0
down vote
up vote
0
down vote
These are some fast and easy ways to fix the you have held broken packages error.
Open your sources.list file in
/etc/apt/sources.listand check that there aren't any software sources for a different Ubuntu release than the Ubuntu release that you are currently using. If you find any incorrect release lines in sources.list, open the sources.list file withsudoedit /etc/apt/sources.list, comment out the incorrect lines in sources.list by preceding them with a#character, save the sources.list file, and runsudo apt updateto update the list of available software packages.
Select the Fix Broken Packages option in Synaptic package manager. Run the following command to install Synaptic.
sudo apt install synaptic
Open Synaptic and in Synaptic select Edit -> Fix Broken Packages and then repeat Edit -> Fix Broken Packages a second time.
If you get this error message:
Try 'apt-get -f install' with no packages (or specify a solution)
Run the following command:
sudo apt-get -f install
answered Oct 8 at 11:13
karel
55.6k11124141
These are some fast and easy ways to fix the you have held broken packages error.
Open your sources.list file in
/etc/apt/sources.listand check that there aren't any software sources for a different Ubuntu release than the Ubuntu release that you are currently using. If you find any incorrect release lines in sources.list, open the sources.list file withsudoedit /etc/apt/sources.list, comment out the incorrect lines in sources.list by preceding them with a#character, save the sources.list file, and runsudo apt updateto update the list of available software packages.
Select the Fix Broken Packages option in Synaptic package manager. Run the following command to install Synaptic.
sudo apt install synaptic
Open Synaptic and in Synaptic select Edit -> Fix Broken Packages and then repeat Edit -> Fix Broken Packages a second time.
If you get this error message:
Try 'apt-get -f install' with no packages (or specify a solution)
Run the following command:
sudo apt-get -f install
answered Oct 8 at 11:13
karel
55.6k11124141
edited Oct 21 at 16:56
answered Oct 8 at 11:13
karel
55.6k11124141
answered Oct 8 at 11:13
karel
55.6k11124141
answered Oct 8 at 11:13
karel
55.6k11124141
55.6k11124141
add a comment |
add a comment |
protected by Braiam Aug 23 '14 at 3:05
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
3
It may help if you showed us the command you are actually trying (such as
sudo apt-get install ia32-libs) and the output from that command. Also, doessudo apt-get dist-upgradeshow any available updates?– thomasrutter
Nov 29 '12 at 1:59
3
I don't know what's wrong with your question, I don't see any actual error, nor the one you describe in your title.
– Braiam
Sep 10 '14 at 14:20
possible duplicate of How do I resolve unmet dependencies?
– Eliah Kagan
Sep 14 '14 at 15:45
Related: E: Unable to correct problems, you have held broken packages
– Melebius
Jul 25 at 11:18