Linked by Eugenia Loli on Wed 8th Jun 2005 08:43 UTC, submitted by george
Debian and its clones A configuration mistake in the new Debian Linux distribution has forced a fix less than 24 hours after the software was released. "New installs [of Debian 3.1 from CD and DVD] will not get security updates by default," said Debian developer Colin Watson in an e-mail warning. Installations from floppy disks or network servers were not affected.
Permalink for comment
To read all comments associated with this story, please click here.
Debian should have caught this...
by David Pastern on Wed 8th Jun 2005 13:26 UTC

Well Libranet 3 doesn't have any issues here ;-) Firstly, you really shouldn't have 'stable' in your /etc/apt/sources.list, but woody. Same with testing. It should have been entered as sarge. Reasoning? When you get a major new release like this, sarge becomes stable. Not testing. What was the Sid packages becomes testing packages, namely Etch. Sid always stays Sid, and unstable. So - by using testing originally, you're updates are going to come from Etch 'testing' and not the Sarge 'stable' that they really should be tracking.

Libranet 3 has the entries in /etc/apt/sources.list correctly named, with security entries as well. And not hashed out.

Debian needs to pay more attention to silly little things like this, although truth be told, it's the sort of thing that's easily missed. The really sad and *bad* thing is that Debian doesn't appear to have anything about this issue on it's main page, or the release page for 3.1. That's disgraceful.