Linux – Cannot install MYSQL using aptitude…can anyone tell me why

aptitudeinstallationlinuxMySQLunix

It just stops and freezes after this.

 The following packages will be upgraded:
      libmysqlclient15off mysql-client mysql-client-5.0 mysql-common
    4 packages upgraded, 4 newly installed, 0 to remove and 49 not upgraded.
    Need to get 38.0MB of archives. After unpacking 91.1MB will be used.
    Do you want to continue? [Y/n/?] y
    Writing extended state information... Done
    Get:1 http://archive.ubuntu.com jaunty-updates/main mysql-common 5.1.30really5.0                                                       .75-0ubuntu10.2 [62.9kB]
    Get:2 http://archive.ubuntu.com jaunty-updates/main mysql-client 5.1.30really5.0                                                       .75-0ubuntu10.2 [55.0kB]
    Get:3 http://archive.ubuntu.com jaunty-updates/main libmysqlclient15off 5.1.30re                                                       ally5.0.75-0ubuntu10.2 [1878kB]
    Get:4 http://archive.ubuntu.com jaunty-updates/main mysql-client-5.0 5.1.30reall                                                       y5.0.75-0ubuntu10.2 [8292kB]
    Get:5 http://archive.ubuntu.com jaunty-updates/main mysql-server-core-5.0 5.1.30                                                       really5.0.75-0ubuntu10.2 [3534kB]
    Get:6 http://archive.ubuntu.com jaunty-updates/main mysql-server-5.0 5.1.30reall                                                       y5.0.75-0ubuntu10.2 [24.0MB]
    Get:7 http://archive.ubuntu.com jaunty/main libhtml-template-perl 2.9-1 [65.8kB]
    Get:8 http://archive.ubuntu.com jaunty-updates/main mysql-server 5.1.30really5.0                                                       .75-0ubuntu10.2 [57.2kB]
    Fetched 38.0MB in 3s (10.8MB/s)
    Preconfiguring packages ...
    (Reading database ... 17211 files and directories currently installed.)
    Preparing to replace mysql-common 5.1.30really5.0.75-0ubuntu10 (using .../mysql-                                                       common_5.1.30really5.0.75-0ubuntu10.2_all.deb) ...
    Unpacking replacement mysql-common ...
    Preparing to replace mysql-client 5.1.30really5.0.75-0ubuntu10 (using .../mysql-                                                       client_5.1.30really5.0.75-0ubuntu10.2_all.deb) ...
    Unpacking replacement mysql-client ...
    Preparing to replace libmysqlclient15off 5.1.30really5.0.75-0ubuntu10 (using ...                                                       /libmysqlclient15off_5.1.30really5.0.75-0ubuntu10.2_amd64.deb) ...
    Unpacking replacement libmysqlclient15off ...
    Preparing to replace mysql-client-5.0 5.1.30really5.0.75-0ubuntu10 (using .../my                                                       sql-client-5.0_5.1.30really5.0.75-0ubuntu10.2_amd64.deb) ...
    Unpacking replacement mysql-client-5.0 ...
    Selecting previously deselected package mysql-server-core-5.0.
    Unpacking mysql-server-core-5.0 (from .../mysql-server-core-5.0_5.1.30really5.0.                                                       75-0ubuntu10.2_amd64.deb) ...
    Setting up mysql-common (5.1.30really5.0.75-0ubuntu10.2) ...
    Selecting previously deselected package mysql-server-5.0.
    (Reading database ... 17290 files and directories currently installed.)
    Unpacking mysql-server-5.0 (from .../mysql-server-5.0_5.1.30really5.0.75-0ubuntu                                                       10.2_amd64.deb) ...
     * Stopping MySQL database server mysqld                                 [ OK ]
    Selecting previously deselected package libhtml-template-perl.
    Unpacking libhtml-template-perl (from .../libhtml-template-perl_2.9-1_all.deb) .                                                       ..
    Selecting previously deselected package mysql-server.
    Unpacking mysql-server (from .../mysql-server_5.1.30really5.0.75-0ubuntu10.2_all                                                       .deb) ...
     * Stopping MySQL database server mysqld                                 [ OK ]
    Setting up libmysqlclient15off (5.1.30really5.0.75-0ubuntu10.2) ...

    Setting up mysql-client-5.0 (5.1.30really5.0.75-0ubuntu10.2) ...
    Setting up mysql-client (5.1.30really5.0.75-0ubuntu10.2) ...
    Setting up mysql-server-core-5.0 (5.1.30really5.0.75-0ubuntu10.2) ...
    Setting up mysql-server-5.0 (5.1.30really5.0.75-0ubuntu10.2) ...
     * Stopping MySQL database server mysqld                                 [ OK ]
     * /etc/init.d/mysql: WARNING: /etc/mysql/my.cnf cannot be read. See README.Debi                                                       an.gz
     * Starting MySQL database server mysqld                                 [fail]
    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
    Setting up libhtml-template-perl (2.9-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
    Processing triggers for libc6 ...
    No apport report written because the error message indicates its a followup erro                                                       r from a previous failure.
                              ldconfig deferred processing now taking place
    Errors were encountered while processing:
     mysql-server-5.0
     mysql-server
    E: Sub-process /usr/bin/dpkg returned an error code (1)
    A package failed to install.  Trying to recover:
    Setting up mysql-server-5.0 (5.1.30really5.0.75-0ubuntu10.2) ...
     * Stopping MySQL database server mysqld                                 [ OK ]
     * /etc/init.d/mysql: WARNING: /etc/mysql/my.cnf cannot be read. See README.Debi                                                       an.gz
     * Starting MySQL database server mysqld                                 [ OK ]
    /etc/init.d/mysql: line 115: /etc/mysql/debian-start: No such file or directory
    invoke-rc.d: initscript mysql, action "start" failed.

Best Answer

Because when you removed the packages last time, you only removed them, not purged them, and then you deleted the config files by hand. So dpkg thinks you don't want a default config file (because you deleted it), so it doesn't install a new one, and MySQL has a cry.

Purge all mysql-related packages and try again.

Related Solutions

Debian – Running Stable and Installing Packages from Testing

Many people seem to be afraid of mixing stable with testing, but frankly, testing is fairly stable in its own right, and with proper preferences and solution checking, you can avoid the "stability drift" that puts your core packages on the unstable path.

"Testing is fairly stable??", you ask. Yes. In order for a package to migrate from unstable to testing, it has to have zero open bugs for 10 consecutive days. Chances are that, especially for the more popular packages, somebody is going to submit a bug report for an unstable version if something is wrong.

Even if you don't want to mix the environments, it's still nice to have the option there in case you run into something that requires a newer version than what is in stable.

Here's what I recommend for setting this up:

First, create the following files in /etc/apt/preferences.d:

stable.pref:

# 500 <= P < 990: causes a version to be installed unless there is a
# version available belonging to the target release or the installed
# version is more recent

Package: *
Pin: release a=stable
Pin-Priority: 900

testing.pref:

# 100 <= P < 500: causes a version to be installed unless there is a
# version available belonging to some other distribution or the installed
# version is more recent

Package: *
Pin: release a=testing
Pin-Priority: 400

unstable.pref:

# 0 < P < 100: causes a version to be installed only if there is no
# installed version of the package

Package: *
Pin: release a=unstable
Pin-Priority: 50

experimental.pref:

# 0 < P < 100: causes a version to be installed only if there is no
# installed version of the package

Package: *
Pin: release a=experimental
Pin-Priority: 1

(Don't be afraid of the unstable/experimental stuff here. The priorities are low enough that it's never going to automatically install any of that stuff. Even the testing branch will behave, as it's only going to install the packages you want to be in testing.)

Now, creating a matching set for /etc/apt/sources.list.d:

stable.list: Copy from your original /etc/apt/sources.list. Rename the old file to something like sources.list.orig.

testing.list: Same as stable.list, except with testing.

unstable.list: Same as stable.list, except with unstable, and remove the security lists.

experimental.list: Same as unstable.list, except with experimental.

You can also add a oldstable in sources.lists.d and preferences.d (use a priority of 1), though this moniker will tend to expire and disappear before the next stable cycle. In cases like that, you can use http://archive.debian.org/debian/ and "hardcode" the Debian version (etch, lenny, etc.).

To install the testing version of a package, simply use aptitude install lib-foobar-package/testing, or just jump into aptitude's GUI and select the version inside of the package details (hit enter on the package you're looking at).

If you get complaints of package conflicts, look at the solutions first. In most cases, the first one is going to be "don't install this version". Learn to use the per-package accept/reject resolver choices. For example, if you're installing foobar-package/testing, and the first solution is "don't install foobar-package/testing", then mark that choice as rejected, and the other solutions will never veer to that path again. In cases like these, you'll probably have to install a few other testing packages.

If it's getting too hairy (like it's trying to upgrade libc or the kernel or some other huge core system), then you can either reject those upgrade paths or just back out of the initial upgrade altogether. Remember that it's only going to upgrade stuff to testing/unstable if you allow it to.

EDIT: Fixed some priority pins, and updated the list.

Java – Why can’t I install Java via “sudo aptitude” in Ubuntu

Change dapper to jaunty in the last two lines, or, ensure that multiverse is enabled for one of the jaunty lines.

Best Answer

Related Solutions

Debian – Running Stable and Installing Packages from Testing

Java – Why can’t I install Java via “sudo aptitude” in Ubuntu

Related Topic