Bug 451729 - "package-cleanup --cleandupes" doesn't appear to clean duplicate kernel-headers packages
"package-cleanup --cleandupes" doesn't appear to clean duplicate kernel-heade...
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: yum-utils (Show other bugs)
rawhide
All Linux
low Severity low
: ---
: ---
Assigned To: Seth Vidal
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-16 20:01 EDT by Tom London
Modified: 2014-01-21 01:10 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-09-08 09:02:18 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Tom London 2008-06-16 20:01:08 EDT
Description of problem:
I had the situatation where I had to cleanup lots of duped packages, but
package-cleanup didn't clean up duplicate kernel-headers packages.

Version-Release number of selected component (if applicable):
yum-utils-1.1.14-4.fc10.noarch

How reproducible:
Every time

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Jan Hutař 2008-09-08 08:37:39 EDT
Hello,
same for me on F8 with yum-utils-1.1.14-4.fc8 - maybe it is intentional?:

# package-cleanup --dupes
Setting up yum
abcde-2.3.99.6-4.fc8.noarch
abcde-2.3.99.6-6.noarch
# rpm -q abcde kernel-headers
abcde-2.3.99.6-6
abcde-2.3.99.6-4.fc8
kernel-headers-2.6.23.1-42.fc8
kernel-headers-2.6.25.14-69.fc8
Comment 2 seth vidal 2008-09-08 09:02:18 EDT
anything starting with kernel is intentionally ignored.
Comment 3 Tom London 2008-09-08 09:24:10 EDT
But does that make sense?

Newer packages like kernel-headers and kernel-firmware are updated, not installed, so there shouldn't be duplicate versions of them.

Wouldn't it make sense for package-cleanup to only ignore dupes on packages that it "installs only"?

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