Better way to handle kept back package: sudo aptitude If you have kept back package you should see Upgradable Packages on top of the list. Provide details and share your research! You have to especially pay attention to the list of packages to be removed. After unpacking 1860kB of additional disk space will be used. I currently mostly use upgrade instead since I once almost uninstalled Plesk because of a dist-upgrade late in the night. Think of it like fixing a car. It will always do that when there would be a version conflict otherwise.
Done The following packages have been kept back: ffmpeg mjpegtools transcode 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. Run upgrade first and then dist-upgrade? Running apt-get install packagenameÂ is more specific about what it does. If Pablo's solution works for you, please upvote it. Otherwise you won't be able to post any information on this site. . Then answer the questions and follow the instructions.
Instead, simply run apt-get install packagenameÂ to resolve those dependencies and to upgrade the package. Done The following packages have been kept back: kopano-backup kopano-client kopano-common kopano-contacts kopano-dagent kopano-gateway kopano-ical kopano-monitor kopano-presence kopano-search kopano-server kopano-server-packages kopano-spooler kopano-utils libkcserver0 libkcsoap0 libmapi1 php5-mapi python-mapi 0 upgraded, 0 newly installed, 0 to remove and 19 not upgraded. Packages currently installed with new versions available are retrieved and upgraded; under no circumstances are currently installed packages removed, or packages not already installed retrieved and installed. . Write back if you need more help. These are mainly kernel related packages namely, linux-generic-lts-vivid, linux-headers-generic-lts-vivid, linux-image-generic-lts-vivid. A regular apt-get upgrade command will install any package from any software source that is enabled; dist-upgrade is not unique in this way.
To fix this you must run : apt-get dist-upgrade This will upgrade the packages that have newer versions available, and install any new dependencies which are required to do that. Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Upgrading the system Once you have taken the previous steps, you are now ready to continue with the main part of the upgrade. Done rake is already the newest version. Done The following packages have been kept back: mailutils 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. . I've had similar experiences with the update-manager where it would upgrade the kernel and then some hardware wouldn't work correctly e.
As apt-get suggests it self, you should just run the autoremove command to safely remove the unnecessary packages: sudo apt-get autoremove Post navigation Leave a Reply Your email address will not be published. Package sendmail-bin which provides mail-transport-agent is not configured yet. The below example outputs are from a Ubuntu 12. Here is what I get with showpkg. .
It means that the new rails package has different dependencies that the older one which is installed, and that at least one of the dependencies of the new rails package is not installed. If you do apt-cache policy linux-generic-lts-vivid you will be able to see what repository the updates originated in - it's either a bug fix in trusty-updates or a Security update in trusty-security. From man aptitude: safe-upgrade Upgrades installed packages to their most recent version. Most likely these packages are held back because their installation would create dependency inconsistencies. . Done Building dependency tree Reading state information. .
What you're seeing is a backported Kernel. . . Wait for them to settle down and you may not need to dist-upgrade at all. Just running sudo apt-get upgrade will only install new versions of packages that you already have on your system. Now sarge is no longer stable, but oldstable, and even a dist-upgrade will hold the related updates back. .
Cautious solution 2: The cautious solution is to run sudo apt-get install. I'm not sure which rake is installed, or how to specify the correct one. I'm not sure which rake is installed, or how to specify the correct one. One poster indicated that there might be other reasons. This is the command I used to install rails. Description It means that the new rails package has different dependencies that the older one which is installed, and that at least one of the dependencies of the new rails package is not installed.