When running dnf update --best (or set best=true in dnf.conf) I get the following on a fully up2date F-21: [hans@shalem ~]$ sudo dnf update --best -v cachedir: /var/cache/dnf/x86_64/21 DNF version: 0.5.4 repo: using cache for: updates-testing repo: using cache for: fedora not found deltainfo for: Fedora 21 - x86_64 repo: using cache for: whot-libinput-userstudy not found deltainfo for: Copr repo for libinput-userstudy owned by whot repo: using cache for: rpmfusion-free-rawhide not found deltainfo for: RPM Fusion for Fedora Rawhide - Free repo: using cache for: adobe-linux-x86_64 not found deltainfo for: Adobe Systems Incorporated repo: using cache for: adobe-linux-i386 not found deltainfo for: Adobe Systems Incorporated repo: using cache for: rpmfusion-nonfree-rawhide not found deltainfo for: RPM Fusion for Fedora Rawhide - Nonfree repo: using cache for: updates --> Starting dependency resolution --> Finished dependency resolution Error: bad problem rule type. bad problem rule type. bad problem rule type. bad problem rule type Let me know what I can do to collect more debug-info for you.
Hi, thanks for the report. I can't see any error reproducing in f21 docker image. The message is unknown error from libsolv. Can you attach debugdata (http://dnf.baseurl.org/2013/11/25/reporting-depsolving-bugs/), please?
Created attachment 919805 [details] dnf update --debugsolver --best debugdata output
The bad error message is already fixed in current libsolv (the one that includes the "yum obsoletes" code). The error itself comes from conflicting jobs: the "update --best" conflicts with the locks for the openssl* packages. If you switch over to the pool->considered mechanism for package excludes, the error will also be gone.
(In reply to Michael Schröder from comment #3) > The bad error message is already fixed in current libsolv (the one that > includes the "yum obsoletes" code). > > The error itself comes from conflicting jobs: the "update --best" conflicts > with the locks for the openssl* packages. Ah yes, that makes sense. > If you switch over to the pool->considered > mechanism for package excludes, the error will also be gone. I guess that is something which needs to be changed in the dnf code, or is it a config / repo setting ?
Yes, it'll be a change in dnf & hawkey. See bug #1099342.
Thanks for the libsolv fix and info, Michael. *** This bug has been marked as a duplicate of bug 1099342 ***