Announcement

Collapse
No announcement yet.

Unable to update system, problem in apt manager

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    [SOLVED] Unable to update system, problem in apt manager

    Hello, I've been trying to update my system today the entire day but not able to figure out what is wrong with the system.

    Code:
    mohit@Dell3568:~$ sudo apt install npm
    Reading package lists... Done
    Building dependency tree 
    Reading state information... Done
    You might want to run 'apt --fix-broken install' to correct these.
    The following packages have unmet dependencies:
    mono-devel : Depends: ca-certificates-mono (= 6.0.0.319-0xamarin1+ubuntu1804b1) but 5.18.1.28-0xamarin5+ubuntu1804b1 is installed
    E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
    When I run apt --fix-broken install it generates a very big output that I saved in a file, that is attached.

    Any help will be really appreciated, I need to install npm for development but I'm not able to do that.

    And

    Code:
    mohit@Dell3568:~$ sudo apt update
    Hit:1 http://in.archive.ubuntu.com/ubuntu bionic InRelease
    Ign:2 http://dl.google.com/linux/earth/deb stable InRelease                                                                          
    Hit:3 http://packages.microsoft.com/repos/vscode stable InRelease                                                                    
    Hit:4 http://in.archive.ubuntu.com/ubuntu bionic-updates InRelease                                                                   
    Hit:5 http://in.archive.ubuntu.com/ubuntu bionic-backports InRelease                                                                 
    Hit:6 http://security.ubuntu.com/ubuntu bionic-security InRelease                                                                    
    Hit:7 https://packages.microsoft.com/ubuntu/18.04/prod bionic InRelease                                              
    Hit:8 http://dl.google.com/linux/earth/deb stable Release                                      
    Hit:9 https://download.mono-project.com/repo/ubuntu vs-bionic InRelease
    Reading package lists... Done                 
    Building dependency tree       
    Reading state information... Done
    32 packages can be upgraded. Run 'apt list --upgradable' to see them.
    N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'http://dl.google.com/linux/earth/deb stable InRelease' doesn't support architecture 'i386'
    Thanks in advance
    Last edited by mohittomar13; Aug 08, 2019, 11:25 AM.

    #2
    After running apt update, did you then run apt full-upgrade to update your system, then try installing npm again?

    The package database could have been out of date if you didn't run apt update before trying to install packages.

    it also might be worth trying different apt repos, if the ones for your country are having temporary issues search for 'software sources' in your Kmenu, or Krunner, and try switching from the India servers the main servers, and see if there is a difference, if the above does not work.


    Your attachment didn't get uploaded or attached to your post. Probably better to use a pastebin like https://paste.ubuntu.com, and link to that. If you did not run apt update beforehand, the output of the 'fix-missing' option will likely be very messy.


    The output you show for your apt update output is correct and normal, no issues there.
    Last edited by claydoh; Aug 08, 2019, 11:48 AM.

    Comment


      #3
      Actually, I noticed this:

      Code:
      mono-devel : Depends: ca-certificates-mono (= 6.0.0.319-0xamarin1+ubuntu1804b1) but 5.18.1.28-0xamarin5+ubuntu1804b1 is installed
      What external sources have you added? This is definitely not an Ubuntu package, and either is an issue with that third party repo, or, as I mentioned above, you did not run apt update before trying to install npm., and your package database is out of sync with the repos.

      Comment


        #4
        Wouldn't running the full upgrade, upgrade my version of LTS 18.04 to 19.xx. I don't want to do that. And I ran sudo apt update and sudo apt upgrade. As far mono is concerned my friend installed that on my machine and he is not in the country.

        Comment


          #5
          Originally posted by mohittomar13 View Post
          Wouldn't running the full upgrade, upgrade my version of LTS 18.04 to 19.xx.
          No, it would not. It just does as bit more (if required) to upgrade packages on your current system - e.g. installing new packages where dependencies require it.
          On #kubuntu-devel & #kubuntu on libera.chat - IRC Nick: RikMills - Launchpad ID: click

          Comment


            #6
            I have the same problem, the sources used were:

            deb https://download.mono-project.com/repo/ubuntu vs-bionic main

            https://www.mono-project.com/download/stable/ for ubuntu 18.04

            Comment


              #7
              Probably more relevant over here: https://github.com/mono/mono/issues/16130

              Comment


                #8
                Originally posted by acheron View Post
                No, it would not. It just does as bit more (if required) to upgrade packages on your current system - e.g. installing new packages where dependencies require it.
                Yes, sorry I confused dist-upgrade with full-upgrade. I will do a full upgrade and will post the results soon. Right now internet is not fast enough to perform an update. Thanks :-)

                Comment


                  #9
                  Originally posted by mohittomar13 View Post
                  Yes, sorry I confused dist-upgrade with full-upgrade.
                  dist-upgrade (sudo apt-get dist-upgrade) and full-upgrade (sudo apt full-upgrade) do the same thing. Neither changes the version of the OS you are using.
                  Using Kubuntu Linux since March 23, 2007
                  "It is a capital mistake to theorize before one has data." - Sherlock Holmes

                  Comment


                    #10
                    Originally posted by Snowhog View Post
                    dist-upgrade (sudo apt-get dist-upgrade) and full-upgrade (sudo apt full-upgrade) do the same thing. Neither changes the version of the OS you are using.
                    Ohh.. I thought dist-upgrade, upgrades the distribution to a new version and I will loose LTS support.

                    Well anyways, I ran the commands and still it is giving the same error. Should I uninstall and then reinstall mono?? By the way following are the results of the commands.

                    Code:
                    mohit@Dell3568:~$ sudo apt update
                    Hit:1 http://in.archive.ubuntu.com/ubuntu bionic InRelease
                    Hit:2 http://in.archive.ubuntu.com/ubuntu bionic-updates InRelease                                                                   i
                    Hit:3 http://packages.microsoft.com/repos/vscode stable InRelease                                                                    
                    Ign:4 http://dl.google.com/linux/earth/deb stable InRelease                                                                          
                    Hit:5 http://in.archive.ubuntu.com/ubuntu bionic-backports InRelease                                                                 
                    Hit:6 http://security.ubuntu.com/ubuntu bionic-security InRelease                                                                    
                    Hit:7 http://dl.google.com/linux/earth/deb stable Release                                                                            
                    Hit:8 https://download.mono-project.com/repo/ubuntu vs-bionic InRelease                        
                    Hit:9 https://packages.microsoft.com/ubuntu/18.04/prod bionic InRelease
                    Reading package lists... Done                    
                    Building dependency tree       
                    Reading state information... Done
                    38 packages can be upgraded. Run 'apt list --upgradable' to see them.
                    N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'http://dl.google.com/linux/earth/deb stable InRelease' doesn't support architecture 'i386'
                    
                    mohit@Dell3568:~$ sudo apt full-upgrade 
                    Reading package lists... Done
                    Building dependency tree       
                    Reading state information... Done
                    You might want to run 'apt --fix-broken install' to correct these.
                    The following packages have unmet dependencies:
                    mono-devel : Depends: libmono-2.0-dev (>= 6.0.0.319-0xamarin2+ubuntu1804b1) but 6.0.0.319-0xamarin1+ubuntu1804b1 is installed
                               Depends: ca-certificates-mono (= 6.0.0.319-0xamarin2+ubuntu1804b1) but 5.18.1.28-0xamarin5+ubuntu1804b1 is installed
                    E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
                    mohit@Dell3568:~$
                    THought I was not able to capture the entire output I have the following link for whatever error I got from apt-get --fix-broken install

                    https://paste.ubuntu.com/p/znKgy7GkqH/
                    Last edited by mohittomar13; Aug 11, 2019, 02:40 AM.

                    Comment


                      #11
                      Uninstalling and reinstalling won't help as the problem likely is with the mono repository you added. Their packaging is what is causing the conflicts. It is looking for something with a different version than what is actually available. You'll have to contact them.

                      Sent from my LG-H931 using Tapatalk

                      Comment


                        #12
                        However. It might be worth trying

                        sudo apt-get -f install

                        And then

                        sudo dpkg --configure -a

                        The output of the fix-missing command looks wrong for some reason, it looks more like a debugging output or a crash report.

                        Unless the mono repo is either fixed, or you uninstall all the mono components you have installed and/or remove the repo, this error won't go away.

                        Sent from my LG-H931 using Tapatalk

                        Comment


                          #13
                          Thanks for your help claydoh. But, nothing seems to work. How can I completely remove all the components of mono from my system, as you suggested? If needed again I will install it, right now I don't need it. I'm working mostly on web development using other technologies not .Net.

                          I ran sudo apt-get -f install and dpkg --configure -a but these are producing output similar to sudo apt-get --fix-broken install.

                          I tried sudo apt-get purge monodevelop but it is giving me the same error "Some packages have unmet dependencies" and asks to run sudo apt-get --fix-broken install.

                          Thanks again.
                          Last edited by mohittomar13; Aug 11, 2019, 07:51 AM.

                          Comment


                            #14
                            You may have to run both commands several times, as it can take several 'passes' of each before everything is 'fixed'. This isn't always the case, but each running of both commands 'can' fix one or more of the issues, allowing the subsequent instances to fix more.
                            Using Kubuntu Linux since March 23, 2007
                            "It is a capital mistake to theorize before one has data." - Sherlock Holmes

                            Comment


                              #15
                              Actually, can-do-noir gave us info that leads to a fix

                              The link
                              https://github.com/mono/mono/issues/16130
                              also has a link to another report that has a fix
                              https://github.com/mono/monodevelop/issues/8356

                              goi8ng back to the bug reports for new info is always a good idea

                              Comment

                              Working...
                              X