“dnf update” and “yum update” produce different output

Seeing many users confused about the difference in the outputs and transactions of running yum update versus dnf update I feel I should explain that this is the expected result and not a bug. One reason is that DNF does not list update candidates as it explores them. More frequently however the reporter means actual difference in the proposed transaction. This is most often because the metadata the two packagers are working with were taken at a different time (DNF has a notoriously looser schedule on metadata updates to save time and bandwidth), and sometimes also because the depsolvers inside are designed to take a different course of action when encountering specific update scenario.

The bottom line is: unless a real update problem occurs (i.e. DNF refuses to update a package that Yum updates) with the same set of metadata (dnf clean all; yum clean all), this is not an issue.

3 thoughts on ““dnf update” and “yum update” produce different output

  1. Also, yum has the debuginfo updater plugin enabled by default. If you have any debuginfo packages installed, ‘yum update’ will find updates for them and ‘dnf update’ will not, unless you actually enable the debuginfo repositories.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Current day month ye@r *