>>> Sorry but the fail here is 100% on bodhi's side , why does a single >>> package obsolete a complete group update? >>> That is just broken, and this example clearly showed it. >> >> It's broken (we've had some fun with that with the KDE grouped updates too, >> we learned to be careful about what we push when), but a maintainer should >> know how to use our tools, which includes being aware of their limitations. >> Double-checking things both before and after filing an update (e.g. checking >> https://admin.fedoraproject.org/updates/thepackageyoureabouttopushanupdatefor >> before filing the new update request) definitely can't hurt (I always do >> that), and it will help avoiding issues you don't even know about, or at >> least catching them earlier than 2 months after the fact (as happened here). > > Sure if you know about a bug/limitation you can try to avoid it, but > as Josh said you can't expect that every maintainer knows about all > (undocumented) bugs/limitations. Agreed, I ran into the issue a while ago. Not such a major issues as it would be for something like a KDE or mono update but annoying none the less. Peter -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
