Broken npm, so tried aptitude, which broke apt AND aptitude leaving me with no package manager











up vote
1
down vote

favorite












So, during a minor update earlier, I noticed that npm wasn't working, so I began updating packages. I landed on this similar issue, so went on to get aptitude installed. Somehow, that installation failed as well. Everything I tried resulted in pages of this error:



E: The method driver /usr/lib/apt/methods/http could not be found.


So after a bunch of more messing around, i had aptitude uninstall itself, which it did. But this left me with no aptitude OR apt.



I tried to download a few of these and install them with dpkg but it fails due to just an endless list of missing dependencies.



# dpkg -i apt_1.7.0_i386.deb 
(Reading database ... 151349 files and directories currently installed.)
Preparing to unpack apt_1.7.0_i386.deb ...
Unpacking apt:i386 (1.7.0) over (1.7.0) ...
dpkg: dependency problems prevent configuration of apt:i386:
apt:i386 depends on libapt-pkg5.0 (>= 1.7.0~alpha3~).
apt:i386 depends on libc6 (>= 2.15).
apt:i386 depends on libgcc1 (>= 1:4.2).
apt:i386 depends on libgnutls30 (>= 3.5.6).
apt:i386 depends on libseccomp2 (>= 1.0.1).
apt:i386 depends on libstdc++6 (>= 5.2).

dpkg: error processing package apt:i386 (--install):
dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for man-db (2.8.3-2) ...
Errors were encountered while processing:
apt:i386


I tried snap, but it had a x509 error, so I kind of gave up on that as well.



Can someone help me de-muck this stuff up? All the google searching I've done so far can't tell that I'm trying to re-install apt-get, and thinks I want to use apt-get to install stuff.



Ubuntu 18.04.1LTS, by the way. On a live server, 300 miles away.



EDIT: So, this server has mostly been restored to it's initial state and I got npm/nvm/pm2 working again. Checking the new logs (and old logs) I see that the root of all these issues was a failure of the certificate authority. Somewhere, in some process, something didn't download over https, and in troubleshooting the failed installation, I likely caused the rest of this mess.










share|improve this question
























  • I am running ubuntu 18.04.1 and my apt version is 1.6.6 could you try that specific version? archive.ubuntu.com/ubuntu/pool/main/a/apt/apt_1.6.6_amd64.deb
    – Hugo
    Nov 27 at 21:58










  • Looks like you are (unwisely) trying to mix packages from different releases of Ubuntu, and/or packages from non-Ubuntu sources. Example: libapt-pkg5.0 version 1.7.0~alpha3~ is not a standard Ubuntu version number, and is too high even for 18.10! Looks like you are trying to install 32-bit packages, too (why?) I think you should take this question to our sibling site Ubuntuforums.org, where gurus can hold your hand and patiently work with you one-on-one for the many days (or weeks) it will take to untangle whatever horrors you have done. AskUbuntu's format is not intended for that.
    – user535733
    Nov 27 at 23:09










  • Yeah, probably. I think I asked AskUbuntu as that's where most of today's googling landed me.
    – mainstreetmark
    Nov 27 at 23:42















up vote
1
down vote

favorite












So, during a minor update earlier, I noticed that npm wasn't working, so I began updating packages. I landed on this similar issue, so went on to get aptitude installed. Somehow, that installation failed as well. Everything I tried resulted in pages of this error:



E: The method driver /usr/lib/apt/methods/http could not be found.


So after a bunch of more messing around, i had aptitude uninstall itself, which it did. But this left me with no aptitude OR apt.



I tried to download a few of these and install them with dpkg but it fails due to just an endless list of missing dependencies.



# dpkg -i apt_1.7.0_i386.deb 
(Reading database ... 151349 files and directories currently installed.)
Preparing to unpack apt_1.7.0_i386.deb ...
Unpacking apt:i386 (1.7.0) over (1.7.0) ...
dpkg: dependency problems prevent configuration of apt:i386:
apt:i386 depends on libapt-pkg5.0 (>= 1.7.0~alpha3~).
apt:i386 depends on libc6 (>= 2.15).
apt:i386 depends on libgcc1 (>= 1:4.2).
apt:i386 depends on libgnutls30 (>= 3.5.6).
apt:i386 depends on libseccomp2 (>= 1.0.1).
apt:i386 depends on libstdc++6 (>= 5.2).

dpkg: error processing package apt:i386 (--install):
dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for man-db (2.8.3-2) ...
Errors were encountered while processing:
apt:i386


