On Thu, 02 Sep 2010 13:48:07 -0700, Adam wrote: > On Fri, 2010-09-03 at 01:47 +0530, Rahul Sundaram wrote: > > Hi > > > > https://admin.fedoraproject.org/updates/gummi-0.4.8-2.fc13 update has > > been pushed to stable despite known brokenness (it doesn't start at > > all). See last comment > > > > Upstream bug report by the Fedora package maintainer at > > > > http://dev.midnightcoding.org/redmine/issues/97 > > > > Red Hat bugzilla report at > > > > https://bugzilla.redhat.com/show_bug.cgi?id=629707 > > > > Why has this happened and how can we avoid it in the future? > > > > Conversation comes from http://identi.ca/conversation/48201120 > > It looks like no-one tested it. > > If the bug is in fact as described, one obvious way to improve this > would be for the maintainer to at least launch it before submitting it > as an update :) > > (as the bug reporter notes, our maintainer reported this bug upstream so > he appears to be aware of it, yet he pushed the update anyway, which > just seems bizarre). The upstream ticket about the problem is more than two months old. The entire update request should not have been submitted if it doesn't fix the issue. Once it had entered the updates system, nothing mentioned the breakage in the bodhi ticket. The nag-mail (and comment) after 7 days then maybe encouraged the maintainer to mark the update stable. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
