Bug 181055 - rfe: find duplicate packages
Summary: rfe: find duplicate packages
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: yum-utils
Version: 6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-02-12 12:55 UTC by Need Real Name
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version: 0.6
Clone Of:
Environment:
Last Closed: 2006-11-17 13:42:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2006-02-12 12:55:18 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20060205 Epiphany/1.9.6

Description of problem:
If yum gets interrupted during an update of a package, it may not call cleanup.

It would be good to have a yum util that checks for dupes of packages.

e.g. find these:
$ rpm -q vixie-cron
vixie-cron-4.1-42.FC5
vixie-cron-4.1-44.FC5

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
x

Additional info:

Comment 1 Seth Vidal 2006-02-24 16:39:04 UTC
We're working on various ways to avoid this problem but in the meantime would it
be reasonable for this feature to be in the package-cleanup script in yum-utils?

Comment 2 Need Real Name 2006-02-24 17:15:49 UTC
That would be great!

Comment 3 Seth Vidal 2006-02-24 21:32:53 UTC
okay I added package-cleanup --dupes

it will sort the rpmdb and produce the lists it ignores:

1. kernels b/c they can have dupes
2. gpg-pubkey 'packages' for obvious reasons
3. multilib 'duplicates'

it will print out anything else. It up to the user to figure out which one they
want to remove (though they should probably remove both and reinstall one of them)


Comment 4 Need Real Name 2006-03-06 18:39:50 UTC
Can you tell me which version this will be in?
I'm using rawhide version yum-utils-0.5-1.

Comment 5 Seth Vidal 2006-03-07 06:25:13 UTC
it'll be in 0.6.

hopefully I'll push that out in a few days.




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