Bug 247769

Summary:	unresolveable dependency for kdesdk
Product:	[Fedora] Fedora	Reporter:	Simon Zilliken <simon.zn>
Component:	kdebindings	Assignee:	Than Ngo <than>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	low
Version:	7
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-08-14 16:12:29 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 Simon Zilliken 2007-07-11 11:37:37 UTC

Description of problem:

yum update fails becasue of unresolveable dependencies for kdebindings:

[root@localhost ~]# yum update
Loading "installonlyn" plugin
Setting up Update Process
Excluding Packages in global exclude list
Finished
Resolving Dependencies
--> Running transaction check
---> Package kdebindings.x86_64 0:3.5.7-1.fc7.1 set to be updated
--> Processing Dependency: perl(DCOP) for package: kdesdk
--> Finished Dependency Resolution
Error: Unresolveable requirement perl(DCOP) for kdesdk

Comment 1 Sebastian Vahl 2007-08-14 07:01:50 UTC

Same here on i386. "repoquery -q --whatprovides "perl(DCOP)" shows that this 
packages provides the requirement:
kdebindings-0:3.5.6-1.fc7.i386
kdebindings-dcopperl-0:3.5.7-1.fc7.1.i386

After a manual installation of kdebindings-dcopperl I could update kdesdk. 
After this I've tried to reproduce this and deinstalled kdebindings-dcopperl, 
kdesdk and cleaned the yum cache. But now an installation of kdesdk works fine 
and pulls kdebindings-dcopperl as a requirement.

So this is maybe a yum problem?

Comment 2 Kevin Kofler 2007-08-14 15:58:01 UTC

I'd say it is, if it's possible to satisfy the dependencies, then it's probably 
yum's fault if it can't manage to.

Comment 3 Rex Dieter 2007-08-14 16:12:29 UTC

it's a bug in yum...

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