On Mon, Feb 15, 2010 at 12:19:20AM +0200, Ville Skytt? wrote: > https://bugzilla.redhat.com/show_bug.cgi?id=562316 > > Why did this bug end up in the FTBFS list? I don't think rpmdevtools has > actually failed to build from source according to the logs available right > now, this bug has nothing directly to do with FTBFS (or at least nothing that > a script could possibly determine fixed/unfixed), and there have been no > rpmdevtools releases yet which fix that actual bug, but it was closed by FTBFS > nevertheless. What's up? Whoops... My ftbfs-closer script took the list of bugs that my ftbfs build scripts believed could be marked "CLOSED RAWHIDE", and did so. That list is at the top of each new run's status report that I emailed out. It's generated by looking at the list of bugs that are open that block (recursively) the top-level FTBFS script, the package that bug corresponds to, and sees if that package builds now. In this case, there was a bug on the FTBFS list, recursively through this chain: Bug 562316 - [perl spec] PERL_INSTALL_ROOT breaks installs with latest EU::MM (edit) Bug 557015 - ExtUtils::MakeMaker 6.51_01+ causing build failures w/Module::Install::Share and others Bug 555496 - FTBFS perl-DBI-Dumper-2.01-8.fc12 F13FTBFS I'll have to make the closer script smarter, to avoid this kind of incorrect closure. Thanks for bringing it to my attention. -Matt -- Matt Domsch Technology Strategist, Dell Office of the CTO linux.dell.com & www.dell.com/linux -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
