package mysql-server 5.0.51a-3ubuntu5 failed to install/upgrade: dependency problems - leaving unconfigured
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
Expired
|
Undecided
|
Unassigned |
Bug Description
using a Dell Inspiron 10 with Ubuntu 8.04 pre-installed
I successfully installed php5 and apache2 with no errors.
I *almost* get MySQL installed, but it fails near the end with INITOUTPUT undefined.
Can this be fixed??
David Jones
<email address hidden>
root@djones:
mysql-server:
Installed: 5.0.51a-3ubuntu5
Candidate: 5.0.51a-3ubuntu5
Version table:
*** 5.0.51a-3ubuntu5 0
500 http://
100 /var/lib/
root@djones:
Reading package lists... Done
Building dependency tree
Reading state information... Done
mysql-server is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Setting up mysql-server-5.0 (5.0.51a-3ubuntu5) ...
/etc/lsb-
invoke-rc.d: initscript mysql, action "stop" failed.
/etc/lsb-
invoke-rc.d: initscript mysql, action "start" failed.
dpkg: error processing mysql-server-5.0 (--configure):
subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of mysql-server:
mysql-server depends on mysql-server-5.0; however:
Package mysql-server-5.0 is not configured yet.
dpkg: error processing mysql-server (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
mysql-server-5.0
mysql-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Package
Architecture: lpia
Date: Sat Jan 1 10:31:31 2011
DistroRelease: Ubuntu 8.04
ErrorMessage: dependency problems - leaving unconfigured
NonfreeKernelMo
Package: mysql-server 5.0.51a-3ubuntu5
PackageArchitec
SourcePackage: mysql-dfsg-5.0
Title: package mysql-server 5.0.51a-3ubuntu5 failed to install/upgrade: dependency problems - leaving unconfigured
Uname: Linux 2.6.24-24-lpia i686
I dont think this is a mysql bug.
chuck