On Wed, 15 Feb 2012 13:02:22 -0500, TH (Tom) wrote: > > Secondly, you can only catch the broken dep prior to moving _individual > > packages_ from updates-testing to updates. Moving alsa-lib plus alsa-utils > > at once would have been fine. > > So don't move them to updates, move them to pushed-but-not-released-updates, > only the test machine has repos pointing to pushed-but-not-released-updates, > only if the yum update works on the test machine are pushed-but-not-released-updates, > actually swapped into the real updates repo. Of course, a temporary staging repo would be needed. Filling it isn't trivial, however, and requires lots of iterations and a bullet-proof "--skip-broken" finder (which, for example, doesn't use compat-arch packages to resolve "broken" dependencies). Also, for any package that enters the skip-broken list, all the corresponding src.rpm's builds must be excluded and another check be done. Possibly it must even be taken into account which src.rpms belong to the same bodhi ticket to withdraw a complete package set (to avoid pushing something where the automatic dependencies aren't strict enough). -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
