Comment 5 for bug 67696

As this is a dist-upgrade, both mysql-server and mythtv-database are upgraded at the same time.

From term.log:
Preparing to replace mysql-server-5.0 5.0.22-0ubuntu6.06.2 (using .../mysql-server-5.0_5.0.24a-9_amd64.deb) ...
Stopping MySQL database server: mysqld
Stopping MySQL database server: mysqld.
Stopping MySQL database server: mysqld
Unpacking replacement mysql-server-5.0 ...
Preparing to replace mythtv-database 0.18.1-5ubuntu3 (using .../mythtv-database_0.20-0.2ubuntu2_all.deb) ...
Unpacking replacement mythtv-database ...
...
Setting up mythtv-database (0.20-0.2ubuntu2) ...
dpkg: error processing mythtv-database (--configure):
...
Setting up mysql-server-5.0 (5.0.24a-9) ...
 * Stopping MySQL database server mysqld
 * Stopping MySQL database server mysqld [ ok ]
 * Starting MySQL database server mysqld
 * Starting MySQL database server mysqld [ ok ]

So the problem is the order in which the two packages are set up.
As mythtv-database does not depend on mysql-server, apt/dpkg sees no reason to set up mysql-server first.

Basically, this change doesn't work:

mythtv (0.20-0.0) unstable; urgency=low
...
  * mythtv-database should depends on mysql-client instead of mysql-server.
 -- Christian Marillat <email address hidden> Tue, 12 Sep 2006 08:46:02 +0200

From the last two lines of term.log you can see that mythtv-database did actually install in the end:
Setting up mythtv-database (0.20-0.2ubuntu2) ...
Setting up mythtv (0.20-0.2ubuntu2) ...