Differences between revisions 2 and 45 (spanning 43 versions)
Revision 2 as of 2004-03-24 20:48:20
Size: 1301
Editor: anonymous
Comment:
Revision 45 as of 2012-06-16 13:19:42
Size: 5478
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## Auto-converted by kwiki2moinmoin v2005-10-07
Debian testing is the current development cycle of Debian.
#language en
~-[[DebianWiki/EditorGuide#translation|Translation(s)]]: English - [[fr/DebianTesting|Français]] - [[it/DebianTesting|Italiano]]-~
Line 4: Line 4:
A package is installed into the testing dist from DebianUnstable automatically when a list of requirements is fulfilled: DebianReleases > Debian Testing
----
 Debian ''testing'' is the current development state of the next stable Debian distribution. It is also made available under the code name of the next stable release, i.e. [[DebianWheezy|wheezy]] (as of 2011-02-06)
Line 6: Line 8:
 * The package is at least 10 days old. == How Debian Testing Works ==
Packages from DebianUnstable enter the next-stable testing distribution automatically, when a list of requirements is fulfilled:
Line 8: Line 11:
 * The package has been in 'unstable' at least for 2-10 days (depending on the urgency of the upload).
Line 9: Line 13:
Line 11: Line 14:
Line 14: Line 16:
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. {{{#!wiki debian
For more in depth information see the official Debian Testing web page: http://www.debian.org/devel/testing .
}}}
Line 16: Line 20:
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. These requirements should assure that the next-stable packages in testing are both reasonably current and in a pretty workable state. Still, sometimes, especially when packages are being restructured, packages that are not quite releasable may get into the next-stable distribution. So, there may remain some of the fun of using a constantly evolving development distribution.
Line 18: Line 22:
It is more unstable than DebianStable, but not as crazy as DebianUnstable. == How to use Debian (next-stable) Testing ==
Line 20: Line 24:
DebianSarge is the current testing distro. First thing is to assess the current state of the next-stable testing. Have a look at the recent topics in the [[http://lists.debian.org/debian-testing|debian-testing mailing list archive]] and update the [[Status/Testing| Status/Testing Wiki-Page]]. Besides using these specific resources you can also use the general [[http://lists.debian.org/debian-user|debian-user]] and [[http://lists.debian.org/debian-devel|debian-devel]] mailing lists, IRC-Chats #debian or #debian-devel, and of course the [[http://bugs.debian.org|debian bug tracker]].
Line 22: Line 26:
If you wonder why a package (or a particular version thereof) is not yet in testing, see http://bjorn.haxx.se/debian . For a new installation, the debian-installer team has a recommended [[http://www.debian.org/devel/debian-installer|testing image of the debian-installer]].

To upgrade to next-stable testing, if you already installed the stable release, edit your '''/etc/apt/sources.list''' substituting 'stable' (or the current codename for stable) in the apt lines to 'testing' (or the current code name for the next stable release). You may also do this with synaptic.

The code name for the next stable release, e.g. 'wheezy', will track 'wheezy' through its transition into 'stable' and later old-stable, while 'testing' will keep rolling on after a new stable release. If your rather want to track the [[DebianWheezy|wheezy]] release as it becomes stable, update your '''/etc/apt/sources.list''' replacing 'stable' or 'testing' with 'wheezy'.

||<tablewidth="100%" tablestyle=""bgcolor="#ffffff" width="32px" style="border-color: rgb(255, 0, 0); text-align: center;"> <!> ||<style="border-color: rgb(255, 0, 0);"> If you are tracking testing or the next-stable code name, you should always have a corresponding '''{{{deb http://security.debian.org <"testing" or codename>/updates main}}}''' line in your '''/etc/apt/sources.list''' . See [[http://www.debian.org/security/faq#testing|this FAQ-Item]]. ||

After installing or adjusting the software sources, run '''{{{apt-get update && apt-get dist-upgrade}}}''' regularly to get new versions and security updates.


== Considerations ==

An example for the kinds of temporary brakages that may happen in next-stable testing, was 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. By setting the environment variable PERL5LIB to /usr/lib/perl/5.6.0 manually one could solve the problem even before the fixed package entered testing.

Testing changes more often than [[DebianStable|stable]], but not as crazily as [[DebianUnstable|unstable]], expect that new stable versions of the programms you use will be installed as soon as they are ready for next-stable testing, exept when testing gets "frozen" to prepare a an imminent stable release. See also DebianStability.

Compared to stable and unstable, next-stable testing has the worst security update speed. Don't prefer testing if security is a concern.


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

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



 How does ''Testing'' become the new ''Stable'' release ? :: see [[DebianReleaseFAQ]].


== See also ==

 * [[DebianWheezy|Debian Wheezy]] - Wheezy is the current testing distribution.
 * Testing
  * [[http://www.debian.org/doc/manuals/securing-debian-howto/ch10.en.html#s-security-support-testing|Security support for the testing branch]] (from the "Securing Debian Manual")
  * [[Status/Testing]] - Current status of Testing.
  * [[TestingRemovals]] - how to request the removal of a package from testing
 * DebianReleases - more about the different Debian releases.
  * [[DebianStable|Debian Stable]] - The official Debian release (the one with the fewer bugs, and security issues).
  * [[DebianUnstable|Debian Unstable]] - repository where new & untested packages are introduced.
----

Translation(s): English - Français - Italiano

DebianReleases > Debian Testing


  • Debian testing is the current development state of the next stable Debian distribution. It is also made available under the code name of the next stable release, i.e. wheezy (as of 2011-02-06)

How Debian Testing Works

Packages from DebianUnstable enter the next-stable testing distribution automatically, when a list of requirements is fulfilled:

  • The package has been in 'unstable' at least for 2-10 days (depending on the urgency of the upload).
  • 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.

For more in depth information see the official Debian Testing web page: http://www.debian.org/devel/testing .

These requirements should assure that the next-stable packages in testing are both reasonably current and in a pretty workable state. Still, sometimes, especially when packages are being restructured, packages that are not quite releasable may get into the next-stable distribution. So, there may remain some of the fun of using a constantly evolving development distribution.

How to use Debian (next-stable) Testing

First thing is to assess the current state of the next-stable testing. Have a look at the recent topics in the debian-testing mailing list archive and update the Status/Testing Wiki-Page. Besides using these specific resources you can also use the general debian-user and debian-devel mailing lists, IRC-Chats #debian or #debian-devel, and of course the debian bug tracker.

For a new installation, the debian-installer team has a recommended testing image of the debian-installer.

To upgrade to next-stable testing, if you already installed the stable release, edit your /etc/apt/sources.list substituting 'stable' (or the current codename for stable) in the apt lines to 'testing' (or the current code name for the next stable release). You may also do this with synaptic.

The code name for the next stable release, e.g. 'wheezy', will track 'wheezy' through its transition into 'stable' and later old-stable, while 'testing' will keep rolling on after a new stable release. If your rather want to track the wheezy release as it becomes stable, update your /etc/apt/sources.list replacing 'stable' or 'testing' with 'wheezy'.

<!>

If you are tracking testing or the next-stable code name, you should always have a corresponding deb http://security.debian.org <"testing" or codename>/updates main line in your /etc/apt/sources.list . See this FAQ-Item.

After installing or adjusting the software sources, run apt-get update && apt-get dist-upgrade regularly to get new versions and security updates.

Considerations

An example for the kinds of temporary brakages that may happen in next-stable testing, was 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. By setting the environment variable PERL5LIB to /usr/lib/perl/5.6.0 manually one could solve the problem even before the fixed package entered testing.

Testing changes more often than stable, but not as crazily as unstable, expect that new stable versions of the programms you use will be installed as soon as they are ready for next-stable testing, exept when testing gets "frozen" to prepare a an imminent stable release. See also DebianStability.

Compared to stable and unstable, next-stable testing has the worst security update speed. Don't prefer testing if security is a concern.

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.

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

see DebianReleaseFAQ.

See also