Bug 178895 - two vixie-crons installed
Summary: two vixie-crons installed
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-01-25 10:26 UTC by Need Real Name
Modified: 2014-01-21 22:53 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-12 12:55:58 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

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.


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