repository breakage

[seth vidal]

> > That's what I consider a bug in yum: Why can't yum simply ignore such
> > broken deps and just warn about them instead of erroring out?
> 
> Seconded, no need to rub it in end users faces.


So if yum updates the other packages and completes its operation, but
doesn't error out, how does the average user know that anything went
wrong?

And if they don't know that something went wrong, then how will they
know if they missed an update?

The reality is that most users see if the operation succeeded or failed.
If it succeeded (no matter the messages it spewed out) they will assume
all is well and move on. If we do that every time then a user could miss
lots of valuable updates and never know. It's only the more advanced
users such as yourself who looks for the nuanced warning messages. Not
to mention, that if the user has enabled a nightly cron update that most
users never see the messages b/c they sit in /var/mail/root w/o ever
being read on many, many workstations and laptops.

At least with a distinct "this has failed, you cannot complete the
operation" the user is told what to look for and that it has failed.

Partial success == complete success to most users.

I'm speaking from years and years of interacting with extremely average
end users using linux systems.

-sv