Re: Sarge release

[Christopher Smiga]

I saw this on a mirror site earlier today. ----- Note: 3.1r0 CD image problem A bug has been discovered in the 3.1r0 CD/DVD images: new installs from these images will have a commented-out entry in /etc/apt/sources.list for "http://security.debian.org/ testing/updates" rather than an active entry for "http://security.debian.org/stable/updates", and thus will not get security updates by default. This was due to incorrect Release files on the images. If you have already installed a system using a 3.1r0 CD/DVD image, you do not need to reinstall. Instead, simply edit /etc/apt/sources.list, look for any lines mentioning security.debian.org, change "testing" to "stable", and remove "# " from the start of the line. If you installed other than from a CD or DVD (for example, netboot, or booting from floppy and installing the base system from the network), you are not affected by this bug. New 3.1r0a images will be available shortly to correct this flaw. We apologise for the inconvenience. ----- Here is the mirror site that stated the information listed above.     http://ftp.ndlug.nd.edu/mirrors/debian-cd/3.1_r0/i386/ Hope this helps some issues. Christopher Smiga Greg Folkert wrote: On Mon, 2005-06-06 at 20:27 -0600, Paul E Condon wrote: I took the occasion of this release to review my sources.list and preferences. In the process I did some experiments and found a puzzle that I hope someone will explain. With sarge in my sources.list I have nothing to download because I have been tracking sarge for almost a year. But I set sources.list to track testing, I suddenly have 246 packages to download. I had thought sarge and testing should be almost identical on release day, but clearly not. What happening? Are these just all the packages that were waiting to move to sarge but were not allowed to move because of a pre-release freeze? Because Testing is now "Etch". Or did you not realize that Etch was already along?