Bug 901975

Summary:	crda-1.1.3 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	crda	Assignee:	John W. Linville <linville>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	linville
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-01-25 20:05:48 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 Upstream Release Monitoring 2013-01-20 10:34:44 UTC

Latest upstream release: 1.1.3
Current version in Fedora Rawhide: 1.1.2_2011.04.28
URL: http://wireless.kernel.org/download/crda/

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_release_monitoring

Comment 1 Fedora Update System 2013-01-25 19:59:51 UTC

crda-1.1.3_2013.01.11-2.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/crda-1.1.3_2013.01.11-2.fc18

Comment 2 Fedora Update System 2013-01-25 20:01:09 UTC

crda-1.1.3_2013.01.11-1.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/crda-1.1.3_2013.01.11-1.fc17

Comment 3 Fedora Update System 2013-02-05 03:05:00 UTC

crda-1.1.3_2013.01.11-2.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 4 Fedora Update System 2013-02-05 03:16:25 UTC

crda-1.1.3_2013.01.11-1.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.