On Fri, 2012-02-03 at 15:25 -0600, Dennis Gilmore wrote: > > Both of these seem like compose issues. A newer firefox is in the > > repos and was in the repos before the compose was done, I know > > because I built it. And ksysguard / ksysguard-libs come from the > > same .src.rpm, so it's some kind of compose problem that one got on > > without the other. The build in question is an oddly old one: the > > current Rawhide build should be kdebase-workspace-4.7.97-1.fc17 and > > even the current F16 build is much newer. That looks like the build > > F16 had at release time. > looking at the rawhide reports the fixed firefox landed today, not > yesterday. we composed to early for it. You may be looking at 10.0-2, not 10.0-1. 10.0-1 would have been fine, and I built that yesterday. It may not have *landed* until today, but I thought you said before that as long as builds had the appropriate koji tag they'd wind up in the compose? > I hadnt cleaned out the bleed repo from f16 that is likely where the > old kde bits came from. i have now cleaned them out. so next compose > should be ok. OK, cool. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