I tried snap, but it had a x509 error, so I kind of gave up on that as well.



Can someone help me de-muck this stuff up? All the google searching I've done so far can't tell that I'm trying to re-install apt-get, and thinks I want to use apt-get to install stuff.



Ubuntu 18.04.1LTS, by the way. On a live server, 300 miles away.



EDIT: So, this server has mostly been restored to it's initial state and I got npm/nvm/pm2 working again. Checking the new logs (and old logs) I see that the root of all these issues was a failure of the certificate authority. Somewhere, in some process, something didn't download over https, and in troubleshooting the failed installation, I likely caused the rest of this mess.










share|improve this question
























  • I am running ubuntu 18.04.1 and my apt version is 1.6.6 could you try that specific version? archive.ubuntu.com/ubuntu/pool/main/a/apt/apt_1.6.6_amd64.deb
    – Hugo
    Nov 27 at 21:58










  • Looks like you are (unwisely) trying to mix packages from different releases of Ubuntu, and/or packages from non-Ubuntu sources. Example: libapt-pkg5.0 version 1.7.0~alpha3~ is not a standard Ubuntu version number, and is too high even for 18.10! Looks like you are trying to install 32-bit packages, too (why?) I think you should take this question to our sibling site Ubuntuforums.org, where gurus can hold your hand and patiently work with you one-on-one for the many days (or weeks) it will take to untangle whatever horrors you have done. AskUbuntu's format is not intended for that.
    – user535733
    Nov 27 at 23:09










  • Yeah, probably. I think I asked AskUbuntu as that's where most of today's googling landed me.
    – mainstreetmark
    Nov 27 at 23:42













up vote
1
down vote

favorite









up vote
1
down vote

favorite











So, during a minor update earlier, I noticed that npm wasn't working, so I began updating packages. I landed on this similar issue, so went on to get aptitude installed. Somehow, that installation failed as well. Everything I tried resulted in pages of this error:



E: The method driver /usr/lib/apt/methods/http could not be found.


So after a bunch of more messing around, i had aptitude uninstall itself, which it did. But this left me with no aptitude OR apt.



I tried to download a few of these and install them with dpkg but it fails due to just an endless list of missing dependencies.



# dpkg -i apt_1.7.0_i386.deb 
(Reading database ... 151349 files and directories currently installed.)
Preparing to unpack apt_1.7.0_i386.deb ...
Unpacking apt:i386 (1.7.0) over (1.7.0) ...
dpkg: dependency problems prevent configuration of apt:i386:
apt:i386 depends on libapt-pkg5.0 (>= 1.7.0~alpha3~).
apt:i386 depends on libc6 (>= 2.15).
apt:i386 depends on libgcc1 (>= 1:4.2).
apt:i386 depends on libgnutls30 (>= 3.5.6).
apt:i386 depends on libseccomp2 (>= 1.0.1).
apt:i386 depends on libstdc++6 (>= 5.2).

dpkg: error processing package apt:i386 (--install):
dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for man-db (2.8.3-2) ...
Errors were encountered while processing:
apt:i386


I tried snap, but it had a x509 error, so I kind of gave up on that as well.



Can someone help me de-muck this stuff up? All the google searching I've done so far can't tell that I'm trying to re-install apt-get, and thinks I want to use apt-get to install stuff.



Ubuntu 18.04.1LTS, by the way. On a live server, 300 miles away.



EDIT: So, this server has mostly been restored to it's initial state and I got npm/nvm/pm2 working again. Checking the new logs (and old logs) I see that the root of all these issues was a failure of the certificate authority. Somewhere, in some process, something didn't download over https, and in troubleshooting the failed installation, I likely caused the rest of this mess.










share|improve this question















So, during a minor update earlier, I noticed that npm wasn't working, so I began updating packages. I landed on this similar issue, so went on to get aptitude installed. Somehow, that installation failed as well. Everything I tried resulted in pages of this error:



E: The method driver /usr/lib/apt/methods/http could not be found.


So after a bunch of more messing around, i had aptitude uninstall itself, which it did. But this left me with no aptitude OR apt.



I tried to download a few of these and install them with dpkg but it fails due to just an endless list of missing dependencies.



