(2008-10-28) F10 build 将成为候选更新

为了更好地准备 F10 软件包更新，从今天起所有 F10 build 将标记为 dist-f10-updates-candidate，成为候选更新。这个设定是在软件包目录的 “common” 子目录做的，所以请确保你用了最新的 common 目录。

dist-f10-updates-candidate 的 buildroot 是以 dist-f10 创建的，dist-f10-updates-candidate 的结果不会自动进入 buildroot。如果你需要编译相互依赖的包，必须申请修改 buildroot。

所有打破冻结的软件包和包含在最终发布中的包都包含在 buildroot 中。

dist-f10 标签已被锁定，新的 build 不会被自动标记。如果你遇到由于锁定的标签引起的 build 失败，请联系 releng 或自己修改标签：
# koji tag-pkg dist-f10-updates-candidate

原文见 F10 builds targetted for dist-f10-updates-candidate

In order to properly prepare F10 updates, all F10 builds are now
targetted at dist-f10-updates-candidate. This is a setting in the
‘common’ directory of your package modules, so you’ll want to make sure
you’re using an up to date common.

The buildroot for dist-f10-updates-candidate is comprised of dist-f10
content, which means builds done in dist-f10-updates-candidate
will /not/ automatically be usable in the buildroot. You’ll need to
request a buildroot override in order to do build sets.

Also, any build that we break the freeze for and tag for Fedora 10
release will also be available in the buildroot.

I have locked the dist-f10 tag so that no more builds can automatically
get tagged. If you have a build that fails due to a locked tag, you can
either ping releng, or manually tag it yourself for
dist-f10-updates-candidate:

# koji tag-pkg dist-f10-updates-candidate
–
Jesse Keating
Fedora — Freedom² is a feature!