Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1292991 - nodejs-error-ex-1.3.0 is available
Summary: nodejs-error-ex-1.3.0 is available
Alias: None
Product: Fedora
Classification: Fedora
Component: nodejs-error-ex
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Parag Nemade
QA Contact: Fedora Extras Quality Assurance
Depends On: 1293204
TreeView+ depends on / blocked
Reported: 2015-12-19 00:23 UTC by Upstream Release Monitoring
Modified: 2015-12-24 08:14 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed: 2015-12-24 08:14:38 UTC

Attachments (Terms of Use)

Description Upstream Release Monitoring 2015-12-19 00:23:00 UTC
Latest upstream release: 1.3.0
Current version/release in rawhide: 1.2.0-1.fc24

Please consult the package updates policy before you issue an update to a stable branch:

More information about the service that created this bug can be found at:

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-12-19 00:23:09 UTC
Failed to kick off scratch build.

spectool was unable to grab new sources

old source: error-ex-1.2.0.tar.gz
old sha256: 5412ff50850c6108f94fac5439d22751632b9450a557c9e4fa1bdd26aa5bfbad

new source: ./error-ex-1.2.0.tar.gz
new sha256: 5412ff50850c6108f94fac5439d22751632b9450a557c9e4fa1bdd26aa5bfbad

Comment 2 Upstream Release Monitoring 2015-12-21 04:09:23 UTC
pnemade's nodejs-error-ex-1.3.0-1.fc24 completed

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