Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 156059 - perl-DBD-MySQL: update to 2.9007
Summary: perl-DBD-MySQL: update to 2.9007
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-DBD-MySQL
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Chip Turner
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-04-27 07:16 UTC by Jose Pedro Oliveira
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-04-27 07:22:09 UTC


Attachments (Terms of Use)
Update to version 2.9007 (deleted)
2005-04-27 07:16 UTC, Jose Pedro Oliveira
no flags Details | Diff

Description Jose Pedro Oliveira 2005-04-27 07:16:34 UTC
Version-Release number of selected component (if applicable):
2.9006-1

Expected results:
2.9007-1

Additional info:
Test suite disbaled.
It passes all tests in a FC4test2 system with MySQL 4.1.11-2

Comment 1 Jose Pedro Oliveira 2005-04-27 07:16:34 UTC
Created attachment 113702 [details]
Update to version 2.9007

Comment 2 Warren Togami 2005-04-27 07:20:52 UTC
Thanks, checked in.  Be aware that FC4test3 freeze happens in about 10 hours,
after that point we cannot upgrade any versions.  I can remain awake to checkin
things for another 3 hours.


Comment 3 Jose Pedro Oliveira 2005-04-27 07:48:56 UTC
Thanks for the update.

DBD::MySQL only apperead in CPAN yesterday
(http://search.cpan.org/recent).

Do you still accept scpefile cleanups after test3?
(Thera are still a couple of modules that were built with perl-5.8.5.)


Comment 4 Warren Togami 2005-04-27 08:13:12 UTC
yes spec cleanups after test3 are fine.  Only version upgrades are bad.



Note You need to log in before you can comment on or make changes to this bug.