unable to reinstall mysql-server

[Nico D.]

ubuntu 13.04
after automatic update to mysql 5.5 (i think) this morning, mysql refuses to start : conflict with apparmor profile.

I try to completly remove mysql :
sudo apt-get purge mysql-server-5.1 mysql-server-5.5 mysql-common mysql-server

then reinstall it:
sudo apt-get install mysql-server

Error :
"mysql-server dépend de mysql-server-5.5 ; cependant :
Le paquet mysql-server-5.5 n'est pas encore configuré."

(mysql-server depends on mysql-server-5.5 ; however mysql-server-5.5 is not configured)

same error with sudo apt-get install mysql-server-5.5

ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: mysql-server-5.5 5.5.32-0ubuntu0.13.04.2
ProcVersionSignature: Ubuntu 3.8.0-28.41-generic 3.8.13.5
Uname: Linux 3.8.0-28-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.3
AptOrdering:
 mysql-server-5.5: Configure
 mysql-server: Configure
Architecture: amd64
Date: Fri Aug 9 10:47:49 2013
ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Logs.var.log.daemon.log:

MarkForUpload: True
MySQLConf.etc.mysql.conf.d.mysqld.safe.syslog.cnf:
 [mysqld_safe]
 syslog
ProcCmdline: BOOT_IMAGE=/vmlinuz-3.8.0-28-generic root=/dev/mapper/ubuntu-root ro quiet splash vt.handoff=7
SourcePackage: mysql-5.5
Title: package mysql-server-5.5 5.5.32-0ubuntu0.13.04.2 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Nico D. (nicolas-dorigny)]

i finally solved my problem :

apt-get clean, autoclean, purge mysql*

stop apparmor

install mysql-server

start apparmor

everyting is ok now, after reboot it's still working, apparmor doesnt' complain

[Bryan Quigley (bryanquigley)]

Thank you for reporting this bug to Ubuntu. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.

This bug is for a very old release and as a packaging bug it will not affect a newer release in the same way.

Glad you got it to work!