Bug 178895

Summary:	two vixie-crons installed
Product:	[Fedora] Fedora	Reporter:	Need Real Name <lsof>
Component:	yum	Assignee:	Jeremy Katz <katzj>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5	CC:	jvdias
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-02-12 12:55:58 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Need Real Name 2006-01-25 10:26:32 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050923 Epiphany/1.6.5

Description of problem:
A fresh install of FC5T2, then yum update, yum upgrade gives me two vixie-crons:

$ 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:
Didn't try

Steps to Reproduce:
x

Additional info:

Comment 1 Jason Vas Dias 2006-01-25 14:56:33 UTC

Nothing has changed in the vixie-cron .spec file that could cause this.

When yum cannot complete its Update transaction for some reason, it may not
do its "Cleanup" transaction, so duplicates of many packages can remain -
this has happened for me many times. When it does, I manually find all the
duplicate packages and then 'rpm -Uvh --force' the duplicates to the newer
package.

I think if this occurs, yum should at least save a "cleanup" script that 
users can run, or should automatically retry a previously failed cleanup
phase on the next run - leaving duplicate instances of packages around is
not a good idea.

Comment 2 Need Real Name 2006-02-12 12:55:58 UTC

Thanks! Filed RFE bug 181055.