Bug 1224781
| Summary: | python-elasticsearch-1.7.0 is available | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> | ||||||
| Component: | python-elasticsearch | Assignee: | Daniel Bruno <dbruno> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | rawhide | CC: | dbruno, piotr1212 | ||||||
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged | ||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | python-elasticsearch-1.7.0-1.fc22 | Doc Type: | Enhancement | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2015-10-15 03:49:52 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: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1258662 | ||||||||
| Attachments: |
|
||||||||
|
Description
Upstream Release Monitoring
2015-05-25 17:18:34 UTC
Created attachment 1029547 [details]
[patch] Update to 1.5.0 (#1224781)
Scratch build succeeded http://koji.fedoraproject.org/koji/taskinfo?taskID=9843263 Latest upstream release: 1.6.0 Current version/release in rawhide: 1.4.0-2.fc23 URL: https://github.com/elasticsearch/elasticsearch-py 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. Created attachment 1037261 [details]
[patch] Update to 1.6.0 (#1224781)
Scratch build succeeded http://koji.fedoraproject.org/koji/taskinfo?taskID=10003115 Latest upstream release: 1.7.0 Current version/release in rawhide: 1.4.0-3.fc23 URL: https://github.com/elasticsearch/elasticsearch-py 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. Failed to kick off scratch build. cmd: sha256sum /var/tmp/thn-eZ1Mk2/100.0% return code: 1 stdout: stderr: sha256sum: /var/tmp/thn-eZ1Mk2/100.0%: No such file or directory dbruno's python-elasticsearch-1.7.0-1.fc24 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=687036 python-elasticsearch-1.7.0-1.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-16427 python-elasticsearch-1.7.0-1.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update python-elasticsearch' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-16427 python-elasticsearch-1.7.0-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. |