Bug 1124473

Summary: yum reports filesystem has a file conflict with previous version of itself
Product: [Fedora] Fedora Reporter: Bruno Wolff III <bruno>
Component: rpmAssignee: Packaging Maintenance Team <packaging-team-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: admiller, bruno, jzeleny, lkardos, novyjindrich, packaging-team-maint, pknirsch
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-30 10:41:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
yum output none

Description Bruno Wolff III 2014-07-29 14:44:55 UTC
Created attachment 922171 [details]
yum output

Description of problem:
When updating the filesystem package a conflict is reported with a previous version of itself, which doesn't make sense since the old version is being removed.

Version-Release number of selected component (if applicable):
yum-3.4.3-152.fc21

Comment 1 Bruno Wolff III 2014-07-29 14:50:07 UTC
dnf has the same problem, so there may be a problem with some of the backend stuff.

Comment 2 Bruno Wolff III 2014-07-29 14:53:00 UTC
rpm has the same problem so I am moving this to rpm.

[root@bruno f]# rpm -Uvh filesystem-3.2-28.fc22.i686.rpm
Preparing...                          ################################# [100%]
	file /media from install of filesystem-3.2-28.fc22.i686 conflicts with file from package filesystem-3.2-27.fc22.i686

Comment 3 Ľuboš Kardoš 2014-07-30 10:41:11 UTC
The problem is that directory /media changed to symlink to /run/media. This change was done because of bug 965918. For problem changing directory to symlink a bug already exits (bug 447156).

*** This bug has been marked as a duplicate of bug 447156 ***