Unable to correct problems, you have held broken packagesnpm : Depends: node-gyp (>= 0.10.9) but it is not going to be installedUnable to install nvidia drivers on Ubuntu 18.04Unable to install libjack-devInstalling 32 bit libraries on 64 system, libz.so.1 missingDependency issue on installing gstreamer on Ubuntu 18.04mysql-server:Depends: mysql-server-5.5 but it is not going to be installedUbuntu 12.04 LTS server - build-essential install not possibleHow to install wine in ubuntu 16.04?Unable to Install blender in Ubuntu 18.04Broken packages error when installing libdvd-pkgProblem installing apache2Help installing wineWhy doesn't adding the Kubuntu backports ppa allow me to get the latest KDE version?Unable to locate package mysql-server

Delete selection without gradient effect

Exporting multiple point shapefiles from one file using QGIS

Retracting Recommendation Letters

Why do amateur radio operators call an RF choke a balun?

Do Adventure cards count towards "number of instant and sorcery cards in your graveyard"?

Is gaining 1 AC in exchange for disadvantage on Perception checks a balanced trade?

Are Generation Ships inherently implausible?

Did "2001: A Space Odyssey" make any reference to the names of companies, or show any evidence of the existence of advertisements?

Is it possible to stall a plane so badly that the nose refuses to go down due to lack of airspeed?

Template not provided using create-react-app

What visual cues distinguish the different floors on The Big Bang Theory?

What should I do about a new employee who didn't mention their second job or planned leave?

Is the spacetime interval a tensor?

"Don't invest now because the market is high"

Typing "PartOf" in excel changes automatically to part of?

Prefix all commands in shell

Why try to impeach Trump now?

Do insurance rates depend on credit scores?

Professor Pun's Personal Project

Can I make leading exclamation points be ignored in the terminal? (I type them by instinct due to ipython)

How do professors and lecturers learn to teach?

Prospective employer asking for my current pay slip during interview

Travelling to Paris by train during strike in December 2019

How can I convince my department that I have the academic freedom to select textbooks and use multiple-choice tests in my courses?



Unable to correct problems, you have held broken packages


npm : Depends: node-gyp (>= 0.10.9) but it is not going to be installedUnable to install nvidia drivers on Ubuntu 18.04Unable to install libjack-devInstalling 32 bit libraries on 64 system, libz.so.1 missingDependency issue on installing gstreamer on Ubuntu 18.04mysql-server:Depends: mysql-server-5.5 but it is not going to be installedUbuntu 12.04 LTS server - build-essential install not possibleHow to install wine in ubuntu 16.04?Unable to Install blender in Ubuntu 18.04Broken packages error when installing libdvd-pkgProblem installing apache2Help installing wineWhy doesn't adding the Kubuntu backports ppa allow me to get the latest KDE version?Unable to locate package mysql-server






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;









224


















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.









share|improve this question






















  • 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






  • 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 '18 at 11:18

















224


















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.









share|improve this question






















  • 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






  • 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 '18 at 11:18













224













224









224


66






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.









share|improve this question
















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






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 23 '14 at 2:30









Braiam

56.7k21 gold badges148 silver badges230 bronze badges




56.7k21 gold badges148 silver badges230 bronze badges










asked Nov 28 '12 at 23:48









trondtrond

2,2572 gold badges10 silver badges3 bronze badges




2,2572 gold badges10 silver badges3 bronze badges










  • 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






  • 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 '18 at 11:18












  • 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






  • 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 '18 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 '18 at 11:18





Related: E: Unable to correct problems, you have held broken packages

– Melebius
Jul 25 '18 at 11:18










10 Answers
10






active

oldest

votes


















249



















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>





share|improve this answer






















  • 6





    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






  • 64





    Aptitude was more helpful to me than apt-get, thanks for the hint.

    – szx
    Oct 27 '13 at 15:20






  • 9





    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



















33



















That happened to me too. All I did was sudo apt-get update and that fixed my issue. Good luck.






