drizzle-plugin-mysql-client conflicts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Drizzle |
Invalid
|
Undecided
|
Monty Taylor | ||
7.0 |
Invalid
|
Undecided
|
Monty Taylor |
Bug Description
After the recent DEB updates, I noticed that drizzle-
root@mcp:~# apt-get install drizzle-
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
mysql-server mysql-server-5.1
The following NEW packages will be installed:
drizzle-
0 upgraded, 1 newly installed, 2 to remove and 0 not upgraded.
Need to get 355kB of archives.
After this operation, 15.4MB disk space will be freed.
Do you want to continue [Y/n]? n
Abort.
I kinda need MySQL though on the server as I will need MySQL to migrate things over. I'm not sure exactly why there is a conflict here though?
I believe this is intentional. You don't need mysql protocol plugin to migrate stuff as there is the drizzle protocol plugin. All the mysql protocol plugin does is make drizzle listen on port 3306, so the conflict would be intentional as there would be a port conflict out-of-the-box. Port 4427 still understands the MySQL protocol and all drizzle clients now use that.
What I am basically saying is you probably don't need drizzle- plugin- mysql-protocol.
I will assign to mtaylor anyway to confirm what I said above.