I started using RT 1 six months ago. This is my first look at RT2.
The installation was done on a Debian GNU/Linux system using mostly
TESTING and some UNSTABLE.
I wanted to use PostgreSQL, but the latest version (in unstable) is
7.0.3-4. So I used MySQL.
MySQL 3.23.33
Perl v5.6.0
DBI 1.13
DBD::mysql 2.0415
DBIx::DataSource 0.02
DBIx::DBSchema 0.16
The initdb didn’t work. I got errors on tows 71 and 73:
print “\nCreating database schema.\n”;
my $dbh = DBI->connect( $dsn, $DB_DBA, $DB_DBA_PASSWORD ) or die $DBI::errstr;
foreach my $statement ( $schema->sql($dsn, $DB_DBA, $DB_DBA_PASSWORD ) ) {
print STDERR $statement if $DEBUG;
my $sth = $dbh->prepare($statement) or die $dbh->errstr;
unless ($sth->execute) {
print STDERR “Problem with statement:\n $statement\n”;
die $sth->errstr;
}
}
It was a lot of errors (sorry, didn’t save them) about two things
during table creation:
It tried to create indexes there one of the keys was marked as NULL
instead of NOT NULL. That was not allowed.
It tried to produce keys longer that 255 bytes. Ie, the combined
length of an primary key or index key was too long.
I changed a number of NULL to not NULL and commented out many
indexes. The changed file is included here:
Are you sure you’re running mysql 3.23? those errors sound a lot like what
would happen with 3.22.
I don’t in fact get any such errors running make install
on an up to date debian unstable box.
what does perl tools/testdep -warn mysql
tell you?
if you could rerun the broken install and capture the error messages, I’d
greatly appreciate it.
Thanks,
jesse
I started using RT 1 six months ago. This is my first look at RT2.
The installation was done on a Debian GNU/Linux system using mostly
TESTING and some UNSTABLE.
I wanted to use PostgreSQL, but the latest version (in unstable) is
7.0.3-4. So I used MySQL.
MySQL 3.23.33
Perl v5.6.0
DBI 1.13
DBD::mysql 2.0415
DBIx::DataSource 0.02
DBIx::DBSchema 0.16
The initdb didn’t work. I got errors on tows 71 and 73:
print “\nCreating database schema.\n”;
my $dbh = DBI->connect( $dsn, $DB_DBA, $DB_DBA_PASSWORD ) or die $DBI::errstr;
foreach my $statement ( $schema->sql($dsn, $DB_DBA, $DB_DBA_PASSWORD ) ) {
print STDERR $statement if $DEBUG;
my $sth = $dbh->prepare($statement) or die $dbh->errstr;
unless ($sth->execute) {
print STDERR “Problem with statement:\n $statement\n”;
die $sth->errstr;
}
}
It was a lot of errors (sorry, didn’t save them) about two things
during table creation:
It tried to create indexes there one of the keys was marked as NULL
instead of NOT NULL. That was not allowed.
It tried to produce keys longer that 255 bytes. Ie, the combined
length of an primary key or index key was too long.
I changed a number of NULL to not NULL and commented out many
indexes. The changed file is included here:
what does perl tools/testdep -warn mysql
tell you?
Checking for DBI 1.13 …found
Checking for DBIx::DataSource 0.02 …found
Checking for DBIx::DBSchema 0.14 …found
Checking for DBIx::SearchBuilder 0.22 …found
Checking for Apache::DBI…Apache::DBI not installed.
Checking for HTML::Entities…found
Checking for MLDBM…found
Checking for HTML::Mason 0.896 …found
Checking for CGI::Cookie 1.06 …found
Checking for Apache::Session 1.53 …found
Checking for Date::Manip…found
Checking for Date::Format…found
Checking for MIME::Entity 5.108 …found
Checking for Mail::Mailer 1.20 …found
Checking for Getopt::Long 2.24 …found
Checking for Tie::IxHash…found
Checking for Text::Wrapper…found
Checking for Text::Template…found
Checking for File::Spec 0.8 …found
Checking for File::Temp…found
Checking for Log::Dispatch 1.6 …found
Checking for DBD::mysql …found
actually, it’s from within mysql that was the question, but I’ve got it now.
select version();
thanks,
jesseOn Fri, Mar 09, 2001 at 03:57:15PM -0700, Robert Tarrall wrote:
Jesse wrote:
→ > I missed that. But it would be helpful to provide an instruction on
→ > how to find out the versions needed.
→
→ nod I’ve been looking, but don’t see any mysql API for determining
→ server version. I’ll keep at it. If you know any tricks
This seems too easy, but…
<~> mysqld --version
/usr/local/mysql/bin/mysqld Ver 3.23.33 for pc-linux-gnu on i686
Is this what you’re looking for?
-Robert Tarrall.-
Unix System/Network Admin
E.Central/Neighborhood Link
Another (offtopic) comment about me having multiple versions of the
diffrent parts om mysql:
The latest unstable mysql-server is depending on a debconf newer than
that in TESTING. But the latest debconf failed to install, leaving
my system broken.
I was able to back up to stable debconf and reinstall the older
mysql-server.
This is not an experiment I like to repeat.
And the system did actually work with the changes I make. At least
worked enough for an evaluation regarding how and then to upgrade.
We are also looking at TUTOS, since we are presently using RT for
support, sales, projects and as an bank for ideas abut future
projects. Tutos is here: http://www.tutos.org/
But we would like to have the system in modules, so it can be
integrated with separate databases for various things.
I think I run both: