Package: libdbd-mysql
Version: 0.8.3-1-1
Severity: grave
File: /usr/lib/dbd/libdbdmysql.so

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi

it looks like libdbd-* packages are built agains on libdbi and they fail to
load with current one:

/usr/lib/dbd/libdbdmysql.so: undefined symbol: _dbd_parse_datetime
libdbi: Failed to load driver: /usr/lib/dbd/libdbdmysql.so
/usr/lib/dbd/libdbdsqlite.so: undefined symbol: _dbd_parse_datetime
libdbi: Failed to load driver: /usr/lib/dbd/libdbdsqlite.so
/usr/lib/dbd/libdbdfreetds.so: undefined symbol: _dbd_parse_datetime
libdbi: Failed to load driver: /usr/lib/dbd/libdbdfreetds.so
/usr/lib/dbd/libdbdsqlite3.so: undefined symbol: _dbd_parse_datetime
libdbi: Failed to load driver: /usr/lib/dbd/libdbdsqlite3.so
/usr/lib/dbd/libdbdpgsql.so: undefined symbol: _dbd_parse_datetime
libdbi: Failed to load driver: /usr/lib/dbd/libdbdpgsql.so

I guess there should be stricter dependency between the drivers and libdbi to
avoid these kind of problems.

- -- 
        Michal Čihař | http://cihar.com | http://blog.cihar.com

- -- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.31.12-0.2-default (SMP w/2 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libdbd-mysql depends on:
ii  libc6                         2.11.2-2   Embedded GNU C Library: Shared lib
ii  libdbi0                       0.8.3-1    DB Independent Abstraction Layer f
ii  libmysqlclient16              5.1.49-1   MySQL database client library

libdbd-mysql recommends no packages.

libdbd-mysql suggests no packages.

- -- no debconf information

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkx3fckACgkQ3DVS6DbnVgSPNACg+P2r6evTjwXX+8aSxR2xT0L0
eu4AoLigqR82AmeJn+5R6AeJYPQPL8Ii
=NPym
-----END PGP SIGNATURE-----



--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to