Bug 201431 - yum doesn't handle file collisions wisely
Summary: yum doesn't handle file collisions wisely
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 5
Hardware: noarch
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-08-05 08:18 UTC by Jeff Silverman
Modified: 2014-01-21 22:54 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-09-18 21:05:06 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
This is a screen capture of a typical session which reproduces the problem (3.01 KB, text/plain)
2006-08-05 08:18 UTC, Jeff Silverman
no flags Details

Description Jeff Silverman 2006-08-05 08:18:26 UTC
Description of problem:

When two packages attempt to install the same file, yum detects that a file
collision has occurred and exits.  I think that the desired behavior should be
that it reports the problem, perhaps in a log file, and continues on with
everything else that it can do.  Otherwise, one has to redownload many many many
files.  Alternatively, if yum supported the --replacefiles switch as rpm does,
that would resolve the problem for me


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

How reproducible:
Reliably


Steps to Reproduce:  
1.  yum -y update wxGTK
2.  yum -y update --replacefiles wxGTK        ought to work, but the
--replacefiles switch isn't accepted.
3.
  
Actual results:


Expected results:


Additional info:
The underlying problem that triggers the error is described in bug 188370.

Comment 1 Jeff Silverman 2006-08-05 08:18:27 UTC
Created attachment 133674 [details]
This is a screen capture of a typical session which reproduces the problem

Comment 2 Jeremy Katz 2006-09-18 21:05:06 UTC
The removal+redownload bit should be fixed now.  But there's no way to "avoid"
the conflict -- it has to be handled by the user (or broken repositories should
be fixed, even better)


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