Bug 1094738

Summary:	whois-5.1.2 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	whois	Assignee:	Petr Pisar <ppisar>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	ppisar
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	whois-5.1.2-1.fc21	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:
Clones:	1095166 (view as bug list)		Environment:
Last Closed:	2014-07-02 13:24:14 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 2014-05-06 11:45:35 UTC

Latest upstream release: 5.1.2
Current version/release in Fedora Rawhide: 5.1.1-1.fc21
URL: http://ftp.debian.org/debian/pool/main/w/whois/

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 2014-05-07 08:37:31 UTC

whois-5.1.2-1.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/whois-5.1.2-1.fc20

Comment 2 Fedora Update System 2014-05-07 08:37:48 UTC

whois-5.1.2-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/whois-5.1.2-1.fc19

Comment 3 Fedora Update System 2014-05-12 05:23:09 UTC

whois-5.1.2-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 4 Fedora Update System 2014-05-17 06:31:35 UTC

whois-5.1.2-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.