Slashdot Mirror
Bugs Delay Release of Debian Lenny
A. B. VerHausen writes to tell us that over 200 release-critical bugs continue to push back Debian Lenny's release date. Originally slated for a September release, there is still a long road to be traveled before Lenny sees the light of day. Project leader Steve McIntyre says they may consider dropping some packages for the release if they continue to cause problems, and while an end of October release is the goal, only time will tell.
Shocking!!!
Seriously, this doesn't seem unusual. I'm happy that the team is waiting until all the bugs are squashed.
This is good news. There are many distributions that just take the latest and greatest of every package without doing proper quality control (Ubuntu, Gentoo, Fedora, etc). The price they pay is regressions and stuff that doesn't work. There needs to be distros like Debian which, while always delayed, has all the important bugs ironed out.
Football Odds
1. Release is as is 2. Call it Ubuntu 3. ????? 4. ENDLESS PROFIT!!!
Anybody want my mod points?
For production quality operating systems there is *nothing* better than release when ready. Given the sheer number of packages and diversity of platforms, all the Debian volunteers do a great job.
It remains the corner-case user who needs the latest and greatest release of any given package.
As an fyi, I've been running Lenny for at least 6 months as a clean-install desktop with no issues. Upgrading from stable to Lenny had issues for me. I've got two servers running Lenny without show-stopper bugs right now.
Lenny's got a really nice KDE4 in an unofficial repo at deb http://kde4.debian.net/ . I encourage users to check it out. Don't enter bugs against these packages in Debian though.
http://www.maxineudall.com/2010/02/should-economists-be-sued-for-malpractice.html
Actually, I think we would be glad if Microsoft was holding back a release because of critical bugs. Sure, there would be the occasional jackhole who said Microsoft sucks because they can't keep a release date. But, if they were being as open as Debian and admitting to fixing critical bugs (and presenting them for us to see), I'm sure there would be some insightful comments about the increased quality being worth the wait.
Seriously.
If this is happening, first check the changelog for the affected package in /usr/share/doc. If it is out of date or missing, you need to file a severity minor (with the following rationale) against the packages missing the updated changelog. This is not a violation of Debian policy (which would warrant a severity of serious), but it's suggested by policy and trivial to add.
Who? Only a few thousand sysadmins, researchers, and other conscientious geeks. There's so much more going on in the real world than you'll hear about in the media...
Caveat Utilitor
I am laughing very hard that RHEL tried to say there's no such thing as a '.0' or '.1' release, and it's all 'RHEL 4' or 'RHEL 5'. Take a look at the available media, though, and you'll see that they're really still doing what they did with the old RedHat 6 and RedHat 7: .0 is unstable, .1 has bugfixes, .2 is stable.
The above user does not want to install the packages unless they have a change he would interested in. Changelogs are only available in /usr/share/doc AFTER the package is installed. Although, I suppose he could manually download the .deb, unarchive it using ar, tar, and gz, and then see if it would have a changelog in /usr/share/doc that way.
I have noticed something similar as the above poster; it might have the same cause. I will sometimes browse packages.debian.org/sid/package-name, and then click on changelog, and get a 404. I don't know why it happens.
Write your own Choose Your Own Adventure. http://www.freegameengines.org/gamebook-engine/
What I would like to have is a 4.1 release
Well, don't project what you want unto the rest of the world.
Debian stable is a server distro. Every time there is an upgrade, a full regression test must be done to the server. This is expensive and time-consuming. The whole idea of Debian stable is that it is stable and doesn't change often. No one running stable wants the latest and greatest. We want stability and security fixes. That's it.
Clearly you already know about the testing and unstable releases, but did you know about backports and volitile? Volitile is great for things like anti-virus and anti-spam software that you really do want and need upgrades. Backports is a little different--it's basically upgrades for popular packages in stable, and you can pick and choose which ones you want.
Stable means stable, and backports and volitile are great tools to help you. If you want the latest and greatest, that's what the testing release is for.
They don't grade fathers, but if your daughter's a stripper, you fucked up. --Chris Rock
Debian has no release date. It never had, and doesn't seem to have any plans on adopting release dates. Thus, Debian can't be "late", since being late implies on missing a release date, and Debian doesn't have that. Or, maybe I didn't repeat that enough, so let me tell you: Debian never made a compromisse on releasing any version on any exact day.
What Debian does have is a list of bugs. Everytime testing is frozen, it is created a list with the showstopper bugs, and release happens when that list becomes empty. The list can increase if more bugs are found, or decrease if bugs are solved or some functionality removed.
Debian also do have people betting when it'll be out. Those people give specific (or sometimes not very specific) dates, but that isn't a release date for the team, just a guesstimate.
Rethinking email
"Not Lenny!!!!"
Possibly, but I truly don't think Microsoft could ever do right around here. Short of releasing the OS under either the BSD license or the GPL, they will forever have a reputation as software bloaters, monopolists, and DRM-supporters. And such a reputation is not undeserved.
The truth is, I'm not sure they could ever make a stable release of Windows. Vista was horribly delayed, horribly buggy on release, and had dropped a fair number of planned features in order to prevent further delays. If they'd planned to quash most of the bugs before release, I wonder how long it would have taken to get it all done?
Debian has the benefit of a good reputation and of having free software. People aren't scared to run pre-release versions of Debian in production, and it's relatively simple to fix many bugs yourself while waiting for something official from Debian. This means that Debian gets more testers doing real work with their release candidates.
Compare this to Microsoft, who also publish beta and release candidates for free (though free-as-in-beer.) How many people ran Vista full-time before it was released? Heck, Microsoft can barely get people to run it full-time now that it's been out for a while!
I still use Debian Sarge on my current server.
Bad idea. Support for Sarge ended in April, so you haven't been getting any security updates since then, and there are some known weaknesses.
You should upgrade to Etch, ASAP.
Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
Red Hat marketing may not acknowledge point releases, but they do indeed exist. And CentOS tracks 'em. That's why I know. (Too cheap for RHEL, too lazy for Fedora. I use Kubuntu for desktops, but the server has always been in the Red Hat lineage.)
Welcome to the Panopticon. Used to be a prison, now it's your home.
The problem is the kernel team aren't cooperating :(. They won't keep the -486 kernel slim enough and they won't sanction the creation of a seperate kernel flavor just for the floppy installer to use it.
With etch the kernel had grown to the point that they had to kick everything that wasn't absoloutly essential (including USB floppy support) from the boot floppy.
With lenny a couple of bad things happened. Firstly the UPX recompressor stopped working for current kernels. And then just as there was talk of fixing that the lenny kernel grew to the point that it just wasn't feasible to put it on a floppy at all.
note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
I'm not supposed to get release-critical bugs in it!
>fresh installation
Why are you doing this? Just upgrade in place, like everyone else, instead of reinstalling.
Climate Progress - Hell and High Water