Joined: Dec. 2006
||Posted: Jan. 05 2007,07:23
I strongly suggest, from personal experience, to try to stick with the oldstable as long as you can, until all the mirrors have gotten rid of it.
I just tried the trick of downloading cron from stable. It was the most useless cron I have ever used. OK, probably not cron's fault, but it was incompatible with DSL enough that it wouldn't run jobs. Using my good trusty friend Google, I tracked down a couple of working Debian mirrors still hosting oldstable. Changed the sources.list file to suit, and voila, working cron!
My point is this: oldstable is spelled differently to stable for a reason. Some packages MAY work fine from stable with DSL, there may not be enough different between versions to affect anything. Unfortunately, there are programs in stable that just won't work with DSL, at least not without a lot of messing around with settings and such. To help out a bit, I'll post a couple such servers here for you to use (as of the time of this post they are working). They're in sources format, so you can just copy and paste these lines directly into sources.list.
#deb http://ftp.br.debian.org/debian/ oldstable main contrib non-free
#deb http://mirror.aarnet.edu.au/debian oldstable main contrib non-free
#deb http://mirror.linux.org.au/debian oldstable main contrib non-free
#deb http://mirrors.usc.edu/pub/linux/distributions/debian oldstable main contrib non-free
Just remove the # from the beginning of one of those (and add a # to the beginning of any other sources for oldstable/stable), and run apt-get update. Hopefully, one of those servers will still be up for you.
What I want to know is, why is Debian appearing to be removing this version (woody) from their servers, when they've left up even older versions??? Unless they're just in the process of transferring woody to their archive servers with the other older versions. One can only hope, because apt in DSL depends on these servers!