Bug 1284946 - nodejs-nano-6.1.5 is available
nodejs-nano-6.1.5 is available
Product: Fedora
Classification: Fedora
Component: nodejs-nano (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Parag Nemade
Fedora Extras Quality Assurance
: FutureFeature, Triaged
Depends On:
  Show dependency treegraph
Reported: 2015-11-24 09:06 EST by Upstream Release Monitoring
Modified: 2015-11-24 09:21 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-11-24 09:15:00 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Upstream Release Monitoring 2015-11-24 09:06:22 EST
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 09:06:28 EST
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 09:15:00 EST
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 09:21:43 EST
No it's just that I turned on the monitoring while it was building ;-)

Note You need to log in before you can comment on or make changes to this bug.