Closed Bug 211973 Opened 22 years ago Closed 22 years ago

checksetup.pl can be only run once in 2.17.x (x=3 and 4)

Categories

(Bugzilla :: Installation & Upgrading, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 212095

People

(Reporter: omgs, Assigned: zach)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.4) Gecko/20030625 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.4) Gecko/20030625 In both 2.17.x, the checksetup.pl can only be run once, because seems to check the existence of some tables, and if it finds some (I haven't tried all, but at least the "tokens" table), refuses to go on. Since it's for trial purposes and I have no data, if I drop the entire database, the checksetup.pl creates the db, but only for the first time, because if I run it again, I get the same situation as before, but seems to run (after the erasure and first retry). Reproducible: Always Steps to Reproduce: 1. Install bugzilla 2.17.3 or 2.17.4. 2. Run ./checksetup.pl 3. Actual Results: Bugzilla returned an error saying that the table 'tokens' already existed in database. Expected Results: The same as previous versiones, i.e., check whatever necessary, but not refusing to go on if simply a table (created by checksetup.pl itself) already exists
Is this an out of the box or an upgrade? I'm using 2.17.4 as an upgrade in several places and can't reproduce. It sounds like whatever it's testing to determine whether it has to create the tokens table is failing so it then tries to create it, which then fails because it's already there.
# ls -l checksetup.pl -rwxr-x--- 1 root www-data 142051 abr 25 01:11 checksetup.pl # ./checksetup.pl Checking perl modules ... Checking for AppConfig (v1.52) ok: found v1.55 Checking for CGI (v2.88) ok: found v2.93 Checking for Data::Dumper (any) ok: found v2.102 Checking for Date::Format (v2.21) ok: found v2.22 Checking for DBI (v1.32) ok: found v1.37 Checking for DBD::mysql (v2.1010) ok: found v2.9002 Checking for File::Spec (v0.82) ok: found v0.82 Checking for File::Temp (any) ok: found v0.12 Checking for Template (v2.08) ok: found v2.08 Checking for Text::Wrap (v2001.0131) ok: found v2001.0929 The following Perl modules are optional: Checking for GD (v1.20) found v1.19 Checking for Chart::Base (v0.99) ok: found v2.2 Checking for XML::Parser (any) ok: found v2.30 Checking for GD::Graph (any) ok: found v1.39 Checking for GD::Text::Align (any) ok: found v1 If you you want to see graphical bug charts (plotting historical data over time), you should install libgd and the following Perl modules: GD: perl -MCPAN -e'install "GD"' If you you want to see graphical bug reports (bar, pie and line charts of current data), you should install libgd and the following Perl modules: GD: perl -MCPAN -e'install "GD"' Checking user setup ... Removing existing compiled templates ... Precompiling templates ... Checking for MySQL Server (v3.23.41) ok: found v3.23.51-log Creating table tokens ... [Mon Jul 7 21:22:00 2003] checksetup.pl: DBD::mysql::db do failed: Table 'tokens' already exists at ./checksetup.pl line 1808. Could not create table 'tokens'. Please check your 'mysql' access.
Sorry, I didn't read the first part of the message. It's out of the box, just download from www.bugzilla.org, uncompressed and configured. Now I'm translating the templates into spanish. The installation works (or that's what it seems). Now I'm only using 2.17.4.
I am unable to reproduce this, either with 2.17.4 or the CVS tip. Steps I'm using to attempt to reproduce: cvs -q update -dP -rBUGZILLA-2_17_4 (this is the command that was used to produce the tarball) rm -rf data mysql -u bugs -e 'drop database bugs;' ./checksetup.pl (creates database normally, says it's successful) ./checksetup.pl (run second time, does version checks, recompiles templates, no changes to database) Then repeated the test with cvs tip, with same results.
This looks a bit like bug 212095.
From comment #2: > Checking for DBD::mysql (v2.1010) ok: found v2.9002 Sounds like we have a winner. The other is a newer bug, but it has a better and more to-the-point description, and a fix suggestion in the works already. *** This bug has been marked as a duplicate of 212095 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.