Hi.
On Mon, 11 May 2009 13:12:59 +0200, Michael Schwendt wrote
The basic idea of buildroot protection is good. What doesn't
work
well so far, however, is how the buildroot overrides are executed. A
packager submits a releng ticket, the request is accepted, the tag
gets created, the incompatible package enters the buildroots, no
announcement is sent, danger lies ahead. As pointed out elsewhere in
this thread, this has hit qtorrent (rb_libtorrent, springlobby) for
Fedora 11. The process would be much better if (a) all buildroot
overrides would be announced in a prominent place and (b) marking
incompatible packages "stable" in order to skip the buildroot
override procedure would be forbidden.
Could koji provide 'private' buildroots, which are created for a limited
time and in which the override packages are imported? Like this:
a) Packager builds new package of libfoo
b) Packager request buildroot override for libfoo
c) a private koji tag is created which includes the new libfoo and which
stays valid for a specific time (say, a couple of days, or until the
packager dismisses it)
d) Packager builds appfoo in the private tag
Noone except the packager would be affected by the override, until
libfoo hits the proper repos.