1) mysql-updates That's probably means kdepim must depend on a certain mysqld version and include conversion scripts when needed.
2) settings The default settings are of course perfect for hardy for the default use case. We are talking about a specialised set up for storing pim data, which can and probably already is using special settings to optimize that. 3) rootaccess Indeed the default install does not need a password for this. But that means you a) are storing private data system wide, which of course can be shielded, bus it wrong by design imho and b) the default no-password can be changed by the user and so requiring manual intervention by the user to setup Akonadi, which is currently not needed. Last point: It is not a matter of 'if' upstream will do it like this, it simply is done this way by upstream. 'We' need to deal with it. Another option is to add a conflict on apparmor, which would suck more. -- akonadi does not work with the apparmor rules introduced for /usr/sbin/mysqld on hardy. https://bugs.launchpad.net/bugs/197476 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
