Differences between revisions 38 and 40 (spanning 2 versions)
Revision 38 as of 2011-02-06 09:33:12
Size: 3260
Editor: HenriLeFoll
Comment: change Lenny to Squeeze and Squeeze to Wheezy
Revision 40 as of 2011-05-21 20:56:43
Size: 3310
Editor: ?skizzhg
Comment: fixing header
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
DebianReleases > DebianTesting ~-[[DebianWiki/EditorGuide#translation|Translation(s)]]: English - [[it/DebianTesting|Italiano]]-~
Line 4: Line 4:
~-Translation(s): [[it/DebianTesting|Italiano]]-~ DebianReleases > Debian Testing

Translation(s): English - Italiano

DebianReleases > Debian Testing

  • Debian testing is the current development cycle of Debian. It's named after the next stable release Wheezy (as of 2011-02-06)

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, you should change your /etc/apt/sources.list to track Wheezy, for security reasons.

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.

If you are tracking testing but really mean to be tracking Wheezy, update your /etc/apt/sources.list replacing 'testing' with 'Wheezy'. The 'Wheezy' alias will track 'Wheezy' 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'' become the new ''Stable'' release ?

see DebianReleaseFAQ.

See also