Differences between revisions 3 and 4
Revision 3 as of 2016-07-03 09:15:38
Size: 6744
Editor: BoyuanYang
Comment: a little bit more translation
Revision 4 as of 2016-07-05 08:10:22
Size: 6899
Editor: BoyuanYang
Comment: more translations
Deletions are marked like this. Additions are marked like this.
Line 32: Line 32:
The code name for the next stable release, e.g. "<<DebianCodename(testing)>>", will track "<<DebianCodename(testing)>>" through its transition into "stable" and later oldstable, while "testing" will keep rolling on after a new stable release. If you would rather track the [[DebianStretch|stretch]] release as it becomes stable, update your '''/etc/apt/sources.list''' replacing "stable" or "testing" with "<<DebianCodename(testing)>>". 下一个稳定版本的代号,例如 "<<DebianCodename(testing)>>",将会一直保持不变,一直跟随 "<<DebianCodename(testing)>>",无论它接下来是变成 "stable" 稳定版还是再之后变成 "oldstable" 旧稳定版。与其不同的是,"testing" 这个名称在新稳定版本发布后也将一直滚动下去。如果您打算仅跟随 [[DebianStretch|stretch]] 版本,在其发布后自动变成稳定版,请更新您的 '''/etc/apt/sources.list''' 文件,并将 "stable" 或者 "testing" 替换为 "<<DebianCodename(testing)>>"。
Line 34: Line 34:
||<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 [[https://www.debian.org/security/faq#testing|this FAQ-Item]]. || ||<tablewidth="100%" tablestyle=""bgcolor="#ffffff" width="32px" style="border-color: rgb(255, 0, 0); text-align: center;"> <!> ||<style="border-color: rgb(255, 0, 0);"> 如果您选择跟踪 testing(或称 next-stable)的发行代号,您应当总是将对应的 '''{{{deb http://security.debian.org <"testing" or codename>/updates main}}}''' 这一行添加进您的 '''/etc/apt/sources.list'''。请进一步查看 [[https://www.debian.org/security/faq#testing|FAQ 信息]]。 ||

Translation(s): English - Français - Italiano - Svenska - Русский- 简体中文(Chinese)

Debian 发行版 > Debian Testing


  • Debian testing(测试版)是下一个稳定 Debian 发行版的当前开发状态。它同样使用下一个稳定发行版本的代号,即,stretch(在2015-04-25时)。

Debian Testing 如何工作

来自 Debian Unstable(不稳定版)的软件包将自动进入作为下一个稳定版的 testing 发行版,条件是以下列出的要求得到满足:

  • 该软件包在“unstable”中已存在至少2到10天(根据上传的紧急程度决定)。
  • 该软件包已经为 testing 中已有的该软件包所对应的所有架构成功打包。
  • 将其安装至 testing 版本的系统中不会使得发行版变得更加无法安装。
  • 该软件包未引入新的致命发布缺陷(RC bugs)。

如需了解更深入的信息,请见 Debian Testing 官方网页:https://www.debian.org/devel/testing

这些要求应该能够确保在 testing 中将作为 next-stable 一部分的软件包既有合理的新版本又拥有较为正常的工作状态。然而,仍然有些时候,特别是当软件包正在进行重构时,不那么适合于发布的软件包仍然可能进入 next-stable 发行版。因此,你仍然可以体验到使用一个持续演化的开发版本的一些“乐趣”。

如何使用 Debian (next-stable) Testing

要做的第一件事就是对 testing 的当前状态进行评估。可以在 debian-testing 邮件列表存档Status/Testing 维基页面 上看一看最近的话题。除了使用这些特定的资源外,你也可以使用一般的 debian-userdebian-devel 邮件列表、 #debian 或 #debian-next IRC 频道,当然也可以检查一下 debian 缺陷追踪系统。你也可能想再看一看 DebianDesktopHowTo

从头开始安装 testing 的可靠方式是,使用稳定版本的安装器进行一次最小化安装,然后将其从 stable 升级到 testing。

除此之外,你可以使用 debian-installer 的 testing 镜像,但是请注意 testing 安装器与其说是为了安装 testing 而存在,不如说是为了对安装器进行测试。testing 安装器存在的缺陷应作为 debian-installer 伪软件包的缺陷报告提交。

要升级到 testing,如果您已经安装了稳定版本,请编辑您的 /etc/apt/sources.list 并将 apt 行中的 'stable'(或者稳定版本的当前代号)更改为 'testing'(或者下一个稳定版本的当前代号)。也可能需要同时更改文件中的其它部分。您可以考虑使用 synaptics 工具协助完成这个工作。

下一个稳定版本的代号,例如 "trixie",将会一直保持不变,一直跟随 "trixie",无论它接下来是变成 "stable" 稳定版还是再之后变成 "oldstable" 旧稳定版。与其不同的是,"testing" 这个名称在新稳定版本发布后也将一直滚动下去。如果您打算仅跟随 stretch 版本,在其发布后自动变成稳定版,请更新您的 /etc/apt/sources.list 文件,并将 "stable" 或者 "testing" 替换为 "trixie"。

<!>

如果您选择跟踪 testing(或称 next-stable)的发行代号,您应当总是将对应的 deb http://security.debian.org <"testing" or codename>/updates main 这一行添加进您的 /etc/apt/sources.list。请进一步查看 FAQ 信息

After installing or adjusting the software sources, run apt-get update && apt-get upgrade regularly to get new versions and security updates. If you notice that some packages are not upgraded you should also try apt-get dist-upgrade, but beware that this command will also install or remove packages, so do check carefully all proposed actions before proceeding.

testing/sid 用户的最佳实践

请看一下 对 testing/sid 用户的最佳实践的建议,并考虑按照其建议开展工作。

考量

An example of the kinds of temporary breakage 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. However, 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, so expect that new stable versions of the programs you use will be installed as soon as they are ready for next-stable testing, except when testing gets "frozen" to prepare for 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.

Testing 是怎样变成新的 Stable 而发布的呢? :: 请见 DebianReleaseFAQ

参见