How to convince dpkg that libssl1.0.2 is >= libssl1.0.0?

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











up vote
8
down vote

favorite
3












I am trying to install a 3rd party .deb package that I have installed before on Debian 8. But I cannot install on a fresh Debian 9 setup because I get the following error:



dpkg: dependency problems prevent configuration of parity:
parity depends on libssl1.0.0 (>= 1.0.0); however:
Package libssl1.0.0 is not installed.


I do have libssl1.0.2 installed. But it is not being recognized as ">= libssl1.0.0" so I wonder how to fix this.



  1. Do I install libssl1.0.0 manually? If so, how?


  2. Do I symlink something? If so, what?


  3. Something else?










share|improve this question



























    up vote
    8
    down vote

    favorite
    3












    I am trying to install a 3rd party .deb package that I have installed before on Debian 8. But I cannot install on a fresh Debian 9 setup because I get the following error:



    dpkg: dependency problems prevent configuration of parity:
    parity depends on libssl1.0.0 (>= 1.0.0); however:
    Package libssl1.0.0 is not installed.


    I do have libssl1.0.2 installed. But it is not being recognized as ">= libssl1.0.0" so I wonder how to fix this.



    1. Do I install libssl1.0.0 manually? If so, how?


    2. Do I symlink something? If so, what?


    3. Something else?










    share|improve this question

























      up vote
      8
      down vote

      favorite
      3









      up vote
      8
      down vote

      favorite
      3






      3





      I am trying to install a 3rd party .deb package that I have installed before on Debian 8. But I cannot install on a fresh Debian 9 setup because I get the following error:



      dpkg: dependency problems prevent configuration of parity:
      parity depends on libssl1.0.0 (>= 1.0.0); however:
      Package libssl1.0.0 is not installed.


      I do have libssl1.0.2 installed. But it is not being recognized as ">= libssl1.0.0" so I wonder how to fix this.



      1. Do I install libssl1.0.0 manually? If so, how?


      2. Do I symlink something? If so, what?


      3. Something else?










      share|improve this question















      I am trying to install a 3rd party .deb package that I have installed before on Debian 8. But I cannot install on a fresh Debian 9 setup because I get the following error:



      dpkg: dependency problems prevent configuration of parity:
      parity depends on libssl1.0.0 (>= 1.0.0); however:
      Package libssl1.0.0 is not installed.


      I do have libssl1.0.2 installed. But it is not being recognized as ">= libssl1.0.0" so I wonder how to fix this.



      1. Do I install libssl1.0.0 manually? If so, how?


      2. Do I symlink something? If so, what?


      3. Something else?







      debian dpkg libraries ssl dependencies






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Sep 26 '17 at 10:54









      Jeff Schaller

      32.3k849110




      32.3k849110










      asked Sep 26 '17 at 4:33









      stone212

      164111




      164111




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          16
          down vote



          accepted










          libssl1.0.2 and libssl1.0.0 are different packages, providing incompatible libraries; that’s why you can’t satisfy a libssl1.0.0 dependency using libssl1.0.2.



          To satisfy your package’s requirements, I’d suggest adding the Debian 8 repositories to your configuration, since Debian 8 is still supported (so if necessary you’ll get security updates). To do so, edit your /etc/apt/sources.list file, and copy every stretch line, replacing stretch with jessie (so you end up with both stretch and jessie lines). Then run apt update, and apt install libssl1.0.0 should work.



          Alternatively, you can download the package (look for your architecture at the bottom of the page), and install it with dpkg -i.



          In both cases, apt-mark auto libssl1.0.0 will help: that way the package will be considered for auto-removal, should it become unnecessary in the future.






          share|improve this answer




















          • If I have the repos for both stretch and jessie, how will conflicts be avoided on packages in both repos?
            – stone212
            Oct 14 '17 at 0:09











          • apt will pick later versions of packages from similarly-configured repositories; so in your case, it will favour Jessie, and will only use the Stretch repositories for packages which are no longer in Stretch (such as libssl1.0.0), as long as they don’t conflict with installed Jessie packages.
            – Stephen Kitt
            Oct 14 '17 at 9:23










          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%2f394456%2fhow-to-convince-dpkg-that-libssl1-0-2-is-libssl1-0-0%23new-answer', 'question_page');

          );

          Post as a guest






























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          16
          down vote



          accepted










          libssl1.0.2 and libssl1.0.0 are different packages, providing incompatible libraries; that’s why you can’t satisfy a libssl1.0.0 dependency using libssl1.0.2.



          To satisfy your package’s requirements, I’d suggest adding the Debian 8 repositories to your configuration, since Debian 8 is still supported (so if necessary you’ll get security updates). To do so, edit your /etc/apt/sources.list file, and copy every stretch line, replacing stretch with jessie (so you end up with both stretch and jessie lines). Then run apt update, and apt install libssl1.0.0 should work.



          Alternatively, you can download the package (look for your architecture at the bottom of the page), and install it with dpkg -i.



          In both cases, apt-mark auto libssl1.0.0 will help: that way the package will be considered for auto-removal, should it become unnecessary in the future.






          share|improve this answer




















          • If I have the repos for both stretch and jessie, how will conflicts be avoided on packages in both repos?
            – stone212
            Oct 14 '17 at 0:09











          • apt will pick later versions of packages from similarly-configured repositories; so in your case, it will favour Jessie, and will only use the Stretch repositories for packages which are no longer in Stretch (such as libssl1.0.0), as long as they don’t conflict with installed Jessie packages.
            – Stephen Kitt
            Oct 14 '17 at 9:23














          up vote
          16
          down vote



          accepted










          libssl1.0.2 and libssl1.0.0 are different packages, providing incompatible libraries; that’s why you can’t satisfy a libssl1.0.0 dependency using libssl1.0.2.



          To satisfy your package’s requirements, I’d suggest adding the Debian 8 repositories to your configuration, since Debian 8 is still supported (so if necessary you’ll get security updates). To do so, edit your /etc/apt/sources.list file, and copy every stretch line, replacing stretch with jessie (so you end up with both stretch and jessie lines). Then run apt update, and apt install libssl1.0.0 should work.



          Alternatively, you can download the package (look for your architecture at the bottom of the page), and install it with dpkg -i.



          In both cases, apt-mark auto libssl1.0.0 will help: that way the package will be considered for auto-removal, should it become unnecessary in the future.






          share|improve this answer




















          • If I have the repos for both stretch and jessie, how will conflicts be avoided on packages in both repos?
            – stone212
            Oct 14 '17 at 0:09











          • apt will pick later versions of packages from similarly-configured repositories; so in your case, it will favour Jessie, and will only use the Stretch repositories for packages which are no longer in Stretch (such as libssl1.0.0), as long as they don’t conflict with installed Jessie packages.
            – Stephen Kitt
            Oct 14 '17 at 9:23












          up vote
          16
          down vote



          accepted







          up vote
          16
          down vote



          accepted






          libssl1.0.2 and libssl1.0.0 are different packages, providing incompatible libraries; that’s why you can’t satisfy a libssl1.0.0 dependency using libssl1.0.2.



          To satisfy your package’s requirements, I’d suggest adding the Debian 8 repositories to your configuration, since Debian 8 is still supported (so if necessary you’ll get security updates). To do so, edit your /etc/apt/sources.list file, and copy every stretch line, replacing stretch with jessie (so you end up with both stretch and jessie lines). Then run apt update, and apt install libssl1.0.0 should work.



          Alternatively, you can download the package (look for your architecture at the bottom of the page), and install it with dpkg -i.



          In both cases, apt-mark auto libssl1.0.0 will help: that way the package will be considered for auto-removal, should it become unnecessary in the future.






          share|improve this answer












          libssl1.0.2 and libssl1.0.0 are different packages, providing incompatible libraries; that’s why you can’t satisfy a libssl1.0.0 dependency using libssl1.0.2.



          To satisfy your package’s requirements, I’d suggest adding the Debian 8 repositories to your configuration, since Debian 8 is still supported (so if necessary you’ll get security updates). To do so, edit your /etc/apt/sources.list file, and copy every stretch line, replacing stretch with jessie (so you end up with both stretch and jessie lines). Then run apt update, and apt install libssl1.0.0 should work.



          Alternatively, you can download the package (look for your architecture at the bottom of the page), and install it with dpkg -i.



          In both cases, apt-mark auto libssl1.0.0 will help: that way the package will be considered for auto-removal, should it become unnecessary in the future.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Sep 26 '17 at 5:24









          Stephen Kitt

          145k22317382




          145k22317382











          • If I have the repos for both stretch and jessie, how will conflicts be avoided on packages in both repos?
            – stone212
            Oct 14 '17 at 0:09











          • apt will pick later versions of packages from similarly-configured repositories; so in your case, it will favour Jessie, and will only use the Stretch repositories for packages which are no longer in Stretch (such as libssl1.0.0), as long as they don’t conflict with installed Jessie packages.
            – Stephen Kitt
            Oct 14 '17 at 9:23
















          • If I have the repos for both stretch and jessie, how will conflicts be avoided on packages in both repos?
            – stone212
            Oct 14 '17 at 0:09











          • apt will pick later versions of packages from similarly-configured repositories; so in your case, it will favour Jessie, and will only use the Stretch repositories for packages which are no longer in Stretch (such as libssl1.0.0), as long as they don’t conflict with installed Jessie packages.
            – Stephen Kitt
            Oct 14 '17 at 9:23















          If I have the repos for both stretch and jessie, how will conflicts be avoided on packages in both repos?
          – stone212
          Oct 14 '17 at 0:09





          If I have the repos for both stretch and jessie, how will conflicts be avoided on packages in both repos?
          – stone212
          Oct 14 '17 at 0:09













          apt will pick later versions of packages from similarly-configured repositories; so in your case, it will favour Jessie, and will only use the Stretch repositories for packages which are no longer in Stretch (such as libssl1.0.0), as long as they don’t conflict with installed Jessie packages.
          – Stephen Kitt
          Oct 14 '17 at 9:23




          apt will pick later versions of packages from similarly-configured repositories; so in your case, it will favour Jessie, and will only use the Stretch repositories for packages which are no longer in Stretch (such as libssl1.0.0), as long as they don’t conflict with installed Jessie packages.
          – Stephen Kitt
          Oct 14 '17 at 9:23

















           

          draft saved


          draft discarded















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f394456%2fhow-to-convince-dpkg-that-libssl1-0-2-is-libssl1-0-0%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?