** Attachment removed: VarLogDistupgradeSystemstatetargz.gz
https://bugs.launchpad.net/bugs/597587/+attachment/1433791/+files/VarLogDistupgradeSystemstatetargz.gz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in
[Expired for mysql-dfsg-5.1 (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: mysql-dfsg-5.1 (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu.
Did you have mysql configured and working before, and not change the
configuration?
yes
If so, had you customized apparmor?
no
If so then I believe you'll need to re-apply your apparmor profile changes.
There is only /etc/apparmor.d/usr.sbin.mysqld which looks quite default
It looks to me
It looks to me like you have mysql db installed under /home/mysql
yes, you are right. Shame on me.
--
debconf does not show dialog
https://bugs.launchpad.net/bugs/597587
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in
i added the path to usr.sbin.mysqld with w option. The upgrade process still
hangs until I kill
/usr/bin/perl -w /usr/share/debconf/frontend
/var/lib/dpkg/info/mysql-server-5.1.prerm upgrade 5.1.41-3ubuntu12.3 TWICE..
--
debconf does not show dialog
https://bugs.launchpad.net/bugs/597587
You
added it like this:
/home/mysql/ rw,
--
debconf does not show dialog
https://bugs.launchpad.net/bugs/597587
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu.
--
Ubuntu-server-bugs mailing list
** Attachment added: .etc.apparmor.d.usr.sbin.mysqld.txt
http://launchpadlibrarian.net/50787779/.etc.apparmor.d.usr.sbin.mysqld.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/50787780/Dependencies.txt
** Attachment added: Logs.var.log.daemon.log.txt
Did you have mysql configured and working before, and not change the
configuration? If
so, had you customized apparmor? If so then I believe you'll need to re-apply
your apparmor
profile changes.
It looks to me like you have mysql db installed under /home/mysql, and apparmor
is refusing
