Re: rawhide report: 20070919 changes

[Tim Lauridsen <tla@xxxxxxxxx>]

Horst H. von Brand wrote:

Jim Cornette <fct-cornette@xxxxxxxxxxxxxx> wrote:
  

David Boles wrote:
    

Not sure, exactly, what you are saying here. Remove is not normally
necessary. Just exclude the packages that are causing the problems with
some of the packages in the update.
      

[...]

  

So what would the right command to get the packages installed without
conflict be? Would it be something like below? Or would simply
determining your need for the conflicting package and removing it be a
better alternative?

yum -y --skip-broken --exclude=digikamhttp://
    

I'd vote for axing yum-skip-broken. It has *never* worked.
  

The current 1.1.7 should work, but it cant solve all issues (The have some issues because the yum depsolver has been a moving target)
Here is a little explanation of how it works.
for each package in the yum transaction
    make a new yum transaction with only this package
    run the yum depsolver on the transaction
    if it fails then put it on the bad list
remove the packages on the bad list from the original transaction and run the normal yum depsolve.

so it will only find the problems found in the depsolve process, not the ones in the test transaction.
There have been some problems lately, because there have been some issue with clearing the depsolve between check of each package, but as far as i know it should the current 1.1.7 release be working with yum 3.2.5.

Tim

-- 
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe: 
https://www.redhat.com/mailman/listinfo/fedora-test-list