Do you remember when I ranted about lack of communication between provenpackagers and the maintainers of the packages they touch [1]? Here is another case of lack of communication between people touching the same package. On Aug 8, Zeeshan Ali built gnome-boxes-3.8.4-1.fc19 and submitted update FEDORA-2013-14567. On Aug 9, Christophe Fergeau built gnome-boxes-3.8.4-2.fc19. Instead of editing the existing update, Christophe chose to create a competing update, FEDORA-2013-14530. On Aug 13, update FEDORA-2013-14530 acquired enough karma to be autopushed to stable. It went stable on Aug 15. The first update, FEDORA-2013-14567, stayed in limbo for awhile until positive karma was given to it on Sep 28 and 29, causing it to reach its karma threshold on Sep 29, and be autopushed to stable. On Sep 30, it went stable, wiping out the -2 build. Is there any way we can change the update system to detect competing updates like this? The update system should have refused to create the second update, and required Christophe to either (1) edit the existing update, or (2) get the existing update canceled first, then submit the new one. Footnotes: [1] https://lists.fedoraproject.org/pipermail/devel/2013-May/182432.html -- Jerry James http://www.jamezone.org/ -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