# dpkg -i apt_1.7.0_i386.deb 
(Reading database ... 151349 files and directories currently installed.)
Preparing to unpack apt_1.7.0_i386.deb ...
Unpacking apt:i386 (1.7.0) over (1.7.0) ...
dpkg: dependency problems prevent configuration of apt:i386:
apt:i386 depends on libapt-pkg5.0 (>= 1.7.0~alpha3~).
apt:i386 depends on libc6 (>= 2.15).
apt:i386 depends on libgcc1 (>= 1:4.2).
apt:i386 depends on libgnutls30 (>= 3.5.6).
apt:i386 depends on libseccomp2 (>= 1.0.1).
apt:i386 depends on libstdc++6 (>= 5.2).

dpkg: error processing package apt:i386 (--install):
dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for man-db (2.8.3-2) ...
Errors were encountered while processing:
apt:i386


I tried snap, but it had a x509 error, so I kind of gave up on that as well.



Can someone help me de-muck this stuff up? All the google searching I've done so far can't tell that I'm trying to re-install apt-get, and thinks I want to use apt-get to install stuff.



Ubuntu 18.04.1LTS, by the way. On a live server, 300 miles away.



EDIT: So, this server has mostly been restored to it's initial state and I got npm/nvm/pm2 working again. Checking the new logs (and old logs) I see that the root of all these issues was a failure of the certificate authority. Somewhere, in some process, something didn't download over https, and in troubleshooting the failed installation, I likely caused the rest of this mess.







apt package-management dpkg aptitude






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 28 at 15:59

























asked Nov 27 at 21:13









mainstreetmark

1185




1185












  • I am running ubuntu 18.04.1 and my apt version is 1.6.6 could you try that specific version? archive.ubuntu.com/ubuntu/pool/main/a/apt/apt_1.6.6_amd64.deb
    – Hugo
    Nov 27 at 21:58










  • Looks like you are (unwisely) trying to mix packages from different releases of Ubuntu, and/or packages from non-Ubuntu sources. Example: libapt-pkg5.0 version 1.7.0~alpha3~ is not a standard Ubuntu version number, and is too high even for 18.10! Looks like you are trying to install 32-bit packages, too (why?) I think you should take this question to our sibling site Ubuntuforums.org, where gurus can hold your hand and patiently work with you one-on-one for the many days (or weeks) it will take to untangle whatever horrors you have done. AskUbuntu's format is not intended for that.
    – user535733
    Nov 27 at 23:09










  • Yeah, probably. I think I asked AskUbuntu as that's where most of today's googling landed me.
    – mainstreetmark
    Nov 27 at 23:42


















  • I am running ubuntu 18.04.1 and my apt version is 1.6.6 could you try that specific version? archive.ubuntu.com/ubuntu/pool/main/a/apt/apt_1.6.6_amd64.deb
    – Hugo
    Nov 27 at 21:58










  • Looks like you are (unwisely) trying to mix packages from different releases of Ubuntu, and/or packages from non-Ubuntu sources. Example: libapt-pkg5.0 version 1.7.0~alpha3~ is not a standard Ubuntu version number, and is too high even for 18.10! Looks like you are trying to install 32-bit packages, too (why?) I think you should take this question to our sibling site Ubuntuforums.org, where gurus can hold your hand and patiently work with you one-on-one for the many days (or weeks) it will take to untangle whatever horrors you have done. AskUbuntu's format is not intended for that.
    – user535733
    Nov 27 at 23:09










  • Yeah, probably. I think I asked AskUbuntu as that's where most of today's googling landed me.
    – mainstreetmark
    Nov 27 at 23:42
















I am running ubuntu 18.04.1 and my apt version is 1.6.6 could you try that specific version? archive.ubuntu.com/ubuntu/pool/main/a/apt/apt_1.6.6_amd64.deb
– Hugo
Nov 27 at 21:58




I am running ubuntu 18.04.1 and my apt version is 1.6.6 could you try that specific version? archive.ubuntu.com/ubuntu/pool/main/a/apt/apt_1.6.6_amd64.deb
– Hugo
Nov 27 at 21:58












Looks like you are (unwisely) trying to mix packages from different releases of Ubuntu, and/or packages from non-Ubuntu sources. Example: libapt-pkg5.0 version 1.7.0~alpha3~ is not a standard Ubuntu version number, and is too high even for 18.10! Looks like you are trying to install 32-bit packages, too (why?) I think you should take this question to our sibling site Ubuntuforums.org, where gurus can hold your hand and patiently work with you one-on-one for the many days (or weeks) it will take to untangle whatever horrors you have done. AskUbuntu's format is not intended for that.
– user535733
Nov 27 at 23:09




