Can I see why apt-get install -f is removing my package?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












I have a package that I am installing directly from a .deb file by running sudo dpkg -i. After running that, I am presented with the list of unmet dependencies for the package. When I run sudo apt-get install -f to install the dependencies, apt-get instead removes my package without explaining why.



Is there a way to see why apt-get is removing my package instead of installing its dependencies?







share|improve this question

























    up vote
    1
    down vote

    favorite












    I have a package that I am installing directly from a .deb file by running sudo dpkg -i. After running that, I am presented with the list of unmet dependencies for the package. When I run sudo apt-get install -f to install the dependencies, apt-get instead removes my package without explaining why.



    Is there a way to see why apt-get is removing my package instead of installing its dependencies?







    share|improve this question























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      I have a package that I am installing directly from a .deb file by running sudo dpkg -i. After running that, I am presented with the list of unmet dependencies for the package. When I run sudo apt-get install -f to install the dependencies, apt-get instead removes my package without explaining why.



      Is there a way to see why apt-get is removing my package instead of installing its dependencies?







      share|improve this question













      I have a package that I am installing directly from a .deb file by running sudo dpkg -i. After running that, I am presented with the list of unmet dependencies for the package. When I run sudo apt-get install -f to install the dependencies, apt-get instead removes my package without explaining why.



      Is there a way to see why apt-get is removing my package instead of installing its dependencies?









      share|improve this question












      share|improve this question




      share|improve this question








      edited May 29 at 16:20
























      asked May 29 at 15:19









      JM0

      415




      415




















          2 Answers
          2






          active

          oldest

          votes

















          up vote
          2
          down vote



          accepted










          I was able to figure out what was going wrong by running apt-get with a debug option:



          sudo apt-get -o Debug::pkgProblemResolver=true install -f



          This showed why the package was being removed. In my case, apt-get couldn't find a certain dependency in the repositories.






          share|improve this answer




























            up vote
            0
            down vote













            From apt-get manual:



            -f, --fix-broken
            Fix; attempt to correct a system with broken dependencies in place.
            This option, when used with install/remove, can omit any packages to permit APT to deduce a likely solution. If packages are
            specified, these have to completely correct the problem.


            Apparently the only automatic fix detected is removing your package. You should try to solve the dependencies manually.






            share|improve this answer























              Your Answer







              StackExchange.ready(function()
              var channelOptions =
              tags: "".split(" "),
              id: "106"
              ;
              initTagRenderer("".split(" "), "".split(" "), channelOptions);

              StackExchange.using("externalEditor", function()
              // Have to fire editor after snippets, if snippets enabled
              if (StackExchange.settings.snippets.snippetsEnabled)
              StackExchange.using("snippets", function()
              createEditor();
              );

              else
              createEditor();

              );

              function createEditor()
              StackExchange.prepareEditor(
              heartbeatType: 'answer',
              convertImagesToLinks: false,
              noModals: false,
              showLowRepImageUploadWarning: true,
              reputationToPostImages: null,
              bindNavPrevention: true,
              postfix: "",
              onDemand: true,
              discardSelector: ".discard-answer"
              ,immediatelyShowMarkdownHelp:true
              );



              );








               

              draft saved


              draft discarded


















              StackExchange.ready(
              function ()
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f446729%2fcan-i-see-why-apt-get-install-f-is-removing-my-package%23new-answer', 'question_page');

              );

              Post as a guest






























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes








              up vote
              2
              down vote



              accepted










              I was able to figure out what was going wrong by running apt-get with a debug option:



              sudo apt-get -o Debug::pkgProblemResolver=true install -f



              This showed why the package was being removed. In my case, apt-get couldn't find a certain dependency in the repositories.






              share|improve this answer

























                up vote
                2
                down vote



                accepted










                I was able to figure out what was going wrong by running apt-get with a debug option:



                sudo apt-get -o Debug::pkgProblemResolver=true install -f



                This showed why the package was being removed. In my case, apt-get couldn't find a certain dependency in the repositories.






                share|improve this answer























                  up vote
                  2
                  down vote



                  accepted







                  up vote
                  2
                  down vote



                  accepted






                  I was able to figure out what was going wrong by running apt-get with a debug option:



                  sudo apt-get -o Debug::pkgProblemResolver=true install -f



                  This showed why the package was being removed. In my case, apt-get couldn't find a certain dependency in the repositories.






                  share|improve this answer













                  I was able to figure out what was going wrong by running apt-get with a debug option:



                  sudo apt-get -o Debug::pkgProblemResolver=true install -f



                  This showed why the package was being removed. In my case, apt-get couldn't find a certain dependency in the repositories.







                  share|improve this answer













                  share|improve this answer



                  share|improve this answer











                  answered May 29 at 16:17









                  JM0

                  415




                  415






















                      up vote
                      0
                      down vote













                      From apt-get manual:



                      -f, --fix-broken
                      Fix; attempt to correct a system with broken dependencies in place.
                      This option, when used with install/remove, can omit any packages to permit APT to deduce a likely solution. If packages are
                      specified, these have to completely correct the problem.


                      Apparently the only automatic fix detected is removing your package. You should try to solve the dependencies manually.






                      share|improve this answer



























                        up vote
                        0
                        down vote













                        From apt-get manual:



                        -f, --fix-broken
                        Fix; attempt to correct a system with broken dependencies in place.
                        This option, when used with install/remove, can omit any packages to permit APT to deduce a likely solution. If packages are
                        specified, these have to completely correct the problem.


                        Apparently the only automatic fix detected is removing your package. You should try to solve the dependencies manually.






                        share|improve this answer

























                          up vote
                          0
                          down vote










                          up vote
                          0
                          down vote









                          From apt-get manual:



                          -f, --fix-broken
                          Fix; attempt to correct a system with broken dependencies in place.
                          This option, when used with install/remove, can omit any packages to permit APT to deduce a likely solution. If packages are
                          specified, these have to completely correct the problem.


                          Apparently the only automatic fix detected is removing your package. You should try to solve the dependencies manually.






                          share|improve this answer















                          From apt-get manual:



                          -f, --fix-broken
                          Fix; attempt to correct a system with broken dependencies in place.
                          This option, when used with install/remove, can omit any packages to permit APT to deduce a likely solution. If packages are
                          specified, these have to completely correct the problem.


                          Apparently the only automatic fix detected is removing your package. You should try to solve the dependencies manually.







                          share|improve this answer















                          share|improve this answer



                          share|improve this answer








                          edited May 29 at 16:52


























                          answered May 29 at 15:31









                          Bruno9779

                          1,107415




                          1,107415






















                               

                              draft saved


                              draft discarded


























                               


                              draft saved


                              draft discarded














                              StackExchange.ready(
                              function ()
                              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f446729%2fcan-i-see-why-apt-get-install-f-is-removing-my-package%23new-answer', 'question_page');

                              );

                              Post as a guest













































































                              Popular posts from this blog

                              How to check contact read email or not when send email to Individual?

                              Displaying single band from multi-band raster using QGIS

                              How many registers does an x86_64 CPU actually have?