On Wed, 15 Feb 2012 19:45:11 -0500 Tom Horsley <horsley1953@xxxxxxxxx> wrote: > Huh? None of that junk is in updates today, that's why people > find it broken all the time. The test system using the staging > repo can either run "yum update" with no errors, or it can't. > If it gets no errors, the staging repo becomes the updates > repo. If it does get errors, the updates repo is left alone > until the staging repo gets fixed and everyone who pushed > an update since the last time updates was working gets mail > with the yum update transcript. It sounds simple enough... but: Whats on the test system? Everything? It can't have all packages installed due to some conflicting (deliberately, or due to bugs). Just a 'desktop' set? which one? > Yes, that means nothing goes in updates if even one thing > is broken in the staging repo. But that is NOT a problem. > Virtually everyone trying to run "yum update" with the current > process is getting errors and giving up till things work > anyway. yum --skip-broken and wait for the next push to correct things? It's anoying when things like this happen, but it turns out to not be at all simple to solve. In this case, the maintainer should really have seen the negative feedback and stopped pushing the package, or just added them all to the same update. :( kevin
Attachment:
signature.asc
Description: PGP signature
-- 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
