Public bug reported:

Binary package hint: acidbase

Here is the info I captured:
A package failed to install.  Trying to recover:
Setting up acidbase (1.3.9-2) ...
dbconfig-common: writing config to /etc/dbconfig-common/acidbase.conf
*** WARNING: ucf was run from a maintainer script that uses debconf, but
             the script did not pass --debconf-ok to ucf. The maintainer
             script should be fixed to not stop debconf before calling ucf,
             and pass it this parameter. For now, ucf will revert to using
             old-style, non-debconf prompting. Ugh!

             Please inform the package maintainer about this problem.
Replacing config file /etc/acidbase/database.php with new version
ERROR 2002 (HY000): Can't connect to local MySQL server through socket 
'/var/run/mysqld/mysqld.sock' (2).
unable to connect to mysql server.
error encountered creating user:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket 
'/var/run/mysqld/mysqld.sock' (2)
dbconfig-common: acidbase configure: aborted.
dbconfig-common: flushing administrative password
dpkg: error processing acidbase (--configure):
 subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
 acidbase

ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 9.04
ErrorMessage: subprocess post-installation script returned error exit status 1
Package: acidbase 1.3.9-2
PackageArchitecture: all
SourcePackage: acidbase
Title: package acidbase 1.3.9-2 failed to install/upgrade: subprocess 
post-installation script returned error exit status 1
Uname: Linux 2.6.28-11-generic i686

** Affects: acidbase (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: apport-package i386

-- 
acidbase failed to install
https://bugs.launchpad.net/bugs/388805
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to