http://qa.mandrakesoft.com/show_bug.cgi?id=3207
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |ASSIGNED
------- Additional Comments From [EMAIL PROTECTED] 2003-03-12 18:05 -------
I don't understand why it says everything already installed for you but I manage
te reproduce it here.
I try to do something with it and fix it, expect fixes in perl-URPM.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: ASSIGNED
creation_date:
description:
I just had some problem installing MySQL-Max due to the new conflict to MySQL >
4.0.11. I am not certain, if this happens in an upgrade from ML 9.0, but you may
want to check it out.
In short, "urpmi MySQL-Max [MySQL]" only handles the conflict properly (i.e.
suggesting uninstalling the MySQL package), after I upgraded to the newest MySQL
package (MySQL-4.0.11a-4mdk). It looks that the installed RPM needs to have the
conflict marker in order for it to be honored completely.
This is only of interest for people who installed the -Max version of 3.23.x,
which was supposed to have MySQL-Max installed alongside (more presicly: after)
MySQL. From my observations (see below), I fear people having used MySQL-Max in
this way, will run into the same conflict I had. But I am not sure about it and
unfortunately don't have an v3.23 installation to test with.
As this is a problem with the different packaging used before (also in ML9.0),
it may be possible/probable that the problem will also happen for a full upgrade
from 9.0 to 9.1, depending how similar the installer works to urpmi.
With MySQL 4.0.11a-3mdk installed as this
$ rpm -qa | grep -i mysql
MySQL-client-4.0.11a-3mdk
libmysql10-3.23.55-1mdk
libmysql12-4.0.11a-3mdk
MySQL-common-4.0.11a-3mdk
MySQL-4.0.11a-3mdk
php-mysql-4.3.0-2mdk
I get the following:
$ urpmi MySQL-Max MySQL
To satisfy dependencies, the following packages are going to be installed (17 MB):
MySQL-4.0.11a-4mdk.i586
MySQL-Max-4.0.11a-4mdk.i586
MySQL-common-4.0.11a-4mdk.i586
Is this OK? (Y/n)
installing
/var/local/mirror/mandrake/cooker-tree/Mandrake/RPMS/MySQL-4.0.11a-4mdk.i586.rpm
/var/local/mirror/mandrake/cooker-tree/Mandrake/RPMS/MySQL-Max-4.0.11a-4mdk.i586.rpm
/var/local/mirror/mandrake/cooker-tree/Mandrake/RPMS/MySQL-common-4.0.11a-4mdk.i586.rpm
Installation failed:
MySQL-Max > 4.0.11 conflicts with MySQL-4.0.11a-4mdk
MySQL > 4.0.11 conflicts with MySQL-Max-4.0.11a-4mdk
The same happens with "urpmi MySQL-Max". As I said, the problem went away when I
upgraded MySQL beforehand: Now I am asked that MySQL-Max resp. MySQL has to be
removed in order to install the other packet.
As I said, I am not sure how the installer will handle this, but I fear that it
will try the equivalent of "urpmi MySQL-Max MySQL". If you are sure that is no
problem for a full install, feel free to close this bug as invalid, of course.
Severity: minor, because only users of MySQL-Max are affected (and people seem
to not install it that much).
(And yes, I am aware that my environment is signicantly different from ML 9.0,
but the package conflict should be the same. I would love if someone could test
with the ML 9.0 packages.)
