Bug 446974

Summary:	kyum needs to be updated to depend on kdebase3
Product:	[Fedora] Fedora	Reporter:	Jef Spaleta <jspaleta>
Component:	kyum	Assignee:	Jochen Schmitt <jochen>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	9	CC:	tuxbrewr
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	0.7.5-12.fc9	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-05-31 02:10:50 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 Jef Spaleta 2008-05-16 19:43:27 UTC

Description of problem:
kyum will not run correctly on F9 unless kdebase3 is installed.
kyum does not require kdebase3 be installed through appropriate packaging
requirements.


Version-Release number of selected component (if applicable):
kyum 0.7.5-11.fc9


How reproducible:
always until kdebase3 is manually installed so that /usr/bin/kdesu is available.


-jef

Comment 1 Fedora Update System 2008-05-18 18:09:55 UTC

kyum-0.7.5-12.fc9 has been submitted as an update for Fedora 9

Comment 2 Fedora Update System 2008-05-21 10:55:02 UTC

kyum-0.7.5-12.fc9 has been pushed to the Fedora 9 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update kyum'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-4149

Comment 3 Fedora Update System 2008-05-31 02:10:48 UTC

kyum-0.7.5-12.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 4 Fedora Update System 2008-07-26 05:58:14 UTC

kyum-0.7.5-12.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.