Bug 597759

Summary: perl-DBD-MySQL-4.015 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: perl-DBD-MySQLAssignee: Petr Pisar <ppisar>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: mmaslano, ppisar
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
URL: http://cpansearch.perl.org/src/CAPTTOFU/DBD-mysql-4.014/ChangeLog
Whiteboard:
Fixed In Version: perl-DBD-MySQL-4.016-1.fc13 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-03 00:42:00 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 Upstream Release Monitoring 2010-05-30 11:32:26 UTC
Latest upstream release: 4.014
Current version in Fedora Rawhide: 4.013
URL: http://www.cpan.org/authors/id/C/CA/CAPTTOFU/

Please consult the package update guidelines before you issue an update to a stable branch: https://fedoraproject.org/wiki/Package_update_guidelines

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_Release_Monitoring

Comment 1 Petr Pisar 2010-05-31 10:57:20 UTC
4.014 contains significant fixes. F-12,13 delivers 4.013 too. I think rebase for these two stable Fedoras is useful.

OTOH, 4.014 contains functional bug <https://rt.cpan.org/Public/Bug/Display.html?id=57253> leading to segfault while parsing SQL-embedded comments.

I pushed 4.014 to F-14. Upgrade for lower Fedoras will be delayed until the bug is fixed.

Comment 2 Upstream Release Monitoring 2010-07-10 10:44:14 UTC
Latest upstream release: 4.015
Current version in Fedora Rawhide: 4.014
URL: http://search.cpan.org/dist/DBD-mysql/

Please consult the package update guidelines before you issue an update to a stable branch: https://fedoraproject.org/wiki/Package_update_guidelines

More information about the service that created this bug can be found at:
https://fedoraproject.org/wiki/Upstream_Release_Monitoring

Comment 3 Petr Pisar 2010-07-12 09:13:01 UTC
Bug in 4.014 should be fixed in 4.015, upgrading to 4.016 released meantime in all Fedoras.

Fixed as perl-DBD-MySQL-4.016-1.fc14 in F14.

Comment 4 Fedora Update System 2010-07-12 09:18:20 UTC
perl-DBD-MySQL-4.016-1.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/perl-DBD-MySQL-4.016-1.fc13

Comment 5 Fedora Update System 2010-07-12 09:23:05 UTC
perl-DBD-MySQL-4.016-1.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/perl-DBD-MySQL-4.016-1.fc12

Comment 6 Fedora Update System 2010-07-13 07:54:36 UTC
perl-DBD-MySQL-4.016-1.fc12 has been pushed to the Fedora 12 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 'yum --enablerepo=updates-testing update perl-DBD-MySQL'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/perl-DBD-MySQL-4.016-1.fc12

Comment 7 Fedora Update System 2010-07-13 07:54:42 UTC
perl-DBD-MySQL-4.016-1.fc13 has been pushed to the Fedora 13 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 'yum --enablerepo=updates-testing update perl-DBD-MySQL'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/perl-DBD-MySQL-4.016-1.fc13

Comment 8 Fedora Update System 2010-08-03 00:41:56 UTC
perl-DBD-MySQL-4.016-1.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2010-08-03 00:42:18 UTC
perl-DBD-MySQL-4.016-1.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.