User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041223 Firefox/1.0 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041223 Firefox/1.0 I was not able to get checksetup.pl to run cleanly with the latest bugzilla tip. The script now uses the new DB::bz_server_version function. Was able to solve this problem by upgrading my DBD::mysql version from 2.1028 to the latest (2.9004) Reproducible: Always Steps to Reproduce:

No, only to 2.9002.

Ok, 2.9002 it is.

Can bz_server_version be hacked to not require the newer version of DBD::mysql?

*** Bug 289107 has been marked as a duplicate of this bug. ***

Comment on attachment 179302 [details] [diff] [review] patch 2.9002 doesn't work on windows, throws: Renaming indexes... Undefined subroutine &DBD::mysql::db::SQL_INTEGER called at d:/Perl/site/lib/DBD/mysql.pm line 362 2.9003 works.

Anyone care to answer Myk's question in comment 3? Current patch has a denied review anyway, removing approval request.

(In reply to comment #3) > Can bz_server_version be hacked to not require the newer version of DBD::mysql? It could be hacked, but I don't think it would be database independent. Granted, I don't know where we're at with respect to Postgres support.

We require 2.9003 for many other reasons than bz_server_version. For example, the new Schema code needs column_info to work properly, and so forth. 2.9003 is *years* old at this point. It's not a big problem, I think.

Checking in checksetup.pl; /cvsroot/mozilla/webtools/bugzilla/checksetup.pl,v <-- checksetup.pl new revision: 1.396; previous revision: 1.395 done

Added to the release notes in bug 286274.