[Cooker] [Bug 3207] [urpmi] conflict MySQL vs MySQL-Max only partially works
http://qa.mandrakesoft.com/show_bug.cgi?id=3207 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|CLOSED --- Additional Comments From [EMAIL PROTECTED] 2003-03-13 12:49 --- Works fine for me (and even does something sensible for urpmi MySQL-Max MySQL: choosing the not-installed one over the installed one). Thanks! --- 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: CLOSED 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.)
[Cooker] [Bug 3207] [urpmi] conflict MySQL vs MySQL-Max only partially works
http://qa.mandrakesoft.com/show_bug.cgi?id=3207 [EMAIL PROTECTED] changed: What|Removed |Added AssignedTo|[EMAIL PROTECTED] |[EMAIL PROTECTED] Status|UNCONFIRMED |NEW Component|packaging |packaging Ever Confirmed||1 Product|MySQL-Max |urpmi Version|4.0.11a-4mdk|4.2-30mdk --- Additional Comments From [EMAIL PROTECTED] 2003-03-12 13:27 --- So there is effectively a problem, can you send me a bug report using --bug when using urpmi which cause the problem. --- 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: NEW 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.)
[Cooker] [Bug 3207] [urpmi] conflict MySQL vs MySQL-Max only partially works
http://qa.mandrakesoft.com/show_bug.cgi?id=3207 --- Additional Comments From [EMAIL PROTECTED] 2003-03-12 13:54 --- I just reproduced it by downgrading to the MySQL-4.0.11a-4mdk version (also all related packages) and then doing urpmi MySQL-Max again. With --bug the output changed to Everything already installed. Is that expected? Anyhow, without --bug I get exactly the same message as in comment #6. I sent you an mail (to [EMAIL PROTECTED]) with the resulting directory in a tar.gz file. Since I recently got bounces from addresses @mandrakesoft in CC's (looks like some weird TLS problem on our side), I write this bug entry additionally. Let me know, if you don't get the mail (the bounces have some days delay). --- 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: NEW 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.)
[Cooker] [Bug 3207] [urpmi] conflict MySQL vs MySQL-Max only partially works
http://qa.mandrakesoft.com/show_bug.cgi?id=3207 --- Additional Comments From [EMAIL PROTECTED] 2003-03-12 15:16 --- Created an attachment (id=341) -- (http://qa.mandrakesoft.com/attachment.cgi?id=341action=view) debug directly of urpmi --bug MySQL-Max Okay, tar.gz is attached. I just tried to reproduce it and interestingly got no message at all (but it works for about 5 seconds). I then deinstalled MySQL completely and can reproduce this: The first time I call it with --bug I get Everything already installed, the second time (and thereafter) I get an empty message. I can reset the status by calling it without --bug. Then the next with --bug will have the message. I assured that I also get if I try immediately after an deinstall (with --bug). All the time the output from a call without --bug stays the same. Well, because this sounds extremely like a broken installation of urpmi, I did an uninstall and reinstall (only of urpmi and dependecies, deinstalling rpm is a bit too much for now). Also did rpm --rebuild and urpmi.update -a. Arggg! Still all the same, exept that the cases when Everything already installed appears is exactly the other way around. *bangingheadagainstwall* --- 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: NEEDINFO 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.)
[Cooker] [Bug 3207] [urpmi] conflict MySQL vs MySQL-Max only partially works
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.)
[Cooker] [Bug 3207] [urpmi] conflict MySQL vs MySQL-Max only partially works
http://qa.mandrakesoft.com/show_bug.cgi?id=3207 [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-03-12 19:31 --- Fixed in perl-URPM-0.81-13mdk. --- 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: RESOLVED 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.)