share|improve this answer
































    10



















    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!






    share|improve this answer
































      9



















      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.





      share|improve this answer


































        6



















        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.list and 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 with sudoedit /etc/apt/sources.list, comment out the incorrect lines in sources.list by preceding them with a # character, save the sources.list file, and run sudo apt update to update the list of available software packages.



        • Select the Fix Broken Packages option in Synaptic package manager. Run the following commands to install Synaptic.



          sudo apt update 
          sudo apt upgrade
          sudo apt install synaptic


          Open Synaptic and in Synaptic select Edit -> Fix Broken Packages and then repeat Edit -> Fix Broken Packages a second time.



          In Synaptic in the left pane click the Custom Filters button which is marked by the mouse cursor in the below screenshot. From the list in the top left corner select Broken. In the center pane will be listed any broken packages that still need to be repaired.



          show broken packages in Synaptic



          Select the broken packages one at a time. Select a broken package, and then open the terminal and run apt policy <package-name>. The results of this command will tell you if that broken package was installed from the default Ubuntu repositories or from some other source. If the broken package was installed from some other source, maybe that package can be removed along with its software source and replaced by a different version of the same package from the default Ubuntu repositories. Usually this means fixing a broken package by downgrading that package to an older version.




        • If you get this error message:



          Try 'apt-get -f install' with no packages (or specify a solution) 


          Run the following commands:



          sudo apt update 
          sudo apt upgrade
          sudo apt-get -f install



        • Manually remove a broken package.




          1. Find your package in /var/lib/dpkg/info



            ls -l /var/lib/dpkg/info | grep <package>



          2. Move the package folder to another location.



            cd /tmp && sudo mkdir new-package-location 
            sudo mv /var/lib/dpkg/info/<package>.* /tmp/new-package-location/



          3. Run the following command:



            sudo dpkg --remove --force-remove-reinstreq <package> 



        If all of these methods don't work it is possible that the broken packages are caused by something that is embedded so deeply in the operating system that none of these methods have any effect on it. The first obvious place to look for this deeply embedded "something" is in the software sources in /etc/apt/sources.list. Check the sources.list file to see if it contains any non-standard lines that may be causing a broken packages error. A standard Ubuntu sources.list file looks like the sources.list files in this answer.



        The correct way to remove a suspicious line from sources.list is to comment it out by preceding it with a # character. Then run sudo apt update to refresh the list of available software.






        share|improve this answer


































          4



















          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).






          share|improve this answer



























          • 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


















          0



















          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.






          share|improve this answer
































            0



















            I had the same problem reinstalling xsane after a failed ppa installation. As happened to yochannah, "no files listed in dpkg --get-selections | grep hold, and no joy after sudo apt-get update".



            The hint that apt-get gave me is



            xsane : Depends: libsane (>= 1.0.24) but it is not going to be installed



            Because of yochannah answer, I had the feeling I must remove some previously installed packages. And it was so, I had to manually remove all related packages to sane, amongst others xsane-common and libsane, which was still installed as the ppa version.



            Therefore, watch out what you have previously installed and tidy up!






            share|improve this answer
































              0



















              I just ran into the same issue with Ubuntu Mate and I found this thread. My issue was trying to chain the update command together like this...



              sudo apt update && sudo apt upgrade -y && sudo apt autoremove


              Which should have worked. It didn't give me any errors, but it ran quick and gave me a list of packages that aren't ready for release yet. The result was I couldn't install my additional drivers.



              I fixed it by running the update / upgrade / autoremove commands separately...



              sudo apt update
              sudo apt upgrade -y
              sudo apt autoremove


              That took the normal long time - especially upgrade - and now my installers work fine. I still don't know why chaining those commands together into one didn't work.



              #head-scratcher



              Here's my driver install running finally.



              Additional Drivers Installation Running.
              Good luck!



              Update: After thinking about it for a bit, I think the warnings I was getting about the packages that aren't ready to be installed yet, were being treated as errors, and breaking the && chain from continuing. Probably had I just chained the commands together with ; it would have worked.



              sudo apt update ; sudo apt upgrade -y ; sudo apt autoremove





              share|improve this answer
































                0



















                This worked for me



                sudo apt update && sudo apt upgrade -y && sudo apt autoremove
                sudo apt list | grep python | cut -d "/" -f1 | xargs sudo apt-get remove -y
                sudo apt list | grep python3.6 | grep -v libboost | cut -d "/" -f1 | xargs sudo apt-get install -y
                sudo apt-get install python-pip -y
                sudo apt-get install python3-pip -y





                share|improve this answer































                  10 Answers
                  10






                  active

                  oldest

                  votes








                  10 Answers
                  10






                  active

                  oldest

                  votes









                  active

                  oldest

                  votes






                  active

                  oldest

                  votes









                  249



















                  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>





                  share|improve this answer






















                  • 6





                    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






                  • 64





                    Aptitude was more helpful to me than apt-get, thanks for the hint.

                    – szx
                    Oct 27 '13 at 15:20






                  • 9





                    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
















                  249



















                  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>





                  share|improve this answer






















                  • 6





                    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






                  • 64





                    Aptitude was more helpful to me than apt-get, thanks for the hint.

                    – szx
                    Oct 27 '13 at 15:20






                  • 9





                    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














                  249















                  249











                  249









                  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>





                  share|improve this answer
















                  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>






                  share|improve this answer















                  share|improve this answer




                  share|improve this answer








                  edited Feb 10 '18 at 12:09

























                  answered Nov 29 '12 at 1:58









                  thomasrutterthomasrutter

                  29.2k4 gold badges72 silver badges92 bronze badges




                  29.2k4 gold badges72 silver badges92 bronze badges










                  • 6





                    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






                  • 64





                    Aptitude was more helpful to me than apt-get, thanks for the hint.

                    – szx
                    Oct 27 '13 at 15:20






                  • 9





                    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













                  • 6





                    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






                  • 64





                    Aptitude was more helpful to me than apt-get, thanks for the hint.

                    – szx
                    Oct 27 '13 at 15:20






                  • 9





                    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








                  6




                  6





                  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




                  64




                  64





                  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




                  9




                  9





                  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














                  33



















                  That happened to me too. All I did was sudo apt-get update and that fixed my issue. Good luck.






                  share|improve this answer





























                    33



















                    That happened to me too. All I did was sudo apt-get update and that fixed my issue. Good luck.






                    share|improve this answer



























                      33















                      33











                      33









                      That happened to me too. All I did was sudo apt-get update and that fixed my issue. Good luck.






                      share|improve this answer














                      That happened to me too. All I did was sudo apt-get update and that fixed my issue. Good luck.







                      share|improve this answer













                      share|improve this answer




                      share|improve this answer










                      answered Aug 27 '13 at 2:43









                      user2292711user2292711

                      4554 silver badges2 bronze badges




                      4554 silver badges2 bronze badges
























                          10



















                          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!






                          share|improve this answer





























                            10



















                            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!






                            share|improve this answer



























                              10















                              10











                              10









                              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!






                              share|improve this answer














                              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!







                              share|improve this answer













                              share|improve this answer




                              share|improve this answer










                              answered Jul 27 '15 at 13:41









                              Reinstate MonicaReinstate Monica

                              2976 silver badges13 bronze badges




                              2976 silver badges13 bronze badges
























                                  9



















                                  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.





                                  share|improve this answer































                                    9



















                                    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.





                                    share|improve this answer





























                                      9















                                      9











                                      9









                                      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.





                                      share|improve this answer
















                                      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.






                                      share|improve this answer















                                      share|improve this answer




                                      share|improve this answer








                                      edited Mar 2 '14 at 9:29









                                      v2r

                                      7,08911 gold badges41 silver badges49 bronze badges




                                      7,08911 gold badges41 silver badges49 bronze badges










                                      answered Mar 2 '14 at 6:53









                                      PeopleunitPeopleunit

                                      1071 silver badge1 bronze badge




                                      1071 silver badge1 bronze badge
























                                          6



















                                          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.list and 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 with sudoedit /etc/apt/sources.list, comment out the incorrect lines in sources.list by preceding them with a # character, save the sources.list file, and run sudo apt update to update the list of available software packages.



                                          • Select the Fix Broken Packages option in Synaptic package manager. Run the following commands to install Synaptic.



                                            sudo apt update 
                                            sudo apt upgrade
                                            sudo apt install synaptic


                                            Open Synaptic and in Synaptic select Edit -> Fix Broken Packages and then repeat Edit -> Fix Broken Packages a second time.



                                            In Synaptic in the left pane click the Custom Filters button which is marked by the mouse cursor in the below screenshot. From the list in the top left corner select Broken. In the center pane will be listed any broken packages that still need to be repaired.



                                            show broken packages in Synaptic



                                            Select the broken packages one at a time. Select a broken package, and then open the terminal and run apt policy <package-name>. The results of this command will tell you if that broken package was installed from the default Ubuntu repositories or from some other source. If the broken package was installed from some other source, maybe that package can be removed along with its software source and replaced by a different version of the same package from the default Ubuntu repositories. Usually this means fixing a broken package by downgrading that package to an older version.




                                          • If you get this error message:



                                            Try 'apt-get -f install' with no packages (or specify a solution) 


                                            Run the following commands:



                                            sudo apt update 
                                            sudo apt upgrade
                                            sudo apt-get -f install



                                          • Manually remove a broken package.




                                            1. Find your package in /var/lib/dpkg/info



                                              ls -l /var/lib/dpkg/info | grep <package>



                                            2. Move the package folder to another location.



                                              cd /tmp && sudo mkdir new-package-location 
                                              sudo mv /var/lib/dpkg/info/<package>.* /tmp/new-package-location/



                                            3. Run the following command:



                                              sudo dpkg --remove --force-remove-reinstreq <package> 



                                          If all of these methods don't work it is possible that the broken packages are caused by something that is embedded so deeply in the operating system that none of these methods have any effect on it. The first obvious place to look for this deeply embedded "something" is in the software sources in /etc/apt/sources.list. Check the sources.list file to see if it contains any non-standard lines that may be causing a broken packages error. A standard Ubuntu sources.list file looks like the sources.list files in this answer.



                                          The correct way to remove a suspicious line from sources.list is to comment it out by preceding it with a # character. Then run sudo apt update to refresh the list of available software.






                                          share|improve this answer































                                            6



















                                            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.list and 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 with sudoedit /etc/apt/sources.list, comment out the incorrect lines in sources.list by preceding them with a # character, save the sources.list file, and run sudo apt update to update the list of available software packages.



                                            • Select the Fix Broken Packages option in Synaptic package manager. Run the following commands to install Synaptic.



                                              sudo apt update 
                                              sudo apt upgrade
                                              sudo apt install synaptic


                                              Open Synaptic and in Synaptic select Edit -> Fix Broken Packages and then repeat Edit -> Fix Broken Packages a second time.



                                              In Synaptic in the left pane click the Custom Filters button which is marked by the mouse cursor in the below screenshot. From the list in the top left corner select Broken. In the center pane will be listed any broken packages that still need to be repaired.



                                              show broken packages in Synaptic



                                              Select the broken packages one at a time. Select a broken package, and then open the terminal and run apt policy <package-name>. The results of this command will tell you if that broken package was installed from the default Ubuntu repositories or from some other source. If the broken package was installed from some other source, maybe that package can be removed along with its software source and replaced by a different version of the same package from the default Ubuntu repositories. Usually this means fixing a broken package by downgrading that package to an older version.




                                            • If you get this error message:



                                              Try 'apt-get -f install' with no packages (or specify a solution) 


                                              Run the following commands:



                                              sudo apt update 
                                              sudo apt upgrade
                                              sudo apt-get -f install



                                            • Manually remove a broken package.




                                              1. Find your package in /var/lib/dpkg/info



                                                ls -l /var/lib/dpkg/info | grep <package>



                                              2. Move the package folder to another location.



                                                cd /tmp && sudo mkdir new-package-location 
                                                sudo mv /var/lib/dpkg/info/<package>.* /tmp/new-package-location/



                                              3. Run the following command:



                                                sudo dpkg --remove --force-remove-reinstreq <package> 



                                            If all of these methods don't work it is possible that the broken packages are caused by something that is embedded so deeply in the operating system that none of these methods have any effect on it. The first obvious place to look for this deeply embedded "something" is in the software sources in /etc/apt/sources.list. Check the sources.list file to see if it contains any non-standard lines that may be causing a broken packages error. A standard Ubuntu sources.list file looks like the sources.list files in this answer.



                                            The correct way to remove a suspicious line from sources.list is to comment it out by preceding it with a # character. Then run sudo apt update to refresh the list of available software.






                                            share|improve this answer





























                                              6















                                              6











                                              6









                                              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.list and 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 with sudoedit /etc/apt/sources.list, comment out the incorrect lines in sources.list by preceding them with a # character, save the sources.list file, and run sudo apt update to update the list of available software packages.



                                              • Select the Fix Broken Packages option in Synaptic package manager. Run the following commands to install Synaptic.



                                                sudo apt update 
                                                sudo apt upgrade
                                                sudo apt install synaptic


                                                Open Synaptic and in Synaptic select Edit -> Fix Broken Packages and then repeat Edit -> Fix Broken Packages a second time.



                                                In Synaptic in the left pane click the Custom Filters button which is marked by the mouse cursor in the below screenshot. From the list in the top left corner select Broken. In the center pane will be listed any broken packages that still need to be repaired.



                                                show broken packages in Synaptic



                                                Select the broken packages one at a time. Select a broken package, and then open the terminal and run apt policy <package-name>. The results of this command will tell you if that broken package was installed from the default Ubuntu repositories or from some other source. If the broken package was installed from some other source, maybe that package can be removed along with its software source and replaced by a different version of the same package from the default Ubuntu repositories. Usually this means fixing a broken package by downgrading that package to an older version.




                                              • If you get this error message:



                                                Try 'apt-get -f install' with no packages (or specify a solution) 


                                                Run the following commands:



                                                sudo apt update 
                                                sudo apt upgrade
                                                sudo apt-get -f install



                                              • Manually remove a broken package.




                                                1. Find your package in /var/lib/dpkg/info



                                                  ls -l /var/lib/dpkg/info | grep <package>



                                                2. Move the package folder to another location.



                                                  cd /tmp && sudo mkdir new-package-location 
                                                  sudo mv /var/lib/dpkg/info/<package>.* /tmp/new-package-location/



                                                3. Run the following command:



                                                  sudo dpkg --remove --force-remove-reinstreq <package> 



                                              If all of these methods don't work it is possible that the broken packages are caused by something that is embedded so deeply in the operating system that none of these methods have any effect on it. The first obvious place to look for this deeply embedded "something" is in the software sources in /etc/apt/sources.list. Check the sources.list file to see if it contains any non-standard lines that may be causing a broken packages error. A standard Ubuntu sources.list file looks like the sources.list files in this answer.



                                              The correct way to remove a suspicious line from sources.list is to comment it out by preceding it with a # character. Then run sudo apt update to refresh the list of available software.






                                              share|improve this answer
















                                              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.list and 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 with sudoedit /etc/apt/sources.list, comment out the incorrect lines in sources.list by preceding them with a # character, save the sources.list file, and run sudo apt update to update the list of available software packages.



                                              • Select the Fix Broken Packages option in Synaptic package manager. Run the following commands to install Synaptic.



                                                sudo apt update 
                                                sudo apt upgrade
                                                sudo apt install synaptic


                                                Open Synaptic and in Synaptic select Edit -> Fix Broken Packages and then repeat Edit -> Fix Broken Packages a second time.



                                                In Synaptic in the left pane click the Custom Filters button which is marked by the mouse cursor in the below screenshot. From the list in the top left corner select Broken. In the center pane will be listed any broken packages that still need to be repaired.



                                                show broken packages in Synaptic



                                                Select the broken packages one at a time. Select a broken package, and then open the terminal and run apt policy <package-name>. The results of this command will tell you if that broken package was installed from the default Ubuntu repositories or from some other source. If the broken package was installed from some other source, maybe that package can be removed along with its software source and replaced by a different version of the same package from the default Ubuntu repositories. Usually this means fixing a broken package by downgrading that package to an older version.




                                              • If you get this error message:



                                                Try 'apt-get -f install' with no packages (or specify a solution) 


                                                Run the following commands:



                                                sudo apt update 
                                                sudo apt upgrade
                                                sudo apt-get -f install



                                              • Manually remove a broken package.




                                                1. Find your package in /var/lib/dpkg/info



                                                  ls -l /var/lib/dpkg/info | grep <package>



                                                2. Move the package folder to another location.



                                                  cd /tmp && sudo mkdir new-package-location 
                                                  sudo mv /var/lib/dpkg/info/<package>.* /tmp/new-package-location/



                                                3. Run the following command:



                                                  sudo dpkg --remove --force-remove-reinstreq <package> 



                                              If all of these methods don't work it is possible that the broken packages are caused by something that is embedded so deeply in the operating system that none of these methods have any effect on it. The first obvious place to look for this deeply embedded "something" is in the software sources in /etc/apt/sources.list. Check the sources.list file to see if it contains any non-standard lines that may be causing a broken packages error. A standard Ubuntu sources.list file looks like the sources.list files in this answer.



                                              The correct way to remove a suspicious line from sources.list is to comment it out by preceding it with a # character. Then run sudo apt update to refresh the list of available software.







                                              share|improve this answer















                                              share|improve this answer




                                              share|improve this answer








                                              edited Jul 8 at 7:37

























                                              answered Oct 8 '18 at 11:13









                                              karelkarel

                                              71.6k15 gold badges160 silver badges186 bronze badges




                                              71.6k15 gold badges160 silver badges186 bronze badges
























                                                  4



















                                                  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).






                                                  share|improve this answer



























                                                  • 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















                                                  4



















                                                  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).






                                                  share|improve this answer



























                                                  • 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













                                                  4















                                                  4











                                                  4









                                                  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).






                                                  share|improve this answer
















                                                  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).







                                                  share|improve this answer















                                                  share|improve this answer




                                                  share|improve this answer








                                                  edited Aug 17 '14 at 20:57









                                                  belacqua

                                                  19.8k16 gold badges75 silver badges104 bronze badges




                                                  19.8k16 gold badges75 silver badges104 bronze badges










                                                  answered Oct 3 '13 at 11:03









                                                  NollaigNollaig

                                                  651 silver badge1 bronze badge




                                                  651 silver badge1 bronze badge















                                                  • 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











                                                  • 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











                                                  0



















                                                  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.






                                                  share|improve this answer





























                                                    0



















                                                    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.






                                                    share|improve this answer



























                                                      0















                                                      0











                                                      0









                                                      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.






                                                      share|improve this answer














                                                      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.







                                                      share|improve this answer













                                                      share|improve this answer




                                                      share|improve this answer










                                                      answered May 25 '18 at 14:01









                                                      VoidVoid

                                                      1133 bronze badges




                                                      1133 bronze badges
























                                                          0



















                                                          I had the same problem reinstalling xsane after a failed ppa installation. As happened to yochannah, "no files listed in dpkg --get-selections | grep hold, and no joy after sudo apt-get update".



                                                          The hint that apt-get gave me is



                                                          xsane : Depends: libsane (>= 1.0.24) but it is not going to be installed



                                                          Because of yochannah answer, I had the feeling I must remove some previously installed packages. And it was so, I had to manually remove all related packages to sane, amongst others xsane-common and libsane, which was still installed as the ppa version.



                                                          Therefore, watch out what you have previously installed and tidy up!






                                                          share|improve this answer





























                                                            0



















                                                            I had the same problem reinstalling xsane after a failed ppa installation. As happened to yochannah, "no files listed in dpkg --get-selections | grep hold, and no joy after sudo apt-get update".



                                                            The hint that apt-get gave me is



                                                            xsane : Depends: libsane (>= 1.0.24) but it is not going to be installed



                                                            Because of yochannah answer, I had the feeling I must remove some previously installed packages. And it was so, I had to manually remove all related packages to sane, amongst others xsane-common and libsane, which was still installed as the ppa version.



                                                            Therefore, watch out what you have previously installed and tidy up!






                                                            share|improve this answer



























                                                              0















                                                              0











                                                              0









                                                              I had the same problem reinstalling xsane after a failed ppa installation. As happened to yochannah, "no files listed in dpkg --get-selections | grep hold, and no joy after sudo apt-get update".



                                                              The hint that apt-get gave me is



                                                              xsane : Depends: libsane (>= 1.0.24) but it is not going to be installed



                                                              Because of yochannah answer, I had the feeling I must remove some previously installed packages. And it was so, I had to manually remove all related packages to sane, amongst others xsane-common and libsane, which was still installed as the ppa version.



                                                              Therefore, watch out what you have previously installed and tidy up!






                                                              share|improve this answer














                                                              I had the same problem reinstalling xsane after a failed ppa installation. As happened to yochannah, "no files listed in dpkg --get-selections | grep hold, and no joy after sudo apt-get update".



                                                              The hint that apt-get gave me is



                                                              xsane : Depends: libsane (>= 1.0.24) but it is not going to be installed



                                                              Because of yochannah answer, I had the feeling I must remove some previously installed packages. And it was so, I had to manually remove all related packages to sane, amongst others xsane-common and libsane, which was still installed as the ppa version.



                                                              Therefore, watch out what you have previously installed and tidy up!







                                                              share|improve this answer













                                                              share|improve this answer




                                                              share|improve this answer










                                                              answered Oct 9 at 9:29









                                                              loved.by.Jesusloved.by.Jesus

                                                              1561 silver badge13 bronze badges




                                                              1561 silver badge13 bronze badges
























                                                                  0



















                                                                  I just ran into the same issue with Ubuntu Mate and I found this thread. My issue was trying to chain the update command together like this...



                                                                  sudo apt update && sudo apt upgrade -y && sudo apt autoremove


                                                                  Which should have worked. It didn't give me any errors, but it ran quick and gave me a list of packages that aren't ready for release yet. The result was I couldn't install my additional drivers.



                                                                  I fixed it by running the update / upgrade / autoremove commands separately...



                                                                  sudo apt update
                                                                  sudo apt upgrade -y
                                                                  sudo apt autoremove


                                                                  That took the normal long time - especially upgrade - and now my installers work fine. I still don't know why chaining those commands together into one didn't work.



                                                                  #head-scratcher



                                                                  Here's my driver install running finally.



                                                                  Additional Drivers Installation Running.
                                                                  Good luck!



                                                                  Update: After thinking about it for a bit, I think the warnings I was getting about the packages that aren't ready to be installed yet, were being treated as errors, and breaking the && chain from continuing. Probably had I just chained the commands together with ; it would have worked.



                                                                  sudo apt update ; sudo apt upgrade -y ; sudo apt autoremove





                                                                  share|improve this answer





























                                                                    0



















                                                                    I just ran into the same issue with Ubuntu Mate and I found this thread. My issue was trying to chain the update command together like this...



                                                                    sudo apt update && sudo apt upgrade -y && sudo apt autoremove


                                                                    Which should have worked. It didn't give me any errors, but it ran quick and gave me a list of packages that aren't ready for release yet. The result was I couldn't install my additional drivers.



                                                                    I fixed it by running the update / upgrade / autoremove commands separately...



                                                                    sudo apt update
                                                                    sudo apt upgrade -y
                                                                    sudo apt autoremove


                                                                    That took the normal long time - especially upgrade - and now my installers work fine. I still don't know why chaining those commands together into one didn't work.



                                                                    #head-scratcher



                                                                    Here's my driver install running finally.



                                                                    Additional Drivers Installation Running.
                                                                    Good luck!



                                                                    Update: After thinking about it for a bit, I think the warnings I was getting about the packages that aren't ready to be installed yet, were being treated as errors, and breaking the && chain from continuing. Probably had I just chained the commands together with ; it would have worked.



                                                                    sudo apt update ; sudo apt upgrade -y ; sudo apt autoremove





                                                                    share|improve this answer



























                                                                      0















                                                                      0











                                                                      0









                                                                      I just ran into the same issue with Ubuntu Mate and I found this thread. My issue was trying to chain the update command together like this...



                                                                      sudo apt update && sudo apt upgrade -y && sudo apt autoremove


                                                                      Which should have worked. It didn't give me any errors, but it ran quick and gave me a list of packages that aren't ready for release yet. The result was I couldn't install my additional drivers.



                                                                      I fixed it by running the update / upgrade / autoremove commands separately...



                                                                      sudo apt update
                                                                      sudo apt upgrade -y
                                                                      sudo apt autoremove


                                                                      That took the normal long time - especially upgrade - and now my installers work fine. I still don't know why chaining those commands together into one didn't work.



                                                                      #head-scratcher



                                                                      Here's my driver install running finally.



                                                                      Additional Drivers Installation Running.
                                                                      Good luck!



                                                                      Update: After thinking about it for a bit, I think the warnings I was getting about the packages that aren't ready to be installed yet, were being treated as errors, and breaking the && chain from continuing. Probably had I just chained the commands together with ; it would have worked.



                                                                      sudo apt update ; sudo apt upgrade -y ; sudo apt autoremove





                                                                      share|improve this answer














                                                                      I just ran into the same issue with Ubuntu Mate and I found this thread. My issue was trying to chain the update command together like this...



                                                                      sudo apt update && sudo apt upgrade -y && sudo apt autoremove


                                                                      Which should have worked. It didn't give me any errors, but it ran quick and gave me a list of packages that aren't ready for release yet. The result was I couldn't install my additional drivers.



                                                                      I fixed it by running the update / upgrade / autoremove commands separately...



                                                                      sudo apt update
                                                                      sudo apt upgrade -y
                                                                      sudo apt autoremove


                                                                      That took the normal long time - especially upgrade - and now my installers work fine. I still don't know why chaining those commands together into one didn't work.



                                                                      #head-scratcher



                                                                      Here's my driver install running finally.



                                                                      Additional Drivers Installation Running.
                                                                      Good luck!



                                                                      Update: After thinking about it for a bit, I think the warnings I was getting about the packages that aren't ready to be installed yet, were being treated as errors, and breaking the && chain from continuing. Probably had I just chained the commands together with ; it would have worked.



                                                                      sudo apt update ; sudo apt upgrade -y ; sudo apt autoremove






                                                                      share|improve this answer













                                                                      share|improve this answer




                                                                      share|improve this answer










                                                                      answered Oct 28 at 21:32









                                                                      Phillip H. BlantonPhillip H. Blanton

                                                                      867 bronze badges




                                                                      867 bronze badges
























                                                                          0



















                                                                          This worked for me



                                                                          sudo apt update && sudo apt upgrade -y && sudo apt autoremove
                                                                          sudo apt list | grep python | cut -d "/" -f1 | xargs sudo apt-get remove -y
                                                                          sudo apt list | grep python3.6 | grep -v libboost | cut -d "/" -f1 | xargs sudo apt-get install -y
                                                                          sudo apt-get install python-pip -y
                                                                          sudo apt-get install python3-pip -y





                                                                          share|improve this answer































                                                                            0



















                                                                            This worked for me



                                                                            sudo apt update && sudo apt upgrade -y && sudo apt autoremove
                                                                            sudo apt list | grep python | cut -d "/" -f1 | xargs sudo apt-get remove -y
                                                                            sudo apt list | grep python3.6 | grep -v libboost | cut -d "/" -f1 | xargs sudo apt-get install -y
                                                                            sudo apt-get install python-pip -y
                                                                            sudo apt-get install python3-pip -y





                                                                            share|improve this answer





























                                                                              0















                                                                              0











                                                                              0









                                                                              This worked for me



                                                                              sudo apt update && sudo apt upgrade -y && sudo apt autoremove
                                                                              sudo apt list | grep python | cut -d "/" -f1 | xargs sudo apt-get remove -y
                                                                              sudo apt list | grep python3.6 | grep -v libboost | cut -d "/" -f1 | xargs sudo apt-get install -y
                                                                              sudo apt-get install python-pip -y
                                                                              sudo apt-get install python3-pip -y





                                                                              share|improve this answer
















                                                                              This worked for me



                                                                              sudo apt update && sudo apt upgrade -y && sudo apt autoremove
                                                                              sudo apt list | grep python | cut -d "/" -f1 | xargs sudo apt-get remove -y
                                                                              sudo apt list | grep python3.6 | grep -v libboost | cut -d "/" -f1 | xargs sudo apt-get install -y
                                                                              sudo apt-get install python-pip -y
                                                                              sudo apt-get install python3-pip -y






                                                                              share|improve this answer















                                                                              share|improve this answer




                                                                              share|improve this answer








                                                                              edited Nov 19 at 2:55

























                                                                              answered Nov 19 at 2:50









                                                                              Artur MustafinArtur Mustafin

                                                                              1114 bronze badges




                                                                              1114 bronze badges
























                                                                                  Highly active question. Earn 10 reputation in order to answer this question. The reputation requirement helps protect this question from spam and non-answer activity.












                                                                                  Highly active question. Earn 10 reputation in order to answer this question. The reputation requirement helps protect this question from spam and non-answer activity.











                                                                                  Highly active question. Earn 10 reputation in order to answer this question. The reputation requirement helps protect this question from spam and non-answer activity.





                                                                                  Highly active question. Earn 10 reputation in order to answer this question. The reputation requirement helps protect this question from spam and non-answer activity.


                                                                                  Popular posts from this blog

                                                                                  Tamil (spriik) Luke uk diar | Nawigatjuun

                                                                                  Align equal signs while including text over equalitiesAMS align: left aligned text/math plus multicolumn alignmentMultiple alignmentsAligning equations in multiple placesNumbering and aligning an equation with multiple columnsHow to align one equation with another multline equationUsing \ in environments inside the begintabularxNumber equations and preserving alignment of equal signsHow can I align equations to the left and to the right?Double equation alignment problem within align enviromentAligned within align: Why are they right-aligned?

                                                                                  Where does the image of a data connector as a sharp metal spike originate from?Where does the concept of infected people turning into zombies only after death originate from?Where does the motif of a reanimated human head originate?Where did the notion that Dragons could speak originate?Where does the archetypal image of the 'Grey' alien come from?Where did the suffix '-Man' originate?Where does the notion of being injured or killed by an illusion originate?Where did the term “sophont” originate?Where does the trope of magic spells being driven by advanced technology originate from?Where did the term “the living impaired” originate?