On 20120129_090739, Christofer C. Bell wrote: > On Sun, Jan 29, 2012 at 8:27 AM, Colin <colintemp...@gmail.com> wrote: > > > On Sun, Jan 29, 2012 at 11:28 AM, Sven Joachim <svenj...@gmx.de> wrote: > > > On 2012-01-29 11:51 +0100, Colin wrote: > > > This depends on what you intend to do when wheezy becomes stable. Do > > > you want to continue to use testing forever, or do you want to have a > > > system that remains basically unchanged for a long time? If the latter, > > > use "wheezy" instead of "testing". > > > > > > Sven > > > > I see. > > I want to stay with testing in the long term but would prefer not to > > await for security updates. > > Right now security updates are treated as a normal update, that is a > > normal package transition from unstable to testing, correct? > > > > Colin, > > Perhaps this will explain it better. This is taken from ftp.us.debian.org: > > lrwxrwxrwx 1 21285 21285 6 Feb 5 2011 testing -> wheezy > lrwxrwxrwx 1 21285 21285 23 Feb 5 2011 > testing-proposed-updates -> wheezy-proposed-updates > drwxr-sr-x 5 21285 21285 28 Jan 29 2012 wheezy > drwxr-sr-x 5 21285 21285 21 Jan 29 2012 > wheezy-proposed-updates >
I am convinced. I should read with better comprehension. Sorry. > There is no difference, at all, between Wheezy and Testing -- They are the > same physical thing on the Debian repository server's hard disk. Testing > is nothing more than a symlink to Wheezy. When updates go into Testing, > they're actually being put into a directory named Wheezy. > > To answer your other question, security updates for Testing move through > from Unstable like any other update except for being fast tracked: > > http://www.debian.org/security/faq#testing > > Does that help at all? :-) > > -- > Chris -- Paul E Condon pecon...@mesanetworks.net -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120129193850.ge5...@big.lan.gnu