Bug 442004

Summary:	file conflicts - with deleted file - solved with yum clean all
Product:	[Fedora] Fedora	Reporter:	Bob Gustafson <bobgus>
Component:	yum	Assignee:	Seth Vidal <skvidal>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	8	CC:	ffesti, james.antill, katzj, pmatilai, tim.lauridsen
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:	2008-04-14 21:05:54 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 Bob Gustafson 2008-04-11 07:09:17 UTC

Description of problem:

I was trying to get synced up with Fedora openoffice after having installed the
openoffice.org version. I deleted lots of files and rebooted a couple of times
and finally came down to errors of the form:

Transaction Check Error:
  file
/usr/share/icons/hicolor/16x16/mimetypes/gnome-mime-application-vnd.oasis.opendocument.database.png
from install of openoffice.org-core-2.3.0-6.11.fc8.i386 conflicts with file from
package openoffice.org-redhat-menus-2.3-9238.noarch

The odd thing about these errors is that I really did delete the file 

/usr/share/icons/hicolor/16x16/mimetypes/gnome-mime-application-vnd.oasis.opendocument.database.png


It was just not in the directory when I did 'ls'.

The yum file conflicts persisted even after a reboot.

The solution was to go into yum and do

  yum clean all

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

  yum-3.2.8-2.fc8

How reproducible:

 Before doing the yum clean all, the error was frustratingly persistent.

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


Expected results:


Additional info:

Comment 1 Seth Vidal 2008-04-14 21:05:54 UTC

okay so you have separate items here:
1. removing the file doesn't remove it from the rpmdb's record of the file - so
that's why removing the file didn't help the problem
2. when you did the clean all you talked to a different mirror and/or reset your
metadata which probably had a fixed (and updated) openoffice which implicitly
fixed the problem you were having.

I'm going to close this not a bug b/c the error message it outputted for you was
entirely valid.

thanks