DebianThis forum is for the discussion of Debian Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Today I went to install a package using aptitude.
When I hit the "g" key to get the review of what aptitude will install, there was a considerable list of packages shown under the heading of Packages being held back.
The explanation in the lower part of the screen states that these packages could be upgraded but won't be because I've requested them to remain at there current version.
The problem is, It's my box and I have made no such request.
Is this the normal behavior of aptitude?
Naturally all of the packages are listed as installed. Most, but not all, also have an A tag, which, if I'm not mistaken, indicates it was installed as a dependency. All are also tagged with a U, which I thought meant to upgrade that package but obviously I'm wrong.
Could somebody please explain this behavior?
I realize all I have to do is select the heading and press the + to have the packages upgraded but I'd like to understand why the system believes I've issued the hold command.
They won't upgrade simply because you're installing a specific package. If you want to upgrade all the packages already on your system "aptitude upgrade." If you want to upgrade everything to the current version of the default installation "aptitude dist-upgrade." Don't forget to "aptitude update" first.
Also these instructions are for using aptitude from the command line. I never have bothered to figure out the ncurses interface.
Pinning not being set up right might be behind your issues. I would make sure that is set up correctly first. If it is, then you could follow those instruction for using dpkg to change the status of the packages you don't want held. Assuming they're marked as held and that is the problem.