I'm adding this answer because I'm not satisfied with how other answers handle the why part of the question to understand what's going on and choose the appropriate course of action. If you're feeling lucky, you can drop your car off with your cousin dist-upgrade and hope she knows her stuff. if you have time and are handy with a wrench, you'll get some peace of mind by reading up and doing the repair yourself. but you're probably better off learning a bit more about APT and resolving the dependency issues "by hand" by installing and removing packages on a case-by-case basis. So if you find yourself in a place where the "cautious solution" doesn't work, dist-upgrade may work. Unlike you, APT isn't always smart enough to know whether these additions and removals could wreak havoc. Unlike upgrade it may remove packages to resolve complex dependency situations. In most cases this will give the kept-back packages what they need to successfully upgrade.Ī more aggressive solution is to run sudo apt-get dist-upgrade, which will force the installation of those new dependencies.īut dist-upgrade can be quite dangerous. The cautious solution is to run sudo apt-get install. If Pablo's solution works for you, please upvote it. This has the benefit of not marking the kept-back packages as "manually installed," which could force more user intervention down the line (see comments). Per Pablo's answer, you can run sudo apt-get -with-new-pkgs upgrade, and it will install the kept-back packages. Another reason is that phased updates may be enabled, and the updates have not yet been released for your machine.) (Note that this is not the only reason that you may be seeing the message "packages have been kept back". If the dependencies have changed on one of the packages you have installed so that a new package must be installed to perform the upgrade then that will be listed as "kept-back".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |