Bug 1179720 - confused about kernel version numbers?
Summary: confused about kernel version numbers?
Keywords:
Status: CLOSED DUPLICATE of bug 1160950
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-07 12:08 UTC by Neal Becker
Modified: 2015-02-09 14:31 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-07 15:27:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Neal Becker 2015-01-07 12:08:41 UTC
Description of problem:

dnf seems confused, yum works correctly:

sudo dnf install rpmbuild/RPMS/x86_64/*
Fedora 21 - x86_64 - Updates                    1.1 MB/s | 8.5 MB     00:07    
Package kernel-3.17.4-301.fc21.x86_64 is already installed, skipping.
Package kernel-core-3.17.4-301.fc21.x86_64 is already installed, skipping.
Package kernel-devel-3.17.7-300.fc21.x86_64 is already installed, skipping.
Package kernel-headers-3.17.7-300.fc21.x86_64 is already installed, skipping.
Package kernel-modules-3.17.4-301.fc21.x86_64 is already installed, skipping.
Package kernel-modules-extra-3.17.4-301.fc21.x86_64 is already installed, skipping.
Package kernel-tools-3.17.7-300.fc21.x86_64 is already installed, skipping.
Package kernel-tools-libs-3.17.7-300.fc21.x86_64 is already installed, skipping.
Package kernel-tools-libs-devel-3.17.7-300.fc21.x86_64 is already installed, skipping.
Package perf-3.17.7-300.fc21.x86_64 is already installed, skipping.
Package python-perf-3.17.7-300.fc21.x86_64 is already installed, skipping.
Error: Nothing to do.
Version-Release number of selected component (if applicable):

ls   rpmbuild/RPMS/x86_64/*
rpmbuild/RPMS/x86_64/kernel-3.17.7-300.local.fc21.x86_64.rpm
rpmbuild/RPMS/x86_64/kernel-core-3.17.7-300.local.fc21.x86_64.rpm
rpmbuild/RPMS/x86_64/kernel-devel-3.17.7-300.local.fc21.x86_64.rpm
rpmbuild/RPMS/x86_64/kernel-headers-3.17.7-300.local.fc21.x86_64.rpm
rpmbuild/RPMS/x86_64/kernel-modules-3.17.7-300.local.fc21.x86_64.rpm
rpmbuild/RPMS/x86_64/kernel-modules-extra-3.17.7-300.local.fc21.x86_64.rpm
rpmbuild/RPMS/x86_64/kernel-tools-3.17.7-300.local.fc21.x86_64.rpm
rpmbuild/RPMS/x86_64/kernel-tools-libs-3.17.7-300.local.fc21.x86_64.rpm
rpmbuild/RPMS/x86_64/kernel-tools-libs-devel-3.17.7-300.local.fc21.x86_64.rpm
rpmbuild/RPMS/x86_64/perf-3.17.7-300.local.fc21.x86_64.rpm
rpmbuild/RPMS/x86_64/python-perf-3.17.7-300.local.fc21.x86_64.rpm

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Jan Zeleny 2015-01-07 13:07:31 UTC
It seems that you already have all those packages installed on your system, could you post the output of dnf list installed kernel* perf python-perf?

Comment 2 Neal Becker 2015-01-07 14:15:59 UTC
No, these packages were not installed.  I built custom kernel with '.local' in name, and attempted to install.  I believe this is a use case the dnf _must_ support.

Again, dnf refused but yum succeeded.

Since yum has now installed them, I can't reproduce the problem.
Here is the dnf list _after_ yum did the update:

dnf list installed kernel* perf python-perf
Installed Packages
kernel.x86_64                            3.17.6-300.fc21                 @System
kernel.x86_64                            3.17.7-300.fc21                 @System
kernel.x86_64                            3.17.7-300.local.fc21           @System
kernel-core.x86_64                       3.17.6-300.fc21                 @System
kernel-core.x86_64                       3.17.7-300.fc21                 @System
kernel-core.x86_64                       3.17.7-300.local.fc21           @System
kernel-devel.x86_64                      3.17.7-300.fc21                 @System
kernel-devel.x86_64                      3.17.7-300.local.fc21           @System
kernel-doc.noarch                        3.17.4-200.fc20                 @System
kernel-headers.x86_64                    3.17.7-300.local.fc21           @System
kernel-modules.x86_64                    3.17.6-300.fc21                 @System
kernel-modules.x86_64                    3.17.7-300.fc21                 @System
kernel-modules.x86_64                    3.17.7-300.local.fc21           @System
kernel-modules-extra.x86_64              3.17.6-300.fc21                 @System
kernel-modules-extra.x86_64              3.17.7-300.fc21                 @System
kernel-modules-extra.x86_64              3.17.7-300.local.fc21           @System
kernel-tools.x86_64                      3.17.7-300.local.fc21           @System
kernel-tools-libs.x86_64                 3.17.7-300.local.fc21           @System
kernel-tools-libs-devel.x86_64           3.17.7-300.local.fc21           @System
perf.x86_64                              3.17.7-300.local.fc21           @System
python-perf.x86_64                       3.17.7-300.local.fc21           @System

Comment 3 Jan Zeleny 2015-01-07 15:27:42 UTC
Well, the packages (i.e. their names) are the same. That means you are actually trying to do upgrade, not installation. Closing as duplicate ... as explained in bug 1179632, this is a well known behavior and it is being discussed.

*** This bug has been marked as a duplicate of bug 1179632 ***

Comment 4 Radek Holy 2015-01-07 15:55:13 UTC
I'm not sure whether this is really duplicate of that bug because kernel is special in the way that it's "installonly". I'd say it's more similar to bug 1177074. This is kind of different discussion.

*** This bug has been marked as a duplicate of bug 1177074 ***

Comment 5 Radek Holy 2015-02-09 14:31:30 UTC
OK, the root cause is the same as in bug 1179632 which is a duplicate of bug 1160950.

*** This bug has been marked as a duplicate of bug 1160950 ***


Note You need to log in before you can comment on or make changes to this bug.