Differences between revisions 20 and 21
Revision 20 as of 2007-04-08 13:37:44
Size: 2040
Editor: ?marga
Comment: Etch released! (forgot one mention)
Revision 21 as of 2007-09-15 13:04:22
Size: 2786
Editor: FranklinPiat
Comment: split page in sections. +header +links to related pages.
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
["DebianReleases"] > DebianTesting
Line 4: Line 4:
A package is installed into the testing dist from DebianUnstable automatically when a list of requirements is fulfilled: ##This page is also available in: [:XXXXX:Español] - [:XXXXXX:Dansk] - [:XXXXXX:Français].
----
Debian ''testing'' is the current development cycle of Debian.

''[:DebianLenny:lenny]'' is the ''current'' testing distro.

== What is in Testing ==
A package is installed into the testing dist from [:DebianUnstable:Unstable] automatically when a list of requirements is fulfilled:
Line 7: Line 14:
Line 9: Line 15:
Line 11: Line 16:
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. == Considerations ==
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.
Line 18: Line 23:
It changes more often than DebianStable (DebianEtch), but not as crazily as DebianUnstable (["DebianSid"]). See also DebianStability. Testing changes more often than [:DebianStable:stable] , but not as crazily as [:DebianUnstable:unstable]. See also DebianStability.
Line 22: Line 27:
DebianLenny is the current testing distro. If you were tracking DebianTesting but really meant to be tracking DebianEtch, update your {{{/etc/apt/sources.list}}} replacing 'testing' with 'etch'. The 'etch' alias would have tracked 'etch' through it's transition into 'stable'. You can do the same for DebianLenny. If you were tracking [:DebianTesting:testing] but really meant to be tracking [:DebianEtch:etch], update your {{{/etc/apt/sources.list}}} replacing 'testing' with 'etch'. The 'etch' alias would have tracked 'etch' through it's transition into 'stable'.
Line 24: Line 29:
You can see what distribution an alias is tracking by looking at the Release file; e.g.:{{{
 ftp://ftp.us.debian.org/debian/dists/testing/Release
}}}
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
Line 30: Line 34:
See also: == Testing to Stable ==
 How does ''Testing'' becomes the new ''Stable'' release ? :: see ["DebianReleaseFAQ"].
Line 32: Line 37:
 * ["FromTestingToStable"].
 * AptDirectory
== See also ==
 * 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.
 * ["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.

["DebianReleases"] > DebianTesting


Debian testing is the current development cycle of Debian.

[:DebianLenny:lenny] is the current testing distro.

What is in Testing

A package is installed into the testing dist from [:DebianUnstable:Unstable] 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.

Considerations

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 [:DebianStable:stable] , but not as crazily as [:DebianUnstable: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 [:DebianTesting:testing] but really meant to be tracking [:DebianEtch:etch], update your /etc/apt/sources.list replacing 'testing' with 'etch'. The 'etch' alias would have tracked 'etch' 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