Looks like you are (unwisely) trying to mix packages from different releases of Ubuntu, and/or packages from non-Ubuntu sources. Example: libapt-pkg5.0 version 1.7.0~alpha3~ is not a standard Ubuntu version number, and is too high even for 18.10! Looks like you are trying to install 32-bit packages, too (why?) I think you should take this question to our sibling site Ubuntuforums.org, where gurus can hold your hand and patiently work with you one-on-one for the many days (or weeks) it will take to untangle whatever horrors you have done. AskUbuntu's format is not intended for that.
– user535733
Nov 27 at 23:09












Yeah, probably. I think I asked AskUbuntu as that's where most of today's googling landed me.
– mainstreetmark
Nov 27 at 23:42




Yeah, probably. I think I asked AskUbuntu as that's where most of today's googling landed me.
– mainstreetmark
Nov 27 at 23:42










1 Answer
1






active

oldest

votes

















up vote
2
down vote



accepted










I'm not OP, but I worked on the machine in question just now and figured it's best to put the solution here in case anyone else has the same problem in the future.



I first got a copy of the apt package he removed (1.6.3 instead of 1.7). This gave me a missing dependency of libgcc1.4.9, which I went and fetched. libgcc complained about not having gcc-4.9-base, which I then went and found. gcc-4.9-base installed without issue. libgcc had a conflict in /usr/local/doc/libgcc1 , so I removed what was already there and reinstalled the dependency. Then apt installed without issue. I was able to "apt list" without issue, and handed the machine back to mainstreetmark.






share|improve this answer





















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    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: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1096618%2fbroken-npm-so-tried-aptitude-which-broke-apt-and-aptitude-leaving-me-with-no-p%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    2
    down vote



    accepted










    I'm not OP, but I worked on the machine in question just now and figured it's best to put the solution here in case anyone else has the same problem in the future.



    I first got a copy of the apt package he removed (1.6.3 instead of 1.7). This gave me a missing dependency of libgcc1.4.9, which I went and fetched. libgcc complained about not having gcc-4.9-base, which I then went and found. gcc-4.9-base installed without issue. libgcc had a conflict in /usr/local/doc/libgcc1 , so I removed what was already there and reinstalled the dependency. Then apt installed without issue. I was able to "apt list" without issue, and handed the machine back to mainstreetmark.






    share|improve this answer

























      up vote
      2
      down vote



      accepted










      I'm not OP, but I worked on the machine in question just now and figured it's best to put the solution here in case anyone else has the same problem in the future.



      I first got a copy of the apt package he removed (1.6.3 instead of 1.7). This gave me a missing dependency of libgcc1.4.9, which I went and fetched. libgcc complained about not having gcc-4.9-base, which I then went and found. gcc-4.9-base installed without issue. libgcc had a conflict in /usr/local/doc/libgcc1 , so I removed what was already there and reinstalled the dependency. Then apt installed without issue. I was able to "apt list" without issue, and handed the machine back to mainstreetmark.






      share|improve this answer























        up vote
        2
        down vote



        accepted







        up vote
        2
        down vote



        accepted






        I'm not OP, but I worked on the machine in question just now and figured it's best to put the solution here in case anyone else has the same problem in the future.



        I first got a copy of the apt package he removed (1.6.3 instead of 1.7). This gave me a missing dependency of libgcc1.4.9, which I went and fetched. libgcc complained about not having gcc-4.9-base, which I then went and found. gcc-4.9-base installed without issue. libgcc had a conflict in /usr/local/doc/libgcc1 , so I removed what was already there and reinstalled the dependency. Then apt installed without issue. I was able to "apt list" without issue, and handed the machine back to mainstreetmark.






        share|improve this answer












        I'm not OP, but I worked on the machine in question just now and figured it's best to put the solution here in case anyone else has the same problem in the future.



        I first got a copy of the apt package he removed (1.6.3 instead of 1.7). This gave me a missing dependency of libgcc1.4.9, which I went and fetched. libgcc complained about not having gcc-4.9-base, which I then went and found. gcc-4.9-base installed without issue. libgcc had a conflict in /usr/local/doc/libgcc1 , so I removed what was already there and reinstalled the dependency. Then apt installed without issue. I was able to "apt list" without issue, and handed the machine back to mainstreetmark.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 28 at 0:14









        Warren Krewenki

        1562




        1562






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1096618%2fbroken-npm-so-tried-aptitude-which-broke-apt-and-aptitude-leaving-me-with-no-p%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Ellipse (mathématiques)

            Quarter-circle Tiles

            Mont Emei