On Mon, Mar 11, 2013 at 12:50:53PM -0400, Kamil Paral wrote: > > - bugs that break the rawhide buildroot. In practice these are > > usually > > noticed pretty quickly and the offending build is just untagged > > until > > it can be fixed, but there could be cases where the fix is more > > complex and has a bug associated with it. > > For those of us who are not skilled in building a release, what does this exactly mean? I can imagine bugs that prevent compose (no package repo created), but this one could deserve a closer explanation. Whenever libguestfs FTBFS in Rawhide because the current Rawhide userspace doesn't boot during the tests, I'd attach my bug to this one. Thankfully autotest is making this problem rarer these days. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
