Source: libdbi-drivers Version: 0.8.3-1+s-4 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120524 qa-ftbfs Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory `/«BUILDDIR»/libdbi-drivers-0.8.3-1+s/tests' > x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include -g > -DDBI_DRIVER_DIR=\"/usr/lib/dbd\" -MT test_dbi.o -MD -MP -MF > .deps/test_dbi.Tpo -c -o test_dbi.o test_dbi.c > test_dbi.c: In function 'test_insert_row': > test_dbi.c:1077:3: warning: 'dbi_driver_quote_string_copy' is deprecated > (declared at /usr/include/dbi/dbi.h:171) [-Wdeprecated-declarations] > test_dbi.c: In function 'test_retrieve_data': > test_dbi.c:1478:5: warning: 'dbi_result_get_long' is deprecated (declared at > /usr/include/dbi/dbi.h:265) [-Wdeprecated-declarations] > test_dbi.c:1484:5: warning: 'dbi_result_get_ulong' is deprecated (declared at > /usr/include/dbi/dbi.h:266) [-Wdeprecated-declarations] > mv -f .deps/test_dbi.Tpo .deps/test_dbi.Po > /bin/bash ../libtool --tag=CC --mode=link x86_64-linux-gnu-gcc -g > -DDBI_DRIVER_DIR=\"/usr/lib/dbd\" -o test_dbi test_dbi.o -L/usr/lib -lm > -ldbi > libtool: link: x86_64-linux-gnu-gcc -g -DDBI_DRIVER_DIR=\"/usr/lib/dbd\" -o > test_dbi test_dbi.o -L/usr/lib -lm /usr/lib/libdbi.so > make[1]: Leaving directory `/«BUILDDIR»/libdbi-drivers-0.8.3-1+s/tests' > # Testing sqlite and sqlite3 > mkdir -p /«BUILDDIR»/libdbi-drivers-0.8.3-1+s/debian/sqlite3tests > ( echo ./drivers/sqlite3/.libs; \ > echo sqlite3; \ > echo /«BUILDDIR»/libdbi-drivers-0.8.3-1+s/debian/sqlite3tests; \ > echo libdbitest; ) | ./tests/test_dbi > > libdbi-drivers test program: $Id: test_dbi.c,v 1.46 2008/02/06 16:22:44 > mhoenicka Exp $ > Library version: libdbi v0.8.4 > > libdbi driver directory? [/usr/lib/dbd] 1 drivers available: sqlite3 > test which driver? database directory? [.] database name? [libdbitest] > libdbi: [query] CREATE TABLE test_datatypes ( the_char CHAR,the_uchar > CHAR,the_short SMALLINT,the_ushort SMALLINT,the_long INT,the_ulong > INT,the_longlong BIGINT,the_ulonglong BIGINT,the_float FLOAT4,the_double > FLOAT8,the_driver_string VARCHAR(255),the_conn_quoted_string > VARCHAR(255),the_conn_quoted_string_copy VARCHAR(255),the_conn_escaped_string > VARCHAR(255),the_conn_escaped_string_copy VARCHAR(255),the_empty_string > VARCHAR(255),the_null_string VARCHAR(255),the_binary_quoted_string > BLOB,the_binary_escaped_string BLOB,the_datetime DATETIME,the_datetime_tz > DATETIME,the_date DATE,the_time TIME,the_time_tz TIME,id INTEGER AUTO > INCREMENT) > libdbi: [query] INSERT INTO test_datatypes > (the_char,the_uchar,the_short,the_ushort,the_long,the_ulong,the_longlong,the_ulonglong,the_float,the_double,the_driver_string,the_conn_quoted_string,the_conn_quoted_string_copy,the_conn_escaped_string,the_conn_escaped_string_copy,the_empty_string,the_null_string,the_binary_quoted_string,the_binary_escaped_string,the_datetime,the_datetime_tz,the_date,the_time,the_time_tz) > VALUES > (-127,127,-32768,32767,-2147483648,2147483647,-9223372036854775807,9223372036854775807,3.402823466E+38,1.7976931348623157E+307,'Can > ''we'' "quote" this properly?','Can ''we'' "quote" this properly?','Can > ''we'' "quote" this properly?','Can ''we'' "escape" this properly?','Can > ''we'' "escape" this properly?','',NULL,'@A�B&C','@A�B&C','2001-12-31 > 23:59:59','2001-12-31 23:59:59 > -10:00','2001-12-31','23:59:59','23:59:59-10:00') > libdbi: [query] SELECT * from test_datatypes > libdbi: [query] DROP TABLE test_datatypes > libdbi: [query] 1 SYNTAX ERROR > libdbi: [query] 2 SYNTAX ERROR > libdbi: [query] SELECT 0 > > Driver information: > ------------------- > Name: sqlite3 > Filename: ./drivers/sqlite3/.libs/libdbdsqlite3.so > Desc: SQLite3 database support (using libsqlite3) > Maintainer: Markus Hoenicka <mhoeni...@users.sourceforge.net> > URL: http://libdbi-drivers.sourceforge.net > Version: dbd_sqlite3 v0.8.3-1 > Compiled: May 23 2012 > > Successfully connected! > Using database engine version 3071201 (numeric) and 3.7.12.1 (string) > > Test 1: List databases: > Got result, try to access rows > > Test 2: Create database libdbitest using default encoding: > This is a no-op with the sqlite/msql/firebird/ingres drivers. > > Test 3: Select database: > Ok. > > Test 4: Get encoding: > The database encoding appears to be: UTF-8 > > Test 5: Create table: > Ok. > > Test 6: List tables: > Got result, try to access rows > test_datatypes > Test 7: Insert row: > Ok. > Length of quoted binary: 9 > Last ID: 1, next ID 0 > > Test 8: Retrieve data: > Got result, try to access rows > this should cause a column type mismatch... > type mismatch errflag=-7: The requested variable type does not match what > libdbi thinks it should be > this should cause a bad name error... > bad name errflag=-5: An invalid name was passed to libdbi > the_char: in:-127 out:-127<< > the_uchar: in:127 out:127<< > the_short: in:-32768 out:-32768<< > the_ushort: in:32767 out:32767<< > the_long: in:-2147483648 out:-2147483648<< > the_ulong: in:2147483647 out:2147483647<< > the_longlong: in:-9223372036854775807 out:-9223372036854775807<< > the_ulonglong: in:9223372036854775807 out:9223372036854775807<< > the_float: in:3.402823466E+38 out:3.402823e+38<< > the_double: in:1.7976931348623157E+307 out:1.797693e+307<< > the_driver_string: in:'Can 'we' "quote" this properly?' out:'Can 'we' "quote" > this properly?'<< > the_quoted_string: in:'Can 'we' "quote" this properly?' out:'Can 'we' "quote" > this properly?'<< > the_quoted_string_copy: in:'Can 'we' "quote" this properly?' out:'Can 'we' > "quote" this properly?'<< > the_escaped_string: in:'Can 'we' "escape" this properly?' out:'Can 'we' > "escape" this properly?'<< > the_escaped_string_copy: in:'Can 'we' "escape" this properly?' out:'Can 'we' > "escape" this properly?'<< > the_empty_string: out:''<< > the_null_string: out:'(null)' > the_datetime: in:'2001-12-31 23:59:59' out:2001-12-31 23:59:59 > the_datetime_tz: in:'2001-12-31 23:59:59 -10:00' out:2002-1-1 9:59:59 > the_date: in:'2001-12-31' out:2001-12-31 > the_time: in:'23:59:59' out:23:59:59 > the_time_tz: in:'23:59:59-10:00' out:9:59:59 > the_quoted_binary: in: 65-66-0-67-39-68- out: 65-66-0-67-39-68-<< > the_escaped_binary_copy: in: 65-66-0-67-39-68- out: 65-66-0-67-39-68-<< > > > field lengths: > the_driver_string_length 31 > the_quoted_string_length 31 > the_empty_string_length 0 > the_null_string_length 0 > the_quoted_binary_length 6 > the_escaped_binary_length 6 > > > Test 9: Drop table: > Ok. > > Test 10: Drop database: > ...hang on a second... > Ok. > > Test 11: Character encoding conversion: > IANA encoding UTF-8 is known to the engine as UTF-8 > > Test 12: Error message handling: > This is supposed to fail... > Heck! The error number is 1; the message reads: 1: near "1": syntax > error > This is supposed to fail... > Heck! The error number is 1; the message reads: 1: near "2": syntax > error > This is supposed to succeed... > Ok. The error number is 0; the message reads: > > > SUCCESS! All done, disconnecting and shutting down libdbi. Have a nice day. > > rm -rf /«BUILDDIR»/libdbi-drivers-0.8.3-1+s/debian/sqlite3tests > mkdir -p /«BUILDDIR»/libdbi-drivers-0.8.3-1+s/debian/sqlitetests > ( echo ./drivers/sqlite/.libs; \ > echo sqlite; \ > echo /«BUILDDIR»/libdbi-drivers-0.8.3-1+s/debian/sqlitetests; \ > echo libdbitest; ) | ./tests/test_dbi > > libdbi-drivers test program: $Id: test_dbi.c,v 1.46 2008/02/06 16:22:44 > mhoenicka Exp $ > Library version: libdbi v0.8.4 > > libdbi driver directory? [/usr/lib/dbd] 1 drivers available: sqlite > test which driver? database directory? [.] database name? [libdbitest] > libdbi: [query] CREATE TABLE test_datatypes ( the_char CHAR,the_uchar > CHAR,the_short SMALLINT,the_ushort SMALLINT,the_long INT,the_ulong > INT,the_longlong BIGINT,the_ulonglong BIGINT,the_float FLOAT4,the_double > FLOAT8,the_driver_string VARCHAR(255),the_conn_quoted_string > VARCHAR(255),the_conn_quoted_string_copy VARCHAR(255),the_conn_escaped_string > VARCHAR(255),the_conn_escaped_string_copy VARCHAR(255),the_empty_string > VARCHAR(255),the_null_string VARCHAR(255),the_binary_quoted_string > BLOB,the_binary_escaped_string BLOB,the_datetime DATETIME,the_datetime_tz > DATETIME,the_date DATE,the_time TIME,the_time_tz TIME,id INTEGER AUTO > INCREMENT) > libdbi: [query] INSERT INTO test_datatypes > (the_char,the_uchar,the_short,the_ushort,the_long,the_ulong,the_longlong,the_ulonglong,the_float,the_double,the_driver_string,the_conn_quoted_string,the_conn_quoted_string_copy,the_conn_escaped_string,the_conn_escaped_string_copy,the_empty_string,the_null_string,the_binary_quoted_string,the_binary_escaped_string,the_datetime,the_datetime_tz,the_date,the_time,the_time_tz) > VALUES > (-127,127,-32768,32767,-2147483648,2147483647,-9223372036854775807,9223372036854775807,3.402823466E+38,1.7976931348623157E+307,'Can > ''we'' "quote" this properly?','Can ''we'' "quote" this properly?','Can > ''we'' "quote" this properly?','Can ''we'' "escape" this properly?','Can > ''we'' "escape" this properly?','',NULL,'@A�B&C','@A�B&C','2001-12-31 > 23:59:59','2001-12-31 23:59:59 > -10:00','2001-12-31','23:59:59','23:59:59-10:00') > libdbi: [query] SELECT * from test_datatypes > libdbi: [query] DROP TABLE test_datatypes > libdbi: [query] 1 SYNTAX ERROR > libdbi: [query] 2 SYNTAX ERROR > libdbi: [query] SELECT 0 > > Driver information: > ------------------- > Name: sqlite > Filename: ./drivers/sqlite/.libs/libdbdsqlite.so > Desc: SQLite database support (using libsqlite) > Maintainer: Markus Hoenicka <mhoeni...@users.sourceforge.net> > URL: http://libdbi-drivers.sourceforge.net > Version: dbd_sqlite v0.8.3-1 > Compiled: May 23 2012 > > Successfully connected! > Using database engine version 20817 (numeric) and 2.8.17 (string) > > Test 1: List databases: > Got result, try to access rows > > Test 2: Create database libdbitest using default encoding: > This is a no-op with the sqlite/msql/firebird/ingres drivers. > > Test 3: Select database: > Ok. > > Test 4: Get encoding: > The database encoding appears to be: UTF-8 > > Test 5: Create table: > Ok. > > Test 6: List tables: > Got result, try to access rows > test_datatypes > Test 7: Insert row: > Ok. > Length of quoted binary: 9 > Last ID: 1, next ID 0 > > Test 8: Retrieve data: > Got result, try to access rows > this should cause a column type mismatch... > type mismatch errflag=-7: The requested variable type does not match what > libdbi thinks it should be > this should cause a bad name error... > bad name errflag=-5: An invalid name was passed to libdbi > the_char: in:-127 out:-127<< > the_uchar: in:127 out:127<< > the_short: in:-32768 out:-32768<< > the_ushort: in:32767 out:32767<< > the_long: in:-2147483648 out:-2147483648<< > the_ulong: in:2147483647 out:2147483647<< > the_longlong: in:-9223372036854775807 out:-9223372036854775807<< > the_ulonglong: in:9223372036854775807 out:9223372036854775807<< > the_float: in:3.402823466E+38 out:3.402823e+38<< > the_double: in:1.7976931348623157E+307 out:1.797693e+307<< > the_driver_string: in:'Can 'we' "quote" this properly?' out:'Can 'we' "quote" > this properly?'<< > the_quoted_string: in:'Can 'we' "quote" this properly?' out:'Can 'we' "quote" > this properly?'<< > the_quoted_string_copy: in:'Can 'we' "quote" this properly?' out:'Can 'we' > "quote" this properly?'<< > the_escaped_string: in:'Can 'we' "escape" this properly?' out:'Can 'we' > "escape" this properly?'<< > the_escaped_string_copy: in:'Can 'we' "escape" this properly?' out:'Can 'we' > "escape" this properly?'<< > the_empty_string: out:''<< > the_null_string: out:'(null)' > the_datetime: in:'2001-12-31 23:59:59' out:2001-12-31 23:59:59 > the_datetime_tz: in:'2001-12-31 23:59:59 -10:00' out:2002-1-1 9:59:59 > the_date: in:'2001-12-31' out:2001-12-31 > the_time: in:'23:59:59' out:23:59:59 > the_time_tz: in:'23:59:59-10:00' out:9:59:59 > the_quoted_binary: in: 65-66-0-67-39-68- out: 65-66-0-67-39-68-<< > the_escaped_binary_copy: in: 65-66-0-67-39-68- out: 65-66-0-67-39-68-<< > > > field lengths: > the_driver_string_length 31 > the_quoted_string_length 31 > the_empty_string_length 0 > the_null_string_length 0 > the_quoted_binary_length 6 > the_escaped_binary_length 6 > > > Test 9: Drop table: > Ok. > > Test 10: Drop database: > ...hang on a second... > Ok. > > Test 11: Character encoding conversion: > IANA encoding UTF-8 is known to the engine as UTF-8 > > Test 12: Error message handling: > This is supposed to fail... > Heck! The error number is 1; the message reads: 1: near "1": syntax > error > This is supposed to fail... > Heck! The error number is 1; the message reads: 1: near "2": syntax > error > This is supposed to succeed... > Ok. The error number is 0; the message reads: > > > SUCCESS! All done, disconnecting and shutting down libdbi. Have a nice day. > > rm -rf /«BUILDDIR»/libdbi-drivers-0.8.3-1+s/debian/sqlitetests > # Testing MySQL and Postgress > chmod +x ./debian/test_mysql.sh ./debian/test_pgsql.sh > ./debian/test_mysql.sh > Installing MySQL system tables... > OK > Filling help tables... > OK > > To start mysqld at boot time you have to copy > support-files/mysql.server to the right place for your system > > PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER ! > To do so, start the server, then issue the following commands: > > /usr/bin/mysqladmin -u root password 'new-password' > /usr/bin/mysqladmin -u root -h password 'new-password' > > Alternatively you can run: > /usr/bin/mysql_secure_installation > > which will also give you the option of removing the test > databases and anonymous user created by default. This is > strongly recommended for production servers. > > See the manual for more instructions. > > You can start the MySQL daemon with: > cd /usr ; /usr/bin/mysqld_safe & > > You can test the MySQL daemon with mysql-test-run.pl > cd /usr/mysql-test ; perl mysql-test-run.pl > > Please report any problems with the /usr/bin/mysqlbug script! > > /usr/bin/mysqladmin: connect to server at 'localhost' failed > error: 'Can't connect to local MySQL server through socket > '/tmp/tmp.s86lhvHJte/mysql.sock' (2)' > Check that mysqld is running and that the socket: > '/tmp/tmp.s86lhvHJte/mysql.sock' exists! > 120523 20:47:23 [Note] Plugin 'FEDERATED' is disabled. > 120523 20:47:23 InnoDB: The InnoDB memory heap is disabled > 120523 20:47:23 InnoDB: Mutexes and rw_locks use GCC atomic builtins > 120523 20:47:23 InnoDB: Compressed tables use zlib 1.2.7 > 120523 20:47:23 InnoDB: Using Linux native AIO > 120523 20:47:23 InnoDB: Initializing buffer pool, size = 128.0M > 120523 20:47:23 InnoDB: Completed initialization of buffer pool > InnoDB: The first specified data file ./ibdata1 did not exist: > InnoDB: a new database to be created! > 120523 20:47:23 InnoDB: Setting file ./ibdata1 size to 10 MB > InnoDB: Database physically writes the file full: wait... > 120523 20:47:23 InnoDB: Log file ./ib_logfile0 did not exist: new to be > created > InnoDB: Setting log file ./ib_logfile0 size to 5 MB > InnoDB: Database physically writes the file full: wait... > 120523 20:47:23 InnoDB: Log file ./ib_logfile1 did not exist: new to be > created > InnoDB: Setting log file ./ib_logfile1 size to 5 MB > InnoDB: Database physically writes the file full: wait... > InnoDB: Doublewrite buffer not found: creating new > InnoDB: Doublewrite buffer created > InnoDB: 127 rollback segment(s) active. > InnoDB: Creating foreign key constraint system tables > InnoDB: Foreign key constraint system tables created > 120523 20:47:23 InnoDB: Waiting for the background threads to start > 120523 20:47:24 InnoDB: 1.1.8 started; log sequence number 0 > 120523 20:47:24 [Note] /usr/sbin/mysqld: ready for connections. > Version: '5.5.23-2' socket: '/tmp/tmp.s86lhvHJte/mysql.sock' port: 0 > (Debian) > pinging mysqld.mysqld is alive > > libdbi-drivers test program: $Id: test_dbi.c,v 1.46 2008/02/06 16:22:44 > mhoenicka Exp $ > Library version: libdbi v0.8.4 > > libdbi driver directory? [/usr/lib/dbd] 1 drivers available: mysql > test which driver? > database administrator name? > database administrator password? > database hostname? [(blank for local socket if possible)] database name? > [libdbitest] libdbi: [queryf] CREATE DATABASE libdbitest > > Driver information: > ------------------- > Name: mysql > Filename: ./drivers/mysql/.libs/libdbdmysql.so > Desc: MySQL database support (using libmysqlclient) > Maintainer: Mark M. Tobenkin <m...@brentwoodradio.com> > URL: http://libdbi-drivers.sourceforge.net > Version: dbd_mysql v0.8.3-1 > Compiled: May 23 2012 > > Successfully connected! > Using database engine version 50523 (numeric) and 5.5.23-2 (string) > > Test 1: List databases: > Got result, try to access rows > information_schema mysql performance_schema test > Test 2: Create database libdbitest using default encoding: > Ok. > libdbi: [query] SHOW VARIABLES LIKE 'character_set_connection' > libdbi: [query] CREATE TABLE test_datatypes ( the_char TINYINT,the_uchar > TINYINT,the_short SMALLINT,the_ushort SMALLINT,the_long INT,the_ulong > INT,the_longlong BIGINT,the_ulonglong BIGINT,the_float FLOAT4,the_double > FLOAT8,the_driver_string VARCHAR(255),the_conn_quoted_string > VARCHAR(255),the_conn_quoted_string_copy VARCHAR(255),the_conn_escaped_string > VARCHAR(255),the_conn_escaped_string_copy VARCHAR(255),the_empty_string > VARCHAR(255),the_null_string VARCHAR(255),the_binary_quoted_string > BLOB,the_binary_escaped_string BLOB,the_datetime DATETIME,the_datetime_tz > DATETIME,the_date DATE,the_time TIME,the_time_tz TIME,id INT > AUTO_INCREMENT,PRIMARY KEY (id)) > libdbi: [query] INSERT INTO test_datatypes > (the_char,the_uchar,the_short,the_ushort,the_long,the_ulong,the_longlong,the_ulonglong,the_float,the_double,the_driver_string,the_conn_quoted_string,the_conn_quoted_string_copy,the_conn_escaped_string,the_conn_escaped_string_copy,the_empty_string,the_null_string,the_binary_quoted_string,the_binary_escaped_string,the_datetime,the_datetime_tz,the_date,the_time,the_time_tz) > VALUES > (-127,127,-32768,32767,-2147483648,2147483647,-9223372036854775807,9223372036854775807,3.402823466E+38,1.7976931348623157E+307,'Can > \'we\' \"quote\" this properly?','Can \'we\' \"quote\" this properly?','Can > \'we\' \"quote\" this properly?','Can \'we\' \"escape\" this properly?','Can > \'we\' \"escape\" this properly?','',NULL,'AB\0C\'D','AB\0C\'D','2001-12-31 > 23:59:59','2001-12-31 23:59:59 > -10:00','2001-12-31','23:59:59','23:59:59-10:00') > libdbi: [query] SELECT * from test_datatypes > libdbi: [query] DROP TABLE test_datatypes > libdbi: [queryf] DROP DATABASE libdbitest > libdbi: [query] 1 SYNTAX ERROR > libdbi: [query] 2 SYNTAX ERROR > libdbi: [query] SELECT 0 > libdbi: [queryf] CREATE DATABASE libdbitest CHARACTER SET utf8 > > Test 3: Select database: > Ok. > > Test 4: Get encoding: > The database encoding appears to be: ISO-8859-1 > > Test 5: Create table: > Ok. > > Test 6: List tables: > Got result, try to access rows > test_datatypes > Test 7: Insert row: > Ok. > Length of quoted binary: 10 > Last ID: 1, next ID 0 > > Test 8: Retrieve data: > Got result, try to access rows > this should cause a column type mismatch... > type mismatch errflag=-7: The requested variable type does not match what > libdbi thinks it should be > this should cause a bad name error... > bad name errflag=-5: An invalid name was passed to libdbi > the_datetime_tz: test skipped for this driver. > time_tz: test skipped for this driver > the_char: in:-127 out:-127<< > the_uchar: in:127 out:127<< > the_short: in:-32768 out:-32768<< > the_ushort: in:32767 out:32767<< > the_long: in:-2147483648 out:-2147483648<< > the_ulong: in:2147483647 out:2147483647<< > the_longlong: in:-9223372036854775807 out:-9223372036854775807<< > the_ulonglong: in:9223372036854775807 out:9223372036854775807<< > the_float: in:3.402823466E+38 out:3.402820e+38<< > the_double: in:1.7976931348623157E+307 out:1.797693e+307<< > the_driver_string: in:'Can 'we' "quote" this properly?' out:'Can 'we' "quote" > this properly?'<< > the_quoted_string: in:'Can 'we' "quote" this properly?' out:'Can 'we' "quote" > this properly?'<< > the_quoted_string_copy: in:'Can 'we' "quote" this properly?' out:'Can 'we' > "quote" this properly?'<< > the_escaped_string: in:'Can 'we' "escape" this properly?' out:'Can 'we' > "escape" this properly?'<< > the_escaped_string_copy: in:'Can 'we' "escape" this properly?' out:'Can 'we' > "escape" this properly?'<< > the_empty_string: out:''<< > the_null_string: out:'(null)' > the_datetime: in:'2001-12-31 23:59:59' out:2001-12-31 23:59:59 > the_datetime_tz: in:'2001-12-31 23:59:59 -10:00' out:0-0-0 0:0:0 > the_date: in:'2001-12-31' out:2001-12-31 > the_time: in:'23:59:59' out:23:59:59 > the_time_tz: in:'23:59:59-10:00' out:0:0:0 > the_quoted_binary: in: 65-66-0-67-39-68- out: 65-66-0-67-39-68-<< > the_escaped_binary_copy: in: 65-66-0-67-39-68- out: 65-66-0-67-39-68-<< > > > field lengths: > the_driver_string_length 31 > the_quoted_string_length 31 > the_empty_string_length 0 > the_null_string_length 0 > the_quoted_binary_length 6 > the_escaped_binary_length 6 > > > Test 9: Drop table: > Ok. > > Test 10: Drop database: > ...hang on a second... > Ok. > > Test 11: Character encoding conversion: > IANA encoding UTF-8 is known to the engine as utf8 > Engine encoding latin1 is known at IANA as ISO-8859-1 > > Test 12: Error message handling: > This is supposed to fail... > Heck! The error number is 1064; the message reads: 1064: You have an > error in your SQL syntax; check the manual that corresponds to your MySQL > server version for the right syntax to use near '1 SYNTAX ERROR' at line 1 > This is supposed to fail... > Heck! The error number is 1064; the message reads: 1064: You have an > error in your SQL syntax; check the manual that corresponds to your MySQL > server version for the right syntax to use near '2 SYNTAX ERROR' at line 1 > This is supposed to succeed... > Ok. The error number is 0; the message reads: > > Now run a couple of tests related to character encodings > The previous tests used the default encoding, if any. Now we try to connect > using UTF-8 and create an UTF-8 database > > Successfully connected using an UTF-8 encoding! > > Test 13: Create database libdbitest with encoding UTF-8: > Ok. > libdbi: [query] SHOW VARIABLES LIKE 'character_set_connection' > libdbi: [queryf] DROP DATABASE libdbitest > libdbi: [queryf] CREATE DATABASE libdbitest CHARACTER SET latin1 > > Test 14: Select UTF-8 database: > Ok. > > Test 15: Get encoding of UTF-8 database: > The database encoding appears to be: UTF-8 > > Test 16: Drop UTF-8 database: > ...hang on a second... > Ok. > > Now repeat this test with a ISO-8859-1 encoding > > Successfully connected using a ISO-8859-1 encoding! > > Test 17: Create database libdbitest with encoding ISO-8859-1: > Ok. > libdbi: [query] SHOW VARIABLES LIKE 'character_set_connection' > libdbi: [query] SHOW VARIABLES LIKE 'character_set_connection' > libdbi: [query] SHOW CREATE DATABASE libdbitest > libdbi: [query] SHOW CREATE DATABASE libdbitest > libdbi: [queryf] DROP DATABASE libdbitest > > Test 18: Select ISO-8859-1 database: > Ok. > > Test 19: Get encoding of ISO-8859-1 database: > The database encoding appears to be: ISO-8859-1 > > Attempt to connect to the existing ISO-8859-1 database using an UTF-8 encoding > > Successfully connected to ISO-8859-1 database using UTF-8 encoding! > > Test 20: Get encoding of ISO-8859-1 database using UTF-8 encoding: > The database encoding appears to be: UTF-8 > > Attempt to connect to the existing ISO-8859-1 database using the "auto" > encoding feature > > Successfully connected to ISO-8859-1 database using "auto" encoding! > > Test 21: Get encoding of ISO-8859-1 database using "auto" encoding: > The database encoding appears to be: ISO-8859-1 > > Test 22: Drop ISO-8859-1 database: > ...hang on a second... > Ok. > > > SUCCESS! All done, disconnecting and shutting down libdbi. Have a nice day. > > 120523 20:47:35 [Note] /usr/sbin/mysqld: Normal shutdown > > 120523 20:47:35 InnoDB: Starting shutdown... > 120523 20:47:36 InnoDB: Shutdown completed; log sequence number 1605015 > 120523 20:47:36 [Note] /usr/sbin/mysqld: Shutdown complete > > ./debian/test_pgsql.sh > The files belonging to this database system will be owned by user "user". > This user must also own the server process. > > The database cluster will be initialized with locale en_US.UTF-8. > The default database encoding has accordingly been set to UTF8. > The default text search configuration will be set to "english". > > fixing permissions on existing directory /tmp/tmp.3hfkAUZIGq ... ok > creating subdirectories ... ok > selecting default max_connections ... 100 > selecting default shared_buffers ... 24MB > creating configuration files ... ok > creating template1 database in /tmp/tmp.3hfkAUZIGq/base/1 ... ok > initializing pg_authid ... ok > initializing dependencies ... ok > creating system views ... ok > loading system objects' descriptions ... ok > creating collations ... ok > creating conversions ... ok > creating dictionaries ... ok > setting privileges on built-in objects ... ok > creating information schema ... ok > loading PL/pgSQL server-side language ... ok > vacuuming database template1 ... ok > copying template1 to template0 ... ok > > WARNING: enabling "trust" authentication for local connections > You can change this by editing pg_hba.conf or using the -A option the > next time you run initdb. > copying template1 to postgres ... ok > > Success. You can now start the database server using: > > /usr/lib/postgresql/9.1/bin/postgres -D /tmp/tmp.3hfkAUZIGq > or > /usr/lib/postgresql/9.1/bin/pg_ctl -D /tmp/tmp.3hfkAUZIGq -l logfile start > > LOG: database system was shut down at 2012-05-23 20:47:39 UTC > LOG: database system is ready to accept connections > LOG: autovacuum launcher started > Wed May 23 20:47:43 UTC 2012: retrying.. > CREATE DATABASE libdbitest; > DROP DATABASE libdbitest; > CREATE DATABASE "user"; > ALTER USER user WITH PASSWORD 'abcdefg' > ERROR: syntax error at or near "user" at character 12 > STATEMENT: ALTER USER user WITH PASSWORD 'abcdefg' > ERROR: syntax error at or near "user" > LINE 1: ALTER USER user WITH PASSWORD 'abcdefg' > ^ > make: *** [test-stamp] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/05/24/libdbi-drivers_0.8.3-1+s-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
