Skip-broken could not solve problems
awilliam at redhat.com
Mon Jan 10 01:28:01 UTC 2011
On Sun, 2011-01-09 at 18:14 -0500, seth vidal wrote:
> On Sun, 2011-01-09 at 21:59 +0000, Adam Williamson wrote:
> > On Sun, 2011-01-09 at 21:03 +0000, Andre Robatino wrote:
> > > When running "yum --skip-broken update" and getting this message (currently in
> > > Rawhide), should it always be considered a bug and reported?
> > Depends what you mean. If you mean 'is it a bug in yum', no. There are
> > some types of dependency issues that can't really sensibly be resolved
> > by ignoring some updates. It's clearly a bug in *something*, though. You
> > should treat each case individually, figure out what the ultimate root
> > of the problem is, and file a bug against the appropriate package.
> well some of them are a bug in yum. :) And, in theory, yes we should be
> able to walk it back.
right, my answer was 'no it's not *always* a bug in yum', not 'no it's
never a bug in yum'. sorry if that wasn't clear =)
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
More information about the test