Linked by weildish on Fri 13th Feb 2009 04:35 UTC
What a lovely holiday to release the latest and greatest creation brought to us by yours truly, Debian. February 14th marks Debian GNU/Linux 5.0's supposed release into the wilds of the world, nearly two years after 'etch,' lenny's predecessor. The date is set nearly in stone unless something very serious goes wrong in the final days of development or if one of the needed servers for download kicks the bucket at the wrong moment. Read on for the scoop on the most prominent of features.
Thread beginning with comment 348652
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
RE: 86 release critical bugs?
by da_Chicken on Fri 13th Feb 2009 13:21
in reply to "86 release critical bugs?"
Member since:2006-01-01
What are they doing about these 86 bugs? Ignore them? Throw the packages away?
Some will be ignored (and fixed in the Lenny r1 release), some will be thrown away. See the latest release update for more details:
http://lists.debian.org/debian-devel-announce/2009/02/msg00000.html
BTW: I've had big problems with kernel 2.6.26 - 2.6.24 is ok for me. But 2.6.26 did (does?) not work for me. I think it has something to do with the USB stack. Anyone having a similar problem?
Works fine here. You can always get a newer kernel from kernel.org. Or you can start tracking Squeeze or Sid and wait for an updated Debian-packaged kernel. Or you can try the experimental Debian kernel builds:
http://forums.debian.net/viewtopic.php?t=12430
RE: 86 release critical bugs?
by Peter Besenbruch on Sun 15th Feb 2009 01:16
in reply to "86 release critical bugs?"
Member since:2006-03-13
BTW: I've had big problems with kernel 2.6.26 - 2.6.24 is ok for me. But 2.6.26 did (does?) not work for me. I think it has something to do with the USB stack. Anyone having a similar problem?
I had a lot of trouble with the 2.6.26 kernel at first. Issues with the EEEPC were legion. The most memorable bug was the semi-automatic shutdown, usually just as X was starting, due to a bogus ACPI "event." It only happened when the battery wasn't fully charged. Eventually things settled down.
The reason I don't like the 2.6.24 kernel is that it tends to cause file corruption when coming out of suspend on EEEPCs.
One other correction with the article: KDE is mostly 3.5.10, with some programs still at the earlier version (probably because the programs in question didn't change).
Member since:
2006-06-26
What are they doing about these 86 bugs? Ignore them? Throw the packages away?
BTW: I've had big problems with kernel 2.6.26 - 2.6.24 is ok for me. But 2.6.26 did (does?) not work for me. I think it has something to do with the USB stack. Anyone having a similar problem?