Bug 1450921

Summary: gperftools-2.5.91 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: gperftoolsAssignee: Tom "spot" Callaway <tcallawa>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: tcallawa
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gperftools-2.5.91-1.fc26 gperftools-2.5.93-1.fc26 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-09 18:58:08 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:
Attachments:
Description Flags
[patch] Update to 2.5.91 (#1450921) none

Description Upstream Release Monitoring 2017-05-15 12:12:54 UTC 
Latest upstream release: 2.5.91
Current version/release in rawhide: 2.5-5.fc26
URL: https://github.com/gperftools/gperftools

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/1238/
Comment 1 Upstream Release Monitoring 2017-05-15 12:13:02 UTC 
Created attachment 1278954 [details]
[patch] Update to 2.5.91 (#1450921)
Comment 2 Upstream Release Monitoring 2017-05-15 12:22:19 UTC 
hotness's scratch build of gperftools-2.5.91-1.el7.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=19565172
Comment 3 Upstream Release Monitoring 2017-05-15 15:04:50 UTC 
spot's gperftools-2.5.91-1.fc27 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=892234
Comment 4 Fedora Update System 2017-05-15 15:06:05 UTC 
gperftools-2.5.91-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-410a632bc7
Comment 5 Fedora Update System 2017-05-16 06:09:30 UTC 
gperftools-2.5.91-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-410a632bc7
Comment 6 Upstream Release Monitoring 2017-05-22 08:27:33 UTC 
rjones's gperftools-2.5.91-2.fc27 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=895663
Comment 7 Fedora Update System 2017-05-23 15:24:18 UTC 
gperftools-2.5.93-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-685f48d47a
Comment 8 Fedora Update System 2017-05-25 19:18:51 UTC 
gperftools-2.5.93-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-685f48d47a
Comment 9 Fedora Update System 2017-06-09 18:58:08 UTC 
gperftools-2.5.91-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
Comment 10 Fedora Update System 2017-06-09 19:09:29 UTC 
gperftools-2.5.93-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.