Bug 79482 - hif: duplicate kernel-headers package left after update
Summary: hif: duplicate kernel-headers package left after update
Alias: None
Product: PackageKit
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Richard Hughes
QA Contact:
Depends on:
Reported: 2014-05-31 14:12 UTC by Michael Catanzaro
Modified: 2014-06-05 19:46 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Description Michael Catanzaro 2014-05-31 14:12:00 UTC
When running 'yum install' I see the following warning:

** Found 1 pre-existing rpmdb problem(s), 'yum check' output follows:
kernel-headers-3.14.4-200.fc20.x86_64 is a duplicate with kernel-headers-3.14.3-200.fc20.x86_64

This is the only affected package so I wonder if it's related to the custom handling of the kernel package.

I'm using PackageKit-0.9.2-3.fc20 from the GNOME 3.12 copr.
Comment 1 Kalev Lember 2014-06-01 21:07:34 UTC
This might already be fixed by https://gitorious.org/packagekit/packagekit/commit/c3ddce1a4ec11884d57a10d023e8efd41fe7b2b4
Comment 2 Kalev Lember 2014-06-01 21:10:21 UTC
Never mind, sorry, I misread the patch; thought it was asking hy what packages are installonly, but it was hif.
Comment 3 Kalev Lember 2014-06-01 21:29:43 UTC
Anyway, I just tested this on rawhide and it seemed to work fine: updated kernel-headers and installed the rest of the kernel packages. Maybe some F20 quirk?
Comment 4 Kalev Lember 2014-06-05 19:46:24 UTC
I helped recover a Fedora installation today that had duplicate packages due to https://lists.fedoraproject.org/pipermail/desktop/2014-May/009777.html . One of those duplicate packages was kernel-headers and for some reason 'package-cleanup --dupes' left that one duplicate behind after properly cleaning up all the others. I suspect this is also what caused your kernel-header duplicate and there's nothing more to fix here on the PK side.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.