Differences between revisions 31 and 33 (spanning 2 versions)
Revision 31 as of 2009-03-16 03:36:24
Size: 3554
Editor: anonymous
Comment: converted to 1.6 markup
Revision 33 as of 2009-11-21 21:14:48
Size: 3284
Editor: ?Guillaume Tanguy
Comment: Correction: Squeeze is the current testing distribution
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
##This page is also available in: [:XXXXX:Español] - [:XXXXXX:Dansk] - [:XXXXXX:Français].
Line 7: Line 6:
||<tablewidth="100%" tablestyle=""width="32px" style="border-color: rgb(255, 158, 194);"> {{attachment:Portal/IDB/official-doc.png}} ||<bgcolor="#ffe4f1" style="border-color: rgb(255, 158, 194);">http://www.debian.org/devel/testing - Official page about Debian Testing. ||
{{{#!wiki debian
http://www.debian.org/devel/testing - Official page about Debian Testing.
Line 37: Line 37:
 * [[DebianLenny|Debian Squeeze]] - Squeeze is the current testing distribution.  * [[DebianSqueeze|Debian Squeeze]] - Squeeze is the current testing distribution.

DebianReleases > DebianTesting

  • Debian testing is the current development cycle of Debian. It's named after the next stable release squeeze (as of 2009-02-15)

http://www.debian.org/devel/testing - Official page about Debian Testing.

What is in Testing

A package is installed into the testing dist from DebianUnstable automatically when a list of requirements is fulfilled:

  • The package is at least 10 days old.
  • The package has been built for all the architectures which the present version in testing was built for.
  • Installing the package into testing will not make the distribution more uninstallable.
  • The package does not introduce new release critical bugs.

These requirements should assure that testing is in a pretty workable state but still developing. Especially when packages get restructured, packages that are not quite releasable get into testing, so not all the fun of using a developmental version is removed.



If you use testing currently (pre-lenny), you should change your /etc/apt/sources.list to track lenny, for security reasons. read announcement

An example of testing's unstableness is the upgrade from perl-5.6.0 to perl-5.6.1 which made perl unable to find its modules if they were from a package built with perl-5.6.0. Setting the environment variable PERL5LIB to /usr/lib/perl/5.6.0 solved the problem.

Testing changes more often than stable , but not as crazily as unstable. See also DebianStability.

Testing has the worst security update speed compared to stable and unstable. Don't prefer testing if security is a concern. (is this still valid after 2005-06-06?)

If you were tracking testing but really meant to be tracking lenny, update your /etc/apt/sources.list replacing 'testing' with 'lenny'. The 'lenny' alias would have tracked 'lenny' through it's transition into 'stable'.

You can see what distribution an alias is tracking by looking at the Release file; e.g.:

If you wonder why a package (or a particular version thereof) is not yet in testing, see http://bjorn.haxx.se/debian.

Testing to Stable

How does ''Testing'' becomes the new ''Stable'' release ?

see DebianReleaseFAQ.

See also