I have already installed dev-db/mysql-community-5.0.67. When I try to update my phpmyadmin installation, portage insists that dev-db/mysql should be installed. This of course is blocked by existing dev-db/mysql-community installation. Reproducible: Always Steps to Reproduce: 1. Install dev-db/mysql-community on a system without mysql. 2. Try to emerge dev-db/phpmyadmin-3.0.0 or later. Actual Results: I am told that phpmyadmin needs dev-db/mysql which is blocked by dev-db/mysql-community. Expected Results: dev-db/phpmyadmin should install without problems. It seems that the bug I am reporting was introduced by the proposed patch for bug #248623.
It's just a breakage in Portage when calculating the deps: http://archives.gentoo.org/gentoo-dev/msg_efce154d642fe6ede38d084a33c7f949.xml zmedico: Are you going to roll out a new Portage soon with the fix?
(In reply to comment #1) > It's just a breakage in Portage when calculating the deps: > http://archives.gentoo.org/gentoo-dev/msg_efce154d642fe6ede38d084a33c7f949.xml > > zmedico: > Are you going to roll out a new Portage soon with the fix? > I doubt this is the case. I tried to do the inverse proposed workaround (i.e. mask mysql instead of mysql-community) and it didn't work. It insists that mysql should be pulled: ishi portage # cat /etc/portage/package.mask | grep mysql dev-db/mysql ishi portage # emerge -uvp phpmyadmin These are the packages that would be merged, in order: Calculating dependencies... done! !!! All ebuilds that could satisfy ">=dev-db/mysql-5.0.15" have been masked. !!! One of the following masked packages is required to complete your request: - dev-db/mysql-5.0.76 (masked by: package.mask) - dev-db/mysql-5.0.72-r1 (masked by: package.mask) - dev-db/mysql-5.0.72 (masked by: package.mask) - dev-db/mysql-5.0.70-r1 (masked by: package.mask) - dev-db/mysql-5.0.70 (masked by: package.mask) - dev-db/mysql-5.0.60-r1 (masked by: package.mask) - dev-db/mysql-5.0.60 (masked by: package.mask) - dev-db/mysql-5.0.56 (masked by: package.mask) - dev-db/mysql-5.0.54 (masked by: package.mask) - dev-db/mysql-5.0.44-r2 (masked by: package.mask) - dev-db/mysql-5.0.44-r1 (masked by: package.mask) - dev-db/mysql-5.0.44 (masked by: package.mask) - dev-db/mysql-5.0.42 (masked by: package.mask) - dev-db/mysql-5.0.40 (masked by: package.mask) - dev-db/mysql-5.0.38 (masked by: package.mask) - dev-db/mysql-5.0.34 (masked by: package.mask) - dev-db/mysql-5.0.32 (masked by: package.mask) - dev-db/mysql-5.0.26-r2 (masked by: package.mask) For more information, see the MASKED PACKAGES section in the emerge man page or refer to the Gentoo Handbook. (dependency required by "dev-db/phpmyadmin-3.1.2" [ebuild]) (dependency required by "phpmyadmin" [argument])
(In reply to comment #1) > It's just a breakage in Portage when calculating the deps: > http://archives.gentoo.org/gentoo-dev/msg_efce154d642fe6ede38d084a33c7f949.xml > > zmedico: > Are you going to roll out a new Portage soon with the fix? Maybe this weekend, but then it will be at least a month before it goes into stable. (In reply to comment #2) > I doubt this is the case. I tried to do the inverse proposed workaround (i.e. > mask mysql instead of mysql-community) and it didn't work. It insists that > mysql should be pulled: You're definitely going to have to uninstall mysql-community in order to install dev-db/phpmyadmin-3.1.2, given that it currently has >=dev-db/mysql-5.0.15 in RDEPEND. As a workaround for the issue mentioned in comment #1, you're also going to have to mask mysql-community.
> > You're definitely going to have to uninstall mysql-community in order to > install dev-db/phpmyadmin-3.1.2, given that it currently has > >=dev-db/mysql-5.0.15 in RDEPEND. As a workaround for the issue mentioned in > comment #1, you're also going to have to mask mysql-community. > So there won't be a proper fix for this ebuild? Is there a technical reason that phpmyadmin won't work with mysql-community? IMHO this forced switch to mysql is rather un-gentoo-ish. As I pointed out, the patch introduced to fix bug #248623 seems sloppy. The RDEPEND should probably be for virtual/mysql rather than dev-db/mysql. This helps avoid the mentioned problem. I tried it and it seems to work. Also, phpmyadmin site does not mention anything about not being compatible with mysql-community.
Reassigning to web-apps as per comment #4 since this bug is actually is not about the portage issue mentioned in comment #1.
No response from web-apps, fixed by mysql-team.