DebianThis forum is for the discussion of Debian Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The first of many post-freeze goodies(?) to come...
One package I've been keeping an eye on is libc6. 2.5 has been sitting in experimental for a while, given its version (2.5-0exp6), I don't believe it's sitting there due to the etch freeze, so I wouldn't worry about it for a while. But, when it does arrive in Sid, it will be quite a trick to upgrade smoothly.
There is no upgrade that will happen with your current config. It is in essence a downgrade, because Etch moved from testing to stable.
But my sources.list says "testing", so wouldn't that *now* be Lenny instead of Etch? If I'm still set for testing, and testing is now Lenny, then my config should be set to Lenny, no?
One package I've been keeping an eye on is libc6. 2.5 has been sitting in experimental for a while, given its version (2.5-0exp6), I don't believe it's sitting there due to the etch freeze, so I wouldn't worry about it for a while. But, when it does arrive in Sid, it will be quite a trick to upgrade smoothly.
I have been using 2.5_experimental for a while with no problems.
Quote:
1. glibc 2.4 drops support for non-NPTL kernels (i.e. 2.4 and earlier Linux kernels); since Sarge's default kernel was still a 2.4-based kernel, upgrading to a glibc 2.4 will immediately break everything on your system
I have been using 2.5_experimental for a while with no problems.
I give debian developers too little credit then. I remember a while ago, upgrading to 2.3.6 from an earlier 2.3 caused several problems with existing packages and overall stability took a hit. 2.3 to 2.5 is quite a large leap and a libc upgrade would normally mean recompiling nearly everything against the newer version. In any case I think I'll still exercise caution...
But my sources.list says "testing", so wouldn't that *now* be Lenny instead of Etch?
yes.
Quote:
If I'm still set for testing, and testing is now Lenny, then my config should be set to Lenny, no?
lenny or testing, either one. lenny is now a link to testing, etch used to be a link to testing, but now it's a link to stable. Or maybe it's the other way round(testing is a link to lenny (?))... The meat of it though is that lenny and testing are now interchangable terms as far as your sources.list is concerned. As are etch and stable.
the dist-upgrade I did after reading in the wee hours on /. about Etch going stable was problem free. I'm going to run stable for a few months I think, or until there's something in testing I want to use.
The only thing which dislodged me from Debian Sarge was when I bought a motherboard which Sarge couldn't handle. Since that time, I had a love/hate relationship with Etch--I loved that it actually worked, but avoiding unexpected software updates was the reason I ran Sarge in the first place. Now, I get to have stability again! Hooray!
The meat of it though is that lenny and testing are now interchangable terms as far as your sources.list is concerned. As are etch and stable.
So does that mean that as updates and new packages are put into the Lenny/testing repository, I'll be getting them?
If yes, then is there any compelling reason for me to also do a dist-upgrade? Or should I just let the testing updates filter in through normal apt updates?
So does that mean that as updates and new packages are put into the Lenny/testing repository, I'll be getting them?
If yes, then is there any compelling reason for me to also do a dist-upgrade? Or should I just let the testing updates filter in through normal apt updates?
Thanks for the help.
OMG... there is no need at all to do a dist-upgrade... You ONLY need to do a dist upgrade if you are changing to a newer dist. Since you've been running TESTING for months now, and you havent changed your sources, you are STILL running TESTING. Only do a dist-upgrade if you are changing from stable to testing, or from testing to unstable, etc etc. Name changes (etch to lenny) have no effect to you since you are linked to testing.
I'm looking forward to the stability of Etch now that it is stable.
Get a clue... Etch has been stable for months now on most architectures (which most probably includes yours). Unless you use an "off-the-wall" architecture, like sparc, then you've been running the exact same Etch as you are now for months. Nothing has changed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
