On Wed, Sep 07, 2005 at 11:03:01AM -0400, Jeremy Katz wrote: > On Wed, 2005-09-07 at 08:52 -0400, Daniel Veillard wrote: > > In that case it's not a transcient failure, I think last time I tried to > > use anaconda of rawhide back in July I had the exact same error. > > The error you're seeing is a "tree composed badly and broke". That's > unfortunately one that's dependent on the phase of the moon causing the > build machines to be uncooperative. Hard to anticipate :) So I was just unlucky on that too and the fact I get the same error does not mean it was the state of the package in the meantime ? If yes sorry about that I overgeneralized again. Is detecting "tree composed badly and broke" possible ? And avoid pushing those ? Daniel -- Daniel Veillard | Red Hat Desktop team http://redhat.com/ veillard@xxxxxxxxxx | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-devel-list
