mysql-client is broken

[antmat]

It seems that mysql-client metapackage is broken. because it depends on mysql-client-5.1 in squeeze and mysql-cluster-server-sql depends not on mysql-client, but on mysql-client-cluster-7.2. So mysql-client-cluster-7.2 and mysql-client-5.1 are being installing simultaneously. It leads to conflict in dpkg. So I suggest either uncommenting mysql-client package in your packaging or making all your components depend not on mysql-client-cluster-7.2, but on mysql-client package. The first one is preferable in my opinion. Sorry for my english, Cheers! Anton Matveenko

[SteveAyre]

Can you retest with the latest version?

I found some conflicts between mysql-client-5.1 and a couple of the server packages (which are now fixed) which came from partly basing the package layouts originally on the mysql server 5.5 packages from sid where some files previously in the client package are in other packages now. I'm guessing the 5.5 package wouldn't have the same issue because it replaces 5.1, so they might need to be on different packages in squeeze vs wheezy. The files specifically were perror and my_print_defaults and their manpages.

Providing the mysql-client package is probably not an option - if this is to be put in the official repositories alongside mysql-server 5.1/5.5 then that'd mean 2 different source packages providing the same binary package which I want to avoid.

None of the cluster packages depend on mysql-client-cluster-7.2 directly, they all depend on mysql-client. I've got mysql-client-5.1 installed fine now on my squeeze box alongside the cluster packages so not seeing a conflict here any longer- let me know if you still do.

[antmat]

Ok, I'll test it when I have some time.

[SteveAyre]

Ok, there still seems to be an issue but there is a workaround.

Setting up mysql-cluster-client-7.2 (7.2.5-0.2) ... dpkg: dependency problems prevent configuration of mysql-cluster-server-sql-7.2: mysql-cluster-server-sql-7.2 depends on mysql-client; however: Package mysql-client is not installed.

Installing mysql-cluster-client-7.2 replaces mysql-client-5.1 and mysql-client so they get uninstalled. However mysql-cluster-server-sql-7.2 depends on mysql-client. mysql-cluster-client-7.2 does provides mysql-client as a virtual package, but it seems that isn't enough to satisfy dpkg.

The simple workaround for now would be to install mysql-client and mysql-client-5.1, and not to use mysql-cluster-client-7.2. AFAIK the 5.1 client should work fine with 7.2.

[SteveAyre]

"mysql-cluster-server-sql depends not on mysql-client, but on mysql-client-cluster-7.2"

I think I see the confusion there. mysql-cluster-server-sql-7.2 depends on both mysql-cluster-client-7.2 and mysql-client. The first is the NDB cluster client files only (eg ndb_mgm) and the latter is the mysql client files only (eg mysql). The first has to come from cluster and complements mysql-client, any mysql-client (eg from 5.1, 5.5 or 7.2) can be used for now. That's intentional, and not the cause of the conflict. (well the mysql-client part is, but not the mysql-cluster-client-7.2).

To clarify there are 2 client packages from 7.2 with fairly similar names: mysql-cluster-client-7.2 -- NDB client programs mysql-client-cluster-7.2 -- cluster variant of mysql-client

(mysql-client-cluster-7.2 is not named mysql-client-7.2 to avoid any conflict in future with mysql server if/when it reaches a 7.2 version)

For now install the 1st but not the 2nd, use mysql-client-5.1 instead of the latter.

[SteveAyre]

The dependancy issue above is solved by 7.2.5-0.3

mysql-cluster-server-sql-7.2 is now happy with either mysql-client-cluster-7.2 or mysql-client-5.1