Bug #14593 Server won't install because of failed aaa_base dependency
Submitted: 2 Nov 2005 22:34 Modified: 10 Dec 2005 7:13
Reporter: Jeff Battisti Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Installing Severity:S2 (Serious)
Version:5.1.15 OS:Linux (SUSE Linux 9.0)
Assigned to: CPU Architecture:Any

[2 Nov 2005 22:34] Jeff Battisti
Description:
I receive the following error when attemping to install MYSQL server on SUSE 9.0.

rpm -U MySQL-server-standard-5.0.15-0.sles9.i586.rpm
warning: MySQL-client-standard-4.1.15-0.sles9.i586.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5
error: Failed dependencies:
        aaa_base is needed by MySQL-server-standard-4.1.15-0.sles9

How to repeat:
rpm -U MySQL-server-standard-5.0.15-0.sles9.i586.rpm

Suggested fix:
????
[2 Nov 2005 22:43] Jeff Battisti
Generic version works..SUSE 9.0 version fails.
[5 Nov 2005 11:06] Valeriy Kravchuk
Thank you for a problem report. Please, describe the steps you perormed in more details. You are upgrading from 4.1.15 to 5.1.15, right? Send also the results of 'rpm -qa' command (list of all packages installed).
[7 Nov 2005 18:26] Jeff Battisti
I was installing a clean install.  When I went back and installed the "generic" linux version instead of the SUSE version it worked fine.
[10 Nov 2005 7:13] Valeriy Kravchuk
OK. If you are perfroming "clean install", then what this messages are about?

"warning: MySQL-client-standard-4.1.15-0.sles9.i586.rpm: V3 DSA signature: NOKEY,
key ID 5072e1f5
error: Failed dependencies:
        aaa_base is needed by MySQL-server-standard-4.1.15-0.sles9"

For me it looks like there were 4.1.15-0.sles9 RPMs, then you are trying to update them to 5.0.15... (rpm -U).

So, please, send the list of all MySQL packages installed before your installation attempt, all the commands you performed, and all the results. Just to be sure what's happening.
[11 Dec 2005 0:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".