-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi again Sean!
I've been looking very carefully at dbconfig-common code during this last days, and I conclude that, although I didn't consider the DB client stuff, the validation($dbc_db_installed_cmd || dbc_missing_db_package_error), as it is there, needs to be patched with the lines I send first. This is because the block just asks for DB server binary, which just could meet the condition of being required when using unix socket as communication channel. As you mention, something needs to check for DB client binary, thats correct, so does _dbc_sanity_check() (line 46 from [1]) This doesn't apply to the version which is currently on Etch, because the DB server checking stuff was added on a newer release[2] Thanks for your time, Dererk ps: I attach a trace from both, [1] a Etch-released and [2] a latest dbconfig-common release, right there you can see when [2] asks for 'dbc_mysql_db_installed' fuction (which performs a mysqld binary check) even though specified a remote db server IP (that ip isn't local). ([1] is just as a control output) - -- [EMAIL PROTECTED]: ~$ grep -ir 'power in your hands' /proc/ /proc/version: Debian GNUine Perception BOFH excuse #295: The Token fell out of the ring. Call us when you find it.. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHPeibzqYvwbbBjiQRAuheAJ0XxpmJWXp2ncZdaP8cu4jrFiDIugCcC8Yn iClsdS3bYUP25AlFHgDQpVs= =/Fm0 -----END PGP SIGNATURE-----
dbconfig-common.etch.output.gz
Description: GNU Zip compressed data
dbconfig-common.latest.output.gz
Description: GNU Zip compressed data
