On Fri, Aug 21, 2009 at 08:13:34PM +0200, Kevin Kofler wrote: >drago01 wrote: >> 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. I use bodhi every day. I have yet to find all it's limitations. There are known limitations that aren't even documented. I think it's a bit far reaching to say that maintainers should just know, when there is no good way for them to know without either reading the code or excessive use. >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). That's decent advice, but it will not catch quite a number of the problems that we see come up. josh -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
