On Mon, 2010-12-06 at 23:01 -0600, Matt Domsch wrote: > I would like to propose blocking packages at the F15 alpha compose > point if they have not resolved their FTBFS from F14 or earlier. You better not. > The > lists may be broken down by when they last did build. With 3 > exceptions, these 110 bugs are all still in NEW state as well, so they > haven't had much maintainer love in quite some time (6-18 months). All the Fedora bugzilla bugs assigned to you, ever: http://bit.ly/dTndTs A whole 73. Fedora Bugzilla bugs in NEW or ASSIGNED assigned to me: http://bit.ly/gBtVRP 810 bugs. When you deal with as many bugs as I (or some other people) do can you take executive decisions on blocking packages in newer revisions. I bet most of those packages are still functional, and fail to build due to some minor changes in the build system, or breakage in dependency libraries. <snip> > ModemManager-0.4-4.git20100720.fc14 [u'631152 NEW'] (build/make) dcbw > NetworkManager-openvpn-0.8.1-1.fc14 [u'631111 NEW'] (build/make) dcbw,choeger,huzaifas,steve > NetworkManager-vpnc-0.8.1-1.fc14 [u'631194 NEW'] (build/make) dcbw And I'm guessing this list didn't get read by humans either. Feel free to insert here complaints about how the Red Hat bugzilla is slow, bad at reporting, and that abrt reports with missing attachments, poor backtraces and no support for tools like GNOME Bugzilla's simple-dup-finedr aren't helping us keep the bug count down. And I'll go back to fixing actual bugs encountered by people instead of random bot-driven bugs. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
