No! These build tests start their own private mysqld as the user running the build step, not as mysql.
Further, that mysqld needs to be able to write to the directory during these tests, so the readonly restriction would prevent that. To be fair, if they build-depend on mysql-server-core, and not mysql- server, then the apparmor profile won't get loaded on cleanroom builds, and so there is no need for any of this. But its fairly simply to rebase mysqld and get it to run outside the apparmor profile for private build tests. Here is my proposed fix for the PHP issue for instance: https://code.edge.launchpad.net/~clint-fewbar/ubuntu/maverick/php5/fix- mysql-tests-apparmor/+merge/35562 -- MySQL must not use /tmp https://bugs.launchpad.net/bugs/375371 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
