Bug 532961

Summary:	Is something supposed to be obsoleting DeviceKit in F12?
Product:	[Fedora] Fedora	Reporter:	Bruno Wolff III <bruno>
Component:	udev	Assignee:	Harald Hoyer <harald>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	12	CC:	alex, davidz, extras-orphan, harald, notting
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	145-15.fc12	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-01-26 11:09:58 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 Bruno Wolff III 2009-11-04 14:12:42 UTC

Description of problem:
DeviceKit got dropped from the F12 repo not too long ago. But updating didn't remove the package. So I suspect that something should be obsoleting it.

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

How reproducible:


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


Expected results:


Additional info:

Comment 1 Bill Nottingham 2009-11-04 18:51:17 UTC

I think udev was going to grow an obsolete eventually.

Comment 2 Harald Hoyer 2009-11-05 08:41:34 UTC

yes, will, preparing the package... waiting for another fix

Comment 3 Bug Zapper 2009-11-16 15:04:24 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Fedora Update System 2010-01-26 12:57:50 UTC

udev-145-15.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/udev-145-15.fc12

Comment 5 Fedora Update System 2010-02-12 04:46:14 UTC

udev-145-15.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.