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.
I'd say stick with testing. If you do upgrade to sid, be very careful every time you do an upgrade. Blindly using Apt-get to upgrade in sid can be very bad. Use aptitude to upgrade and pay close attention to what is getting upgraded and WHAT IS BEING REMOVED. Because the packages in sid are being constantly updated, dependencies can get really screwed up. I have had sid try to uninstall most of my system on numerous occasions when I tried to upgrade. Testing is just fine for me.
ok. thanks. Approx. how long does it take for a package to get from sid to testing? Mostly what I'm looking for is k3b, which isn't in testing currently.
Approx. how long does it take for a package to get from sid to testing?
That is a moving target, based not only on the condition of the package in question (read the bug reports please), but also on the FTP maintainer, and the build status of the applicable dependent libraries, to mention only a few. Since KDE is currently undergoing a C++ ABI transition, it will probably take a more lengthy period of time than might otherwise be the case.
ok, thanks. I think I'll stick w/ etch for now, as it just updated a bunch, and one of the reasons I wanted to go to sid(openoffice.org2.0)just came in. Thanks again.
I've been contemplating ugrading to sid, but I don't want my system to be continuously broken. Is it worth upgrading to sid?
If you have the time to hand-hold your system, SID can be a great learning experience. However, you do need to expect there can (and will) be significant breakages, and be prepared to read a lot of bug reports. I certainly would not take that step over just a package or two.HERE'S a nice mailing list entry on how SID was affected by the KDE transistion.
I have been using SID for awhile now and haven't had any major issue with it. I don't have KDE installed so I don't have to worry about all the stuff happening with it right now. Obviously something's mess up in Sid but overall I am happy with it. Although I enjoy using bleeding edge software and fiddling with things to get them to work right. I am using Sid with Enlightenment D17 and am happy with it. Haven't had an unusable system or major crash since I installed it 3 or 4 months ago, and I apt-get upgrade pretty much daily.
Last edited by MustangCSA; 01-04-2006 at 06:19 PM.
I think Sid is fine if you just pay even nominal attention to what packages are going in and out of your system (i.e. if something wants to uninstall that appears to be something you need, just cancel whatever it is you're installing). Right now I have a mixed stable/unstable (sarge/sid) system, and it's perfectly stable. I haven't done an upgrade because I don't need one. I just upgrade or install the software I want. I do this more because I'm on dial-up than by choice.
KDE was broken much longer (and worse, I think) in testing. That's the main issue that made me switch to unstable. And pay more attention to what I'm actually doing when I do a major upgrade. I really think unstable is just as "stable" as testing for the most part.
I have been using SID for awhile now and haven't had any major issue with it. I don't have KDE installed so I don't have to worry about all the stuff happening with it right now. Obviously something's mess up in Sid but overall I am happy with it. Although I enjoy using bleeding edge software and fiddling with things to get them to work right. I am using Sid with Enlightenment D17 and am happy with it. Haven't had an unusable system or major crash since I installed it 3 or 4 months ago, and I apt-get upgrade pretty much daily.
Quote:
Originally Posted by Xian
Yeah, if you are running KDE-free then there are quite a number of issues that don't come your way right now.
I use a mixture of Sarge / Sid with all new packages installed from Sid and I don't have too many problems with the unstable stuff. I do not use KDE. The question of Stable vs. Testing vs. Unstable is discussed all the time; some say that no one really needs testing, that production or mission critical boxes should use stable with security updates and that home users / hobbyists should use unstable, which seems about right to me.
I started with Woody when it was stable but close to the release of Sarge and was really annoyed at how much current stuff wasn't there or outdated (I started playing with backports, but never really liked the idea - perhaps I wasn't proficient enough to know what I was doing). I then installed Sarge (which was still testing) and was much happier, but eventually ran into the same problems as Sarge became stable and then began to become outdated (and even Testing before a freeze isn't as up to date as Unstable, which is the whole point of the OP), so I switched my apt sources to Sid, and have been quite happy since.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.