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.
To install a new package, it is just as it ever was, apt-get install <package>. If the package exists in Stable, then that is what it will grab. If the package exists only in Unstable, then from Unstable it will be gotten.
What if the package exists in both Stable and Unstable, but we want the Unstable version? There are two ways we can do that, each with a slightly different syntax, and each with a slightly different effect.
apt-get install <package>/unstable
This will install the unstable version of the package, and try to meet any dependencies from Stable. This may not work, but it will tell you why:
Now the bootcd package is in both stable and testing, then why did it get downloaded from testing??
yea, it's true, you are giving priority to stable. But i think the bootcd is much latest in testing then the bootcd of stable. That's why it's taking the bootcd from testing. Can you please inform the booth version of bootcd ?
Yes it is spelled correctly and I run apt-get update everytime
Yes I will add those line in the apt.conf file and see if it still downloads packages from etch instead of stable.
EDIT: Also of Pinning is specific to package, then why did the specific package bootcd got installed from etch.
Well I went one step ahead. I changed all the instances of Sarge with Stable and Etch with testing in the /etc/apt/preferences, /etc/apt/sources.lst, /etc/apt/apt.conf. And now apt-get downloads package from stable instead of testing.
How do you explain this???
According to Debian Doc, Stable is just a pointer to Sarge and it should not matter what name you give?