From: George C. <ga...@sp...> - 2003-09-28 18:10:17
|
Hi, I'm about to do the mysql upgrade to get ready to going to the latest r-tag on Slash. (At least it *was* going to happen tonight). Most likely not the right place to ask, but can anybody help with an error I'm getting with the perl updates? The mysql upgrade worked fine from debian testing, and I'm assuming that I need to rebuild the perl DBI modules with CPAN. The following seem to be the "db" related modules from Bundle::Slash DBI Bundle::DBD::mysql DBIx::Password Apache::DBI Since my versions are up to date, I've issued "force install" on each of these packages. All of them rebuilt okay except for Apache::DBI, which fails with: Running make test PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/10mysql....NOK 5# Failed test (t/10mysql.t at line 35) # got: '3' # expected: '4' t/10mysql....ok 7/7# Looks like you failed 1 tests of 7. t/10mysql....dubious Test returned status 1 (wstat 256, 0x100) My test slash system still seems to be working after this, but I'm a little concerned about going ahead and running the upgrade on my production system with this error. Production is currently running mysql 3.23.52, and Perl 5.8.0 (I'm also getting a warning that perl is configured with threading enabled, and this is not recommended in production. But I suspect that it has always been that way on this system.) Any comments / suggestions? I'm also planning on doing a mysqldump and restore on the production system just to make sure that the tables are clean across the upgrade. The Debian upgrade installed the following sql packages & upgrades: Inst libncurses5-dev (5.3.20030719-1 Debian:testing) Inst libncurses5 (5.3.20030719-1 Debian:testing) Inst gcc-3.3-base (1:3.3.2-0pre4 Debian:testing) Inst libgcc1 (1:3.3.2-0pre4 Debian:testing) Inst libstdc++5 (1:3.3.2-0pre4 Debian:testing) Inst mysql-common (4.0.13-3 Debian:testing) Inst libmysqlclient12 (4.0.13-3 Debian:testing) Inst libmysqlclient-dev (4.0.13-3 Debian:testing) Inst mysql-client (4.0.13-3 Debian:testing) Inst mysql-doc (4.0.15-1 Debian:testing) Inst mysql-server (4.0.13-3 Debian:testing) Thanks, George |
From: alex <al...@ow...> - 2003-10-02 07:41:55
|
At 13:06 28/09/03, George Clark wrote: >The mysql upgrade worked fine from debian testing, and I'm assuming that >I need to rebuild the perl DBI modules with CPAN. The following seem to >be the "db" related modules from Bundle::Slash I wouldn't expect you *need* to. >DBI >Bundle::DBD::mysql >DBIx::Password >Apache::DBI Don't update DBIx::Password without backing it up first. It is little more than a config file. > All of them rebuilt okay except for Apache::DBI, which >fails with: > >Running make test >PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" >"test_harness(0, 'blib/lib', 'blib/arch')" t/*.t >t/10mysql....NOK 5# Failed test (t/10mysql.t at line 35) ># got: '3' ># expected: '4' >t/10mysql....ok 7/7# Looks like you failed 1 tests of 7. >t/10mysql....dubious > Test returned status 1 (wstat 256, 0x100) Can you not show us the error log created within the build directory? cd blah/.cpan/build/Apachesomething/t/ and look for error.log I have just re-discovered that although you may need to install perl modules as root many also *fail* if you test them as root. This is a major failing in the way CPAN works IMHO. Alex |
From: George C. <ga...@sp...> - 2003-10-02 12:31:06
|
** Reply to message from alex <al...@ow...> on Thu, 02 Oct 2003 08:43:21 +0100 Hi Alex, > Don't update DBIx::Password without backing it up first. > It is little more than a config file. Yup... figured that out <g>. > Can you not show us the error log created within the build directory? > > cd blah/.cpan/build/Apachesomething/t/ > > and look for error.log Nothing there. Just in case CPAN removed it, I changed to that directory and reran the "make test". Same failure, but still no error log. Is there something needed on the Make to generate a persistent log? > I have just re-discovered that although you may need to install perl > modules as root many also *fail* if you test them as root. This is a major > failing in the way CPAN works IMHO. I'm running CPAN as root. So I think that I'm covered here. Thanks, George |