Bug 498899
Summary: | perl-DBD-Pg: two memleaks from upstream RT | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tomas Hoger <thoger> |
Component: | perl-DBD-Pg | Assignee: | Stepan Kasal <kasal> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | devrim, kasal, mmaslano |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-05-04 13:04:57 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: |
Description
Tomas Hoger
2009-05-04 10:25:34 UTC
These does not affect DBD-Pg 1.x currently in RHEL. I did not investigate more closely if these are likely to be exposed in some applications in a harmful way. Would be good to make sure these are fixed before RHEL6 to avoid errata process overhead. perl-DBD-Pg-2.13.1-1.fc9 has been submitted as an update for Fedora 9. http://admin.fedoraproject.org/updates/perl-DBD-Pg-2.13.1-1.fc9 perl-DBD-Pg-2.13.1-1.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/perl-DBD-Pg-2.13.1-1.fc10 perl-DBD-Pg-2.13.1-1.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/perl-DBD-Pg-2.13.1-1.fc11 perl-DBD-Pg-2.13.1-1.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report. perl-DBD-Pg-2.13.1-1.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report. perl-DBD-Pg-2.13.1-1.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report. |