Bug 1465416
Summary: | nodejs-https-proxy-agent-2.2.1 is available | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> | ||||
Component: | nodejs-https-proxy-agent | Assignee: | Orphan Owner <extras-orphan> | ||||
Status: | NEW --- | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | rawhide | Keywords: | FutureFeature, Triaged | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Enhancement | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | Type: | --- | |||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Upstream Release Monitoring
2017-06-27 12:16:11 UTC
Created attachment 1292286 [details]
[patch] Update to 2.0.0 (#1465416)
hotness's scratch build of nodejs-https-proxy-agent-2.0.0-1.el7.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=20206182 Latest upstream release: 2.1.0 Current version/release in rawhide: 1.0.0-5.fc27 URL: http://npmjs.org/package/https-proxy-agent 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. Based on the information from anitya: https://release-monitoring.org/project/2434/ Skipping the scratch build because an SRPM could not be built: ['git', 'clone', 'https://src.fedoraproject.org/git/rpms/nodejs-https-proxy-agent.git', '/var/tmp/thn-rP_sZ4'] returned 128: Cloning into '/var/tmp/thn-rP_sZ4'... fatal: unable to access 'https://src.fedoraproject.org/git/rpms/nodejs-https-proxy-agent.git/': The requested URL returned error: 503 jsmith's nodejs-https-proxy-agent-2.1.0-1.fc28 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=972869 Latest upstream release: 2.2.0 Current version/release in rawhide: 2.1.0-1.fc28 URL: http://npmjs.org/package/https-proxy-agent 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. Based on the information from anitya: https://release-monitoring.org/project/2434/ Latest upstream release: 2.2.1 Current version/release in rawhide: 2.1.0-1.fc28 URL: http://npmjs.org/package/https-proxy-agent 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. Based on the information from anitya: https://release-monitoring.org/project/2434/ |