Alsa-utils update broken

[Kevin Fenzi]

On Wed, 15 Feb 2012 19:45:11 -0500
Tom Horsley <horsley1953 at gmail.com> 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/users/attachments/20120215/7604a289/attachment-0001.sig>