[Dbconfig-common-devel] Re: Bug#398525: simba: postinst fails: No mysql client to execute. (have you installed mysql-client?

[Lucas Nussbaum]

On 14/11/06 at 13:25 +0200, Radu Spineanu wrote:
> Hello Lucas,
> 
> There was a missing dependency on virtual-mysql-client.
> When trying to run piuparts on the fixed package i encountered this error:
> 
> [..]
>   Setting up simba (0.8.4-2) ...
>   dbconfig-common: writing config to /etc/dbconfig-common/simba.conf
> 
>   Creating config file /etc/dbconfig-common/simba.conf with new version
> 
>   Creating config file /etc/simba/simba-db.cfg with new version
>   error encountered creating user:
>   ERROR 2002 (HY000): Can't connect to local MySQL server through socket
> '/var/run/mysqld/mysqld.sock' (2)
>   dbconfig-common: simba configure: aborted.
>   dbconfig-common: flushing administrative password
>   dpkg: error processing simba (--configure):
>    subprocess post-installation script returned error exit status 1
>   Errors were encountered while processing:
>    simba
>   E: Sub-process /usr/bin/dpkg returned an error code (1)
> [..]
> 
> I tried to reproduce it with cacti and i found the same problem again.
> 
> Since both cacti and simba are using dbconfig-common a proper fix should
> be applied there.
> 
> A possible solution would be to modify the "Configure database with
> dbconfig-common?" template to have a false default value.

Yeah, but still, that's a "normal" failure with piuparts, since it's
using the noninteractive debconf frontend. Not much can be done against
it.
-- 
| Lucas Nussbaum
| lucas at lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas at nussbaum.fr             GPG: 1024D/023B3F4F |