On Tue, 21 Aug 2007 13:23:29 -0400
"Ray Strode" <halfline@xxxxxxxxx> wrote:
> Why does it do that?
Automated rebuilds are often done with low priority, so that normal
priority builds aren't held up for days on end (it takes a long time to
build 3K packages x 4 arches). If you were to go in after the
automation came along and updated cvs and scheduled the build,
and /you/ again bumped CVS and started a build, your build would
complete before the automated one, then the automated one would
complete and actually be the 'latest' package since the last tagged
package wins. Your change would be lost. To prevent this, you need to
wait until the automated build completes, or you have to get rel-eng to
cancel the build. It adds a lot of confusion as to the state of the
build system.
Couldn't existing builds for a package be canceled when a new one is queued?
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
