What is the correct way to install the .deb packages in Ubuntu 10.04 ?
meman
dpkg: considering removing mysql-common in favour of mysql-wsrep ...
dpkg: no, cannot proceed with removal of mysql-common (--auto-
deconfigure will help):
libmysqlclient16 depends on mysql-common (>= 5.1.41-3ubuntu12.3)
mysql-common is to be removed.
dpkg: regarding mysql-wsrep-5.1.44-0.7.4-i386.deb containing mysql-
wsrep:
mysql-wsrep conflicts with mysql-common-4.1
mysql-common provides mysql-common-4.1 and is present and installed.
dpkg: error processing mysql-wsrep-5.1.44-0.7.4-i386.deb (--install):
conflicting packages - not installing mysql-wsrep
Errors were encountered while processing:
mysql-wsrep-5.1.44-0.7.4-i386.deb
using the --auto-deconfigure somewhat breaks other mysql packages
depending on mysql-common.
How can I use the .deb package to install and avoid conflicts?
Alex Yurchenko
I have not tried it on Ubuntu 10.4 yet, but the following worked for me on
9.10:
$ sudo dpkg -r mysql-server mysql-client
$ sudo dpkg -i <mysql-wsrep DEB>
Looking at your log, they (Ubuntu MySQL maintainers) might have changed
dependencies (or they might have upgraded to MySQL 5.1) and you may need to
manually remove libmysqlclient16 (with --ignore-depends if necessary).
The problem here is that mysql-wsrep DEB package provides everything:
mysql-server, mysql-client, mysql-common and libmysqlclient16. This is
required because we need to make sure that mysqldump comes from the same
MySQL version. On older distributions they are still using MySQL 5.0 and
mysqldump from 5.0 does not cut it. Somehow dpkg fails to cope with it.
Regards,
Alex
On Mon, 5 Jul 2010 01:18:24 -0700 (PDT), meman <jon.ska...@gmail.com>
wrote:
meman
dpkg: dependency problems prevent configuration of libmysqlclient16:
libmysqlclient16 depends on mysql-common (>= 5.1.41-3ubuntu12.3);
however:
Package mysql-common is not installed.
dpkg: error processing libmysqlclient16 (--install):
dependency problems - leaving unconfigured
Processing triggers for ureadahead ...
ureadahead will be reprofiled on next reboot
Processing triggers for man-db ...
Running apt-get install - it reports an unmet dependency for mysql-
common:
The following packages have unmet dependencies:
mysql-wsrep: Conflicts: mysql-common-4.1
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or
specify a solution).
Running apt-get -f install wants to remove mysql-wsrep..
On 5 Jul, 15:35, Alex Yurchenko <alexey.yurche...@codership.com>
wrote:
>
> I have not tried it on Ubuntu 10.4 yet, but the following worked for me on
> 9.10:
>
> $ sudo dpkg -r mysql-server mysql-client
> $ sudo dpkg -i <mysql-wsrep DEB>
>
> Looking at your log, they (Ubuntu MySQL maintainers) might have changed
> dependencies (or they might have upgraded to MySQL 5.1) and you may need to
> manually remove libmysqlclient16 (with --ignore-depends if necessary).
>
> The problem here is that mysql-wsrep DEB package provides everything:
> mysql-server, mysql-client, mysql-common and libmysqlclient16. This is
> required because we need to make sure that mysqldump comes from the same
> MySQL version. On older distributions they are still using MySQL 5.0 and
> mysqldump from 5.0 does not cut it. Somehow dpkg fails to cope with it.
>
> Regards,
> Alex
>
Alex Yurchenko
1) do what apt-get -f install suggests to do.
2) dpkg -r mysql-server mysql-client libmysqlclient16
3) reinstall mysql-wsrep
If step 2 gives you problems (e.g. there are packages depending on
libmysqlclient16) try --force-depends.
On Mon, 5 Jul 2010 07:52:12 -0700 (PDT), meman <jon.ska...@gmail.com>
wrote:
--
Alexey Yurchenko,
Codership Oy, www.codership.com
Skype: alexey.yurchenko, Phone: +358-400-516-011
meman
handle mysql-wsrep too good. Example:
dpkg -i mysql-wsrep-5.1.44-0.7.4-i386.deb
dpkg: considering removing mysql-common in favour of mysql-wsrep ...
(Reading database ... 49830 files and directories currently
installed.)
Unpacking mysql-wsrep (from mysql-wsrep-5.1.44-0.7.4-i386.deb) ...
dpkg: dependency problems prevent configuration of mysql-wsrep:
mysql-wsrep depends on libdbd-mysql-perl (>= 1.2202); however:
Package libdbd-mysql-perl is not installed.
dpkg: error processing mysql-wsrep (--install):
Processing triggers for ureadahead ...
Errors were encountered while processing:
And then:
apt-get install libdbd-mysql-perl
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run `apt-get -f install' to correct these:
specify a solution).
concerned, but it breaks compatibility with any package depending on
the libmysqlclient16 - like php5-mysql
On Jul 5, 8:24 pm, Alex Yurchenko <alexey.yurche...@codership.com>
wrote:
> 1) do what apt-get -f install suggests to do.
> 2) dpkg -r mysql-server mysql-client libmysqlclient16
> 3) reinstall mysql-wsrep
>
> If step 2 gives you problems (e.g. there are packages depending on
> libmysqlclient16) try --force-depends.
>
Alexey Yurchenko
reconfigure dependent packages after installing mysql-wsrep.
meman
>dpkg --configure -a
libmysqlclient16 depends on mysql-common (>= 5.1.41-3ubuntu12.3);
however:
Package mysql-common is not installed.
libmysqlclient16
Building dependency tree
Reading state information... Done
You might want to run `apt-get -f install' to correct these:
The following packages have unmet dependencies:
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or
specify a solution).
mysql-common..
Not sure why is sais 4.1 tho, but lucid repo online (http://
packages.ubuntu.com/lucid/all/mysql-common/download) sais 5.1.41
Why isn't the mysql-wsrep bundled mysql-common one detected?
On Jul 6, 11:22 am, Alexey Yurchenko <alexey.yurche...@codership.com>
wrote:
Alex Yurchenko
asked? Why is dpkg still trying to configure it?
mysql-wsrep conflicts with all mysql packages from ubuntu 10.4 and they
all must be removed before mysql-wsrep installation. I know this is ugly
and we will try to address it in 0.7.5, but at this point this is the only
option.
it worked *almost* fine on 9.10 and older, but this libmysqlclient16 that
appeared in 10.4 broke whatever we had. See, the problem is that for older
distributions we can't just provide mysql-server package because it
requires 5.1 clients and where do you get 5.1 clients on 9.10? So for now
you have to *manually* remove all mysql packages that come with 10.4 and
then install mysql-wsrep (with --force-depends option if needed, perl libs
might give you a problem). I guess we have a hidden circular dependency
there: perl libs depend on libmysqlclient, mysql-wsrep provides
libmysqlclient but depends on perl libs. That must be the reason why dpkg
behaves that way. In older distributions perl libs depended on
libmysqlclient15 and everything was fine.
And yes, mysql-wsrep provides mysql-common:
$ dpkg-deb -I mysql-wsrep-5.1.44-0.7.4-i386.deb | grep Provides:
Provides: mysql-server-core-5.1, mysql-server-core, mysql-server-5.1,
mysql-server, mysql-client-5.1, mysql-client, mysql-common-5.1,
mysql-common, libmysqlclient16
On Tue, 6 Jul 2010 05:55:38 -0700 (PDT), meman <jon.ska...@gmail.com>
wrote:
--
meman
is that other packages are dependant on this package, and does not
detect/work with the mysql-wsrep provided one. Eg: when trying to
install php5-mysql. To uninstall the libmysqlclient16, any package
depending on it needs to be uninstalled also, like the php5-mysql
package. This effectively breaks php5-mysql (and other similar
packages), as it can't be installed again, without first removing
mysql-wsrep and downgrade mysql-common and similar..
I don't know why the wsrep provided ones doesn't work. Is there any
way to force this?
On Jul 6, 5:11 pm, Alex Yurchenko <alexey.yurche...@codership.com>
wrote:
> asked? Why is dpkg still trying to configure it?
>
> mysql-wsrep conflicts with all mysql packages from ubuntu 10.4 and they
> all must be removed before mysql-wsrep installation. I know this is ugly
> and we will try to address it in 0.7.5, but at this point this is the only
> option.
>
> it worked *almost* fine on 9.10 and older, but this libmysqlclient16 that
> appeared in 10.4 broke whatever we had. See, the problem is that for older
> distributions we can't just provide mysql-server package because it
> requires 5.1 clients and where do you get 5.1 clients on 9.10? So for now
> you have to *manually* remove all mysql packages that come with 10.4 and
> then install mysql-wsrep (with --force-depends option if needed, perl libs
> might give you a problem). I guess we have a hidden circular dependency
> there: perl libs depend on libmysqlclient, mysql-wsrep provides
> libmysqlclient but depends on perl libs. That must be the reason why dpkg
> behaves that way. In older distributions perl libs depended on
> libmysqlclient15 and everything was fine.
>
> And yes, mysql-wsrep provides mysql-common:
> $ dpkg-deb -I mysql-wsrep-5.1.44-0.7.4-i386.deb | grep Provides:
> Provides: mysql-server-core-5.1, mysql-server-core, mysql-server-5.1,
> mysql-server, mysql-client-5.1, mysql-client, mysql-common-5.1,
> mysql-common, libmysqlclient16
>
Alex Yurchenko
packages ignoring their dependencies. But I guess --auto-deconfigure is a
preferred method. Still when installing mysql-wsrep you'll need to use
--force-depends because of its circular dependency on perl libs.
Say, what happens if you do the following:
>0) start with the fully configured mysql server
1) dpkg -r --auto-deconfigure mysql-server mysql-client libmysqlclient16
mysql-common
2) dpkg -i --force-depends <mysql-wsrep deb>
3) dpkg --configure -a
If this does not work than the only way is to
0) start with the fully configured mysql server.
1) dpkg -r --force-depends mysql-server mysql-client libmysqlclient16
mysql-common
2) dpkg -i --force-depends <mysql-wsrep deb>
but it is somewhat risky as it would not show possible dependency
problems.
On Tue, 6 Jul 2010 09:22:02 -0700 (PDT), meman <jon.ska...@gmail.com>
wrote: