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.
Is lenny stable yet or still testing? Looked online but could determine...
If lenny is still testing but about to become stable, am I ok to install lenny testing right now? Will keeping my lines in sources.list as testing cause any problems during the switch? For example:
Here is how to upgrade from Debian Etch to Debian Lenny. I did this on October 13, 2008 and have been running Lenny with no problems since:
Upgrading from Etch to Lenny:
1. Open a terminal and type sudo su
2. Now type cd /etc/apt/ && gedit sources.list
3. Replace all occurrences of etch with lenny and save the file
4. Back at the terminal type apt-get update
5. Once the update has finished type apt-get dist-upgrade (and follow any onscreen instructions)
If all goes well, once finished you should be able to reboot into your new Debian Lenny kernel.
I've upgraded 5 Etch boxes to Lenny. I'm loving Lenny. Just in case I would back-up all of your data just prior to the upgrade in the unlikely event things go awry.
I would also download, burn a copy of the netinstall iso for Lenny. You can use that to do a clean install of Lenny if the upgrade doesn't work out and then copy over your backed-up data afterwards.
Have fun.
Whoops, I should have been a bit clearer. I'm running lenny now. When it moves to the stable branch, will I need to do anything in my sources.list or just cruise along as usual doing regular aptitude update and installs?
If you plan to stick with Lenny after it becomes stable, you need to change your sources list.. I would do it now..
if your sources list is set to testing when lenny becomes stable you will then be running Squeeze the new code name for the testing branch once lenny is the new stable, and etch becomes oldstable.
By changing your sources list from testing to lenny you will stick with Lenny no matter what else happens..
put lenny in your sources.list. If you have testing then you will get massive update of the packages waiting in unstable due to the freeze.will be funny here on lq as for every release
People having testing in their sources will have a big surprise as they will in fact be running the same as unstable.
Thanks everyone for the info. Farslayer, this is exactly what I needed to understand:
"if your sources list is set to testing when lenny becomes stable you will then be running Squeeze the new code name for the testing branch once lenny is the new stable, and etch becomes oldstable.
By changing your sources list from testing to lenny you will stick with Lenny no matter what else happens.."
Thanks,
pb
Last edited by parent's_basement; 02-11-2009 at 02:57 PM.
If you have testing then you will get massive update of the packages waiting in unstable due to the freeze.will be funny here on lq as for every release
People having testing in their sources will have a big surprise as they will in fact be running the same as unstable.
Yeah, I've got testing in my sources.list, and this morning (I hadn't booted into Debian for about a day) I got 47 updates. No problems though - so far.
My sources are set to "testing" and lo and behold, I just got an alert that 220 packages are available. I'm going to flow with it and see what happens. Real life example of what you guys are talking about ROFL!
As a more general answer, if you are a home user (as opposed to a sysadmin running servers for hundreds of clients) then you are quite safe tracking testing. I've been using testing since the "woody" days and never had a major problem, only really minor niggles. Debian is really quite conservative in this respect unlike certain other distros based on debian which can be a little more, shall we say, adventurous.
cheers,
jdk
In my opinion, it's better to have your sources list pointing at Lenny rather than testing, for example, to avoid any confusion!
Sorry Rich, but what kind of confusion? sources pointing at Lenny and those pointing at testing mean two different things. In one case they mean "I want to follow testing"; in the other, "I want to follow Lenny". They may mean the same thing at the moment but they won't in a couple of weeks. Just like testing and Squeeze (Lenny's successor) won't always point to the same repos.
Cheers,
jdk
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.