Bug 1284946

Summary:	nodejs-nano-6.1.5 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	nodejs-nano	Assignee:	Parag Nemade <pnemade>
Status:	CLOSED NEXTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	pnemade, tom
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:	2015-11-24 14:15:00 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 2015-11-24 14:06:22 UTC

Latest upstream release: 6.1.5
Current version/release in rawhide: 6.0.2-2.fc23
URL: http://github.com/dscape/nano

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

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Comment 1 Upstream Release Monitoring 2015-11-24 14:06:28 UTC

Failed to kick off scratch build.

spectool was unable to grab new sources

old source: nano-6.1.5.tgz
old sha256: 44668d153ab05d9d601d959cf80c5309123634071db5525ab373fe5ca969f630

new source: ./nano-6.1.5.tgz
new sha256: 44668d153ab05d9d601d959cf80c5309123634071db5525ab373fe5ca969f630

Comment 2 Parag Nemade 2015-11-24 14:15:00 UTC

wow Tom you are fast and beat the upstream monitoring script but it beat the koji build database.

Bug got reported when build was already done ;-)

Comment 3 Tom Hughes 2015-11-24 14:21:43 UTC

No it's just that I turned on the monitoring while it was building ;-)