Linked by Thom Holwerda on Tue 10th Apr 2007 18:52 UTC, submitted by luna6
Permalink for comment 229291
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.





Member since:
2006-01-13
Let me tell you about MY experience with Etch. I have sarge installed on a dedicated server at a data center. Last night we are doing the usual apt-get to download security updates for sarge, when, to our dismay sarge starts automatically updating to Etch! Now we haven't tested Etch at all, so rolling out these changes on a production system is UNACCEPTABLE. So we try to cancel the changes before things go straight to hell, which leaves the dedicated server in a foobar state. After looking around at what went wrong we discovered the default in sources.list was 'stable' and not 'sarge'. Pretty lame if you ask me. When they changed 'stable' from 'sarge' to 'etch' it tried to auto upgrade the distro. Our debian system was up 500+ days prior to this incident.
I'm not impressed, not at all.