155381 - checksetup.pl fails when testing the database

Status: RESOLVED INVALID

(Bugzilla :: Installation & Upgrading, defect, P2)

Description

[magnus.sandberg]

On my debian Potato (2.2.19) 'checksetup.pl' fails when contacting 
the database.

Modules are:
> Checking perl modules ...
> Checking for             DBI (v1.13)   ok: found v1.13
> Checking for    Data::Dumper (any)     ok: found v2.101
> Checking for      DBD::mysql (v1.2209) ok: found v2.0402
> Checking for     Date::Parse (any)     ok: found v2.09
> Checking for       CGI::Carp (any)     ok: found v1.13

MySQL:
> Checking user setup ...
> Checking for    MySQL Server (v3.22.5) ok: found v3.22.32-log

checkup fails on line 1136 if the database is empty 
(Sorry can't reproduce the error once the tables 
are created, if the tables are there the script
works as supposed)

My fix was the change the line (1136) from:
> my @tables = map { $_ =~ s/.*\.//; $_ } $dbh->tables;
to:
> my @tables;

skipping the command that fails ($dbh->tables),
doing this skips the checking step and successfully
creates the tables.

Comment 1

[Jouni Heikniemi]

>checkup fails on line 1136 if the database is empty 

Wfm a million times on me, both on Win32 and unix.

What's the error message you're getting?

How did the tables get created if your checksetup failed?

Comment 2

[Zach Lipton [:zach]]

I need more information on this problem to fix this bug. I am not able to
reproduce here on Debian or redhat. Can you try this on an empty new database
and report the _exact_ error message from checksetup.pl?

Comment 3

[Gervase Markham [:gerv]]

Closing as INVALID due to lack of response from reporter.

Gerv

Comment 4

[Dave Miller [:justdave]]

clearing target on DUPLICATE/WONTFIX/INVALID/WORKSFORME so they'll show up as
untriaged if they get reopened.