Ask Your Question

[dnf | yum] update, different results

asked 2015-02-19 02:11:34 -0500

lucabotti gravatar image

Hi All,

it's been some days (and today again) that dnf update (which is my first choice) gives me different results from yum update - the former is empty and the latter updates some packages. This morning dnf downloaded "updates" repository metadata and gave me nothing. Yum brings in some updates from fedora official repository. This is the terminal session:

[xxxx@yyy ~]$ sudo dnf update
[sudo] password for xxxx: 
Fedora 21 - x86_64 - Updates                                                                                     1.2 MB/s |  14 MB     00:11    
Dependencies resolved.
Nothing to do.
[xxxx@yyy ~]$ sudo yum update
[sudo] password for xxxx: 
Loaded plugins: langpacks
bumblebee                                                                                                                 | 2.9 kB  00:00:00     
google-chrome                                                                                                             |  951 B  00:00:00     
home_snwh_moka-project                                                                                                    | 1.6 kB  00:00:00     
xxxxx                                                                                                                 | 2.9 kB  00:00:00     
rpmfusion-free-updates                                                                                                    | 2.7 kB  00:00:00     
rpmfusion-nonfree-updates                                                                                                 | 2.7 kB  00:00:00     
updates/21/x86_64/metalink                                                                                                |  26 kB  00:00:00     
updates                                                                                                                   | 4.9 kB  00:00:00     
virtualbox                                                                                                                |  951 B  00:00:00     
updates/21/x86_64/primary_db                                                                                              | 5.2 MB  00:00:04     
(1/3): google-chrome/primary                                                                                              | 1.9 kB  00:00:00     
(2/3): updates/21/x86_64/updateinfo                                                                                       | 617 kB  00:00:00     
(3/3): updates/21/x86_64/pkgtags                                                                                          | 1.4 MB  00:00:01     
google-chrome                                                                                                                                3/3
Resolving Dependencies
--> Running transaction check
---> Package atlas.x86_64 0:3.10.1-16.fc21 will be updated
---> Package atlas.x86_64 0:3.10.1-18.fc21 will be an update
---> Package bind-libs.x86_64 32:9.9.6-6.P1.fc21 will be updated
---> Package bind-libs.x86_64 32:9.9.6-7.P1.fc21 will be an update
---> Package bind-libs-lite.x86_64 32:9.9.6-6.P1.fc21 will be updated
---> Package bind-libs-lite.x86_64 32:9.9.6-7.P1.fc21 will be an update
---> Package bind-license.noarch 32:9.9.6-6.P1.fc21 will be updated
---> Package bind-license.noarch 32:9.9.6-7.P1.fc21 will be an update
---> Package bind-utils.x86_64 32:9.9.6-6.P1.fc21 will be updated
---> Package bind-utils.x86_64 32:9.9.6-7.P1.fc21 will be an update
---> Package libbluray.x86_64 0:0.6.2-1.fc21 will be updated
---> Package libbluray.x86_64 0:0.7.0-1.fc21 will be an update
---> Package perl-version.x86_64 3:0.99.09-1.fc21 will be updated
---> Package perl-version.x86_64 3:0.99.12-1.fc21 will be an update
--> Finished Dependency Resolution

Dependencies Resolved

 Package                              Arch                         Version                                   Repository                     Size
 atlas                                x86_64                       3.10.1-18.fc21                            updates                       5.5 M
 bind-libs                            x86_64                       32:9.9.6-7.P1.fc21                        updates                       1.0 M
 bind-libs-lite                       x86_64                       32:9.9.6-7.P1.fc21                        updates                       733 k
 bind-license                         noarch                       32:9.9.6-7.P1.fc21                        updates                        86 k
 bind-utils                           x86_64                       32:9.9.6-7.P1.fc21                        updates                       376 k
 libbluray                            x86_64                       0.7.0-1.fc21                              updates                       132 k
 perl-version                         x86_64                       3:0.99.12-1.fc21                          updates                        94 k

Transaction Summary
Upgrade  7 Packages

Total download size: 7.9 M
Is this ok [y/d/N]:

Any Idea?

edit retag flag offensive close merge delete




yum clean metadata && dnf clean metadata

yum -y update && dnf -y update
davidva gravatar imagedavidva ( 2015-02-19 09:43:43 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2015-02-19 07:49:22 -0500

mether gravatar image

Yes. They update their cache at different intervals. So this is expected behavior. In both cases, the metadata expiration can be configured to your preference if you wish to do so via yum.conf/dnf.conf.

edit flag offensive delete link more


Is that still the case after a yum / dnf clear all?

lucabotti gravatar imagelucabotti ( 2015-02-21 10:59:11 -0500 )edit

It's your question you could test :) Anyway, in my experience, it can sometimes produce different results. DNF will automatically exclude untenable portions of a package transaction, for example, akin to --skip-broken but in a way that ensures all remaining dependencies are still met. It also might resolve relationships between packages differently; RPMs don't always have explicitly declared requirements on other packages, they require or provide capabilities and dnf could select a different package to provide a given capability.

randomuser gravatar imagerandomuser ( 2015-02-21 14:34:11 -0500 )edit

Question Tools

1 follower


Asked: 2015-02-19 02:11:34 -0500

Seen: 1,626 times

Last updated: Feb 19 '15