Home > Fedora > yum –skip-broken

yum –skip-broken

I have be working on beating the skip broken functionallty in yum in better shape. The was a lot cases were it has to give up. One of the big problems debugging the code is that,  repo inconsistencies where skip broken is useful, don’t last long and can be hard to reproduce and retest.  So i had been working to make some unit tests in yum,  to reproduce the found issues and make the debug output from skip broken a lot better, so it is easier to see what goes wrong.

The current yum in rawhide (3.2.20) is in very good shape and the upstream 3_2_x branch is even better.

If you run into some situation where ‘–skip-broken’ bails out, then please checkout


Categories: Fedora Tags: , ,
  1. Nicolas Mailhot
    November 15, 2008 at 15:23

    Well, given all the manual -xs I had to use recently on rawhide skip-broken is not there yet.

    I’ll believe it’s finaly fixed the day it can handle rawhide/koji just after it’s unfrozen (when evo is rebuilt but not totem, etc)

  2. November 15, 2008 at 16:07


    Next time, please test with upstream yum and make bugzilla reports.
    it is the only way for me to see the corner cases.

    The lastest fixes to multiarch and multiple obsoletes is not in rawhide yet, but only upstream.

  3. Thorsten Leemhuis
    November 15, 2008 at 18:10

    I suppose you have read
    and the thread following it?

    Ohh, and one other thing that would be “nice to have” in yum and/or skip broken: if it fails use the package signing keys to detect where the packages that are involved actually come from 8e.g. from which repo)

  4. Nicolas Mailhot
    November 15, 2008 at 22:02

    @timlau unfortunately I didn’t read this message 4 days ago, and the repo is already much less broken than it was then.

  5. November 16, 2008 at 07:16


    It think that the current upstream skip-broken, cant bail you out of the problems, described in the thread, until the repos get in sync.

    But the try if we can find a better package in another mirror, don’t seams to be a good solution to me and use the gpg key to get the repo where the package was coming from is not my cup of tea.
    We are working on a way to store extra package information, such as the source repo for installed packages, in a future version of yum, but it need to be supported by rpm too. to make it most effective. That will make this kind of “crack” more easy to do.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: