| Summary: | MySQL 4.0.27-r1 has MySQL 5.0 as a dependency | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Kirk <khoganson> |
| Component: | Core - Dependencies | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | jakub |
| Priority: | High | ||
| Version: | 2.1 | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
This will show us what's pulling it in: emerge -pt =dev-db/mysql-4.0.27-r1 (In reply to comment #1) > This will show us what's pulling it in: > > emerge -pt =dev-db/mysql-4.0.27-r1 Well, this is a portage issue... nomerge ] dev-db/mysql-4.0.27-r1 USE="-berkdb -big-tables -debug -embedded -minimal perl -raid (-selinux) ssl -static" [ebuild N ] dev-perl/DBD-mysql-4.00.3 [ebuild N ] dev-perl/DBI-1.54 [ebuild N ] virtual/perl-Sys-Syslog-0.18 [ebuild N ] dev-perl/PlRPC-0.2018 [ebuild N ] dev-perl/Net-Daemon-0.39 [ebuild N ] virtual/mysql-5.0 [ebuild N ] dev-db/mysql-4.0.27-r1 USE="-berkdb -big-tables -debug -embedded -minimal perl -raid (-selinux) ssl -static" [nomerge ] dev-perl/DBD-mysql-4.00.3 [nomerge ] virtual/mysql-5.0 [ebuild N ] dev-db/mysql-5.0.34 USE="-berkdb -big-tables -cluster -debug -embedded -extraengine -latin1 -max-idx-128 -minimal perl (-selinux) ssl -static" [ebuild N ] dev-db/mysql-init-scripts-1.2 $ USE="-*" emerge -pt =dev-db/mysql-4.0.27-r1 These are the packages that would be merged, in reverse order: Calculating dependencies... done! [ebuild N ] dev-db/mysql-4.0.27-r1 USE="-berkdb -big-tables -debug -embedded -minimal -perl -raid (-selinux) -ssl -static" [ebuild N ] dev-db/mysql-init-scripts-1.2 dev-perl/DBD-mysql PDEPENDs on virtual/mysql; mysql.eclass PDEPENDs on dev-perl/DBD-mysql w/ USE=perl. Anyway, pretty much anything that depends on virtual/mysql and gets into depgraph will cause this. Yes, this is a very long standing bug. If you want mysql-4 then you'll have to mask mysql-5: echo ">=virtual/mysql-5" >> /etc/portage/package.mask *** This bug has been marked as a duplicate of bug 1343 *** (In reply to comment #3) > echo ">=virtual/mysql-5" >> /etc/portage/package.mask You also have to mask >=dev-db/mysql-5 if dev-db/mysql is in your world file or something depends on it, otherwise you'll get a similar error when you update your system. Even if bug 1343 is fixed, there's still no support for a versioned atom in the world file. We should have support for something like that in the near future though (bug 144480). |
# emerge -av =dev-db/mysql-4.0.27-r1 These are the packages that would be merged, in order: Calculating dependencies - !!! Multiple versions within a single package slot have been !!! pulled into the dependency graph: ('ebuild', '/', 'dev-db/mysql-5.0.26-r2', 'merge') pulled in by ('ebuild', '/', 'virtual/mysql-5.0', 'merge') ('ebuild', '/', 'dev-db/mysql-4.0.27-r1', 'merge') (no parents) Reproducible: Always Steps to Reproduce: 1. Fresh install 2. emerge -av =dev-db/mysql-4.0.27-r1 3.