Bug 647980

Summary:	yum can't change symlink to directory
Product:	[Fedora] Fedora	Reporter:	Hicham HAOUARI <hicham.haouari>
Component:	yum	Assignee:	Seth Vidal <skvidal>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	14	CC:	cfeller, ffesti, james.antill, maxamillion, pmatilai, tim.lauridsen
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-11-01 13:59:24 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:
Bug Depends On:
Bug Blocks:	646185

Description Hicham HAOUARI 2010-10-30 09:21:15 UTC

Description of problem:
yum fails to change symlink to directory during update, surprisingly, it doesn't even accept the workaround which works in rpm in bug 646523 .

Version-Release number of selected component (if applicable):
3.2.28-5.fc14.noarch


Additional info:
See bug 646523 for more info

Comment 1 James Antill 2010-11-01 12:17:41 UTC

You'll have to give a lot more info. for us to tell if there is any problem in yum, from the other bug...

file
/usr/lib/mozilla/extensions/{718e30fb-e89b-41dd-9da7-e25a45638b28}/{9533f794-00b4-4354-aa15-c2bbda6989f8}/components/libnptray.so
from install of mozilla-firetray-sunbird-0.2.8-3.fc14.i686 conflicts with file
from package mozilla-firetray-core-0.2.8-3.fc14.i686

...yum can't see file conflicts, so if this is the kind of error you are getting it has to be from rpm.

Comment 2 Hicham HAOUARI 2010-11-01 12:57:05 UTC

the %pretrans scriplet from bug 646523 resolves the conflict at the rpm level, but yum still states a conflict.

so updating using rpm is fine, using yum, there is a conflict

Comment 3 Hicham HAOUARI 2010-11-01 12:57:38 UTC

what info do you need ?

Comment 4 James Antill 2010-11-01 13:11:52 UTC

> but yum still states a conflict.

As I said, if the conflict is a file conflict then _it isn't coming from yum_ because yum can't see file conflicts and so doesn't report them.

> what info do you need ?

It'd be helpful to show at least all of the output, but again if you are seeing file conflicts you might as well put the info. in bug#646523.

Comment 5 Hicham HAOUARI 2010-11-01 13:21:27 UTC

see : https://bugzilla.redhat.com/show_bug.cgi?id=646185#c5

Comment 6 James Antill 2010-11-01 13:59:24 UTC

 Ok, so I think the problem here is that when using yum we do the "transaction check", which asks rpm to test the transaction without doing anything (and thus. doesn't run pretrans scripts).
 It's possible that rpm could become very clever to work around this, but I doubt it. So I'd say that using pretrans to workaround the symlink => dir. issue just isn't doing to work.

Comment 7 Hicham HAOUARI 2010-11-01 14:46:59 UTC

what do you suggest for now ? ask the users to remove/install the package ?