| Dirk Hartmann 2007-09-07, 7:15 pm |
| Darren Salt wrote:
> I demand that Dirk Hartmann may or may not have written...
>
> [snip]
>
> oldstable == previous release (currently sarge)
> stable == current release (currently etch)
> testing == next release (currently lenny)
> unstable == always unstable (always sid)
>
> Packages are uploaded to unstable and, after a while, appear in testing,
> replacing older versions (subject to dependencies and security bugs).
> Security updates are done for oldstable (for a while), stable and testing.
>
This answers my question. The difference between stable/testing/unstable
should be clear for any Debian user (mixing it causes trouble e.g. when
forcing apt-get -f). In my opinion Debian is build for easy administration
of the distribution.
Background: To have a clean Debian I use pinning (generally i use apt-get
-ut stable to install a new program). My sources list includes only sarge
repositories. And my /etc/apt/preferences is accommodated as follows
Package: *
Pin: release a=stable
Pin-Priority: 500
Package: *
Pin: release a=testing
Pin-Priority: 400
Package: *
Pin: release a=unstable
Pin-Priority: 50
That's why I insisted on the definition. And old stable (sarge) vs stable
(etch) sounds reasonable. Also that one has to keep in mind in the moment
that the latest testing version ist sid (and sarge unstable is only for
strange experiments)
Thanks for answering and good night (11.10 pm in Germany)
--
Dirk Hartmann
Remove _nospam from my mail address because of spam protection
|