# emerge -avqt1 neutron [ebuild N ] sys-cluster/neutron-2013.2.3 USE="dhcp l3 metadata mysql openvswitch server -doc -postgres -sqlite {-test}" PYTHON_TARGETS="python2_7" [ebuild N ] dev-python/pyudev-0.16.1-r1 USE="-pygobject -pyqt4 -pyside {-test}" PYTHON_TARGETS="python2_7 python3_3 -python2_6 -python3_2" [ebuild N ] dev-python/alembic-0.6.3 USE="-doc {-test}" PYTHON_TARGETS="python2_7 python3_3 -python2_6 -python3_2" [ebuild U ] dev-python/sqlalchemy-0.9.4 [0.7.10] USE="sqlite -doc -examples {-test} (-firebird%) (-mssql%) (-mysql%*) (-postgres%)" PYTHON_TARGETS="python2_7 python3_3%* -pypy% -python2_6 -python3_2% -python3_4%" [ebuild N ] dev-python/mako-0.7.3-r2 USE="-doc {-test}" PYTHON_TARGETS="python2_7 python3_3 -python2_6 -python3_2" [ebuild N ] dev-python/jsonrpclib-0_pre20110820-r1 PYTHON_TARGETS="python2_7 -python2_6" !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: dev-python/sqlalchemy:0 (dev-python/sqlalchemy-0.7.10::gentoo, installed) pulled in by >=dev-python/sqlalchemy-0.7.8[mysql,python_targets_python2_7(-)?,-python_single_target_python2_7(-)] required by (sys-cluster/neutron-2013.2.3::gentoo, ebuild scheduled for merge) >=dev-python/sqlalchemy-0.7.8[mysql,python_targets_python2_7(-)?,-python_single_target_python2_7(-)] required by (sys-auth/keystone-2013.2.3-r1::gentoo, installed) >=dev-python/sqlalchemy-0.7.8[mysql,python_targets_python2_7(-)?,-python_single_target_python2_7(-)] required by (sys-cluster/nova-2013.2.3-r1::gentoo, installed) >=dev-python/sqlalchemy-0.7.8[mysql,python_targets_python2_7(-)?,-python_single_target_python2_7(-)] required by (app-admin/glance-2013.2.3-r1::gentoo, installed) <dev-python/sqlalchemy-0.7.99[mysql,python_targets_python2_7(-)?,-python_single_target_python2_7(-)] required by (app-admin/glance-2013.2.3-r1::gentoo, installed) (and 5 more with the same problems) (dev-python/sqlalchemy-0.9.4::gentoo, ebuild scheduled for merge) pulled in by >=dev-python/sqlalchemy-0.7.3[python_targets_python2_6(-)?,python_targets_python2_7(-)?,python_targets_python3_2(-)?,python_targets_python3_3(-)?,-python_single_target_python2_6(-),-python_single_target_python2_7(-),-python_single_target_python3_2(-),-python_single_target_python3_3(-)] required by (dev-python/alembic-0.6.3::gentoo, ebuild scheduled for merge)
The dependency is needed https://github.com/openstack/neutron/blob/stable/havana/requirements.txt
And yet conflict is still here: # emerge -1vqa neutron [ebuild N ] dev-python/jsonrpclib-0_pre20110820-r1 PYTHON_TARGETS="python2_7 -python2_6" [ebuild N ] dev-python/mako-0.7.3-r2 USE="-doc {-test}" PYTHON_TARGETS="python2_7 python3_3 -python2_6 -python3_2" [ebuild U ] dev-python/sqlalchemy-0.9.4 [0.7.9] USE="sqlite -doc -examples {-test} (-firebird%) (-mssql%) (-mysql%*) (-postgres%)" PYTHON_TARGETS="python2_7%* python3_3%* -pypy% -python2_6% -python3_2% -python3_4%" [ebuild N ] dev-python/alembic-0.6.3 USE="-doc {-test}" PYTHON_TARGETS="python2_7 python3_3 -python2_6 -python3_2" [ebuild U ] dev-python/sqlalchemy-0.7.10 [0.7.9] USE="mysql sqlite -doc -examples (-firebird) -mssql -postgres {-test}" PYTHON_TARGETS="python2_7%* -python2_6%" [ebuild N ] dev-python/pyudev-0.16.1-r1 USE="-pygobject -pyqt4 -pyside {-test}" PYTHON_TARGETS="python2_7 python3_3 -python2_6 -python3_2" [ebuild N ] sys-cluster/neutron-2013.2.3 USE="dhcp l3 metadata mysql openvswitch server -doc -postgres -sqlite {-test}" PYTHON_TARGETS="python2_7" !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: dev-python/sqlalchemy:0 (dev-python/sqlalchemy-0.7.10::gentoo, ebuild scheduled for merge) pulled in by >=dev-python/sqlalchemy-0.7.8[mysql,python_targets_python2_7(-)?,-python_single_target_python2_7(-)] required by (sys-cluster/neutron-2013.2.3::gentoo, ebuild scheduled for merge) <dev-python/sqlalchemy-0.7.99[mysql,python_targets_python2_7(-)?,-python_single_target_python2_7(-)] required by (sys-cluster/neutron-2013.2.3::gentoo, ebuild scheduled for merge) (dev-python/sqlalchemy-0.9.4::gentoo, ebuild scheduled for merge) pulled in by >=dev-python/sqlalchemy-0.7.3[python_targets_python2_6(-)?,python_targets_python2_7(-)?,python_targets_python3_2(-)?,python_targets_python3_3(-)?,-python_single_target_python2_6(-),-python_single_target_python2_7(-),-python_single_target_python3_2(-),-python_single_target_python3_3(-)] required by (dev-python/alembic-0.6.3::gentoo, ebuild scheduled for merge) The following keyword changes are necessary to proceed: (see "package.accept_keywords" in the portage(5) man page for more details) # required by dev-python/alembic-0.6.3 # required by sys-cluster/neutron-2013.2.3 # required by neutron (argument) =dev-python/sqlalchemy-0.9.4 ~amd64 # required by sys-cluster/neutron-2013.2.3[mysql] # required by neutron (argument) =dev-python/sqlalchemy-0.7.10 ~amd64
(note that on an ~amd64 system, I got no pb whatsoever)
(In reply to Matthew Thode ( prometheanfire ) from comment #1) > The dependency is needed > > https://github.com/openstack/neutron/blob/stable/havana/requirements.txt In that document upper limit is 0.9.99, not 0.7.99 SQLAlchemy>=0.7.8,<=0.9.99
SQLAlchemy>=0.7.8,<=0.7.99 copypasta
I think it's portage (?) bug. Dependency mismatch here is that openstack packages require sqlalchemy build for single target python 2.7, but alembic depends on multi target sqlalchemy. I'd like to ask portage team for help here. emerge -avq1 dev-python/alembic [ebuild N ] dev-python/mako-0.7.3-r2 USE="-doc {-test}" PYTHON_TARGETS="python2_7 python3_3 (-python2_6) -python3_2" [ebuild U ] dev-python/sqlalchemy-0.9.4 [0.7.10] USE="sqlite -doc -examples {-test} (-firebird%) (-mssql%) (-mysql%*) (-postgres%)" PYTHON_TARGETS="python2_7 python3_3%* -pypy% (-python2_6) -python3_2% -python3_4%" [ebuild N ] dev-python/alembic-0.6.3 USE="-doc {-test}" PYTHON_TARGETS="python2_7 python3_3 (-python2_6) -python3_2" !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: dev-python/sqlalchemy:0 (dev-python/sqlalchemy-0.7.10::gentoo, installed) pulled in by >=dev-python/sqlalchemy-0.7.8[mysql,python_targets_python2_7(-)?,-python_single_target_python2_7(-)] required by (sys-cluster/nova-2014.1::gentoo, installed) <dev-python/sqlalchemy-0.9.99[mysql,python_targets_python2_7(-)?,-python_single_target_python2_7(-)] required by (sys-cluster/nova-2014.1::gentoo, installed) <=dev-python/sqlalchemy-0.9.99[mysql,python_targets_python2_7(-)?,-python_single_target_python2_7(-)] required by (app-admin/glance-2014.1::gentoo, installed) <=dev-python/sqlalchemy-0.9.99[mysql,python_targets_python2_7(-)?,-python_single_target_python2_7(-)] required by (sys-auth/keystone-2014.1::gentoo, installed) >=dev-python/sqlalchemy-0.7.8[mysql,python_targets_python2_7(-)?,-python_single_target_python2_7(-)] required by (sys-auth/keystone-2014.1::gentoo, installed) >=dev-python/sqlalchemy-0.7.8[mysql,python_targets_python2_7(-)?,-python_single_target_python2_7(-)] required by (app-admin/glance-2014.1::gentoo, installed) (dev-python/sqlalchemy-0.9.4::gentoo, ebuild scheduled for merge) pulled in by dev-python/sqlalchemy[python_targets_python2_6(-)?,python_targets_python2_7(-)?,python_targets_python3_2(-)?,python_targets_python3_3(-)?,-python_single_target_python2_6(-),-python_single_target_python2_7(-),-python_single_target_python3_2(-),-python_single_target_python3_3(-)] required by (dev-python/alembic-0.6.3::vadimk, ebuild scheduled for merge)
It looks to me like dev-python/sqlalchemy-0.7.10 should only have PYTHON_TARGETS. What happens if you try to reinstall dev-python/sqlalchemy-0.7.10? emerge -1 --ignore-default-opts =dev-python/sqlalchemy-0.7.10 If you have to post more output with slot conflicts, please use a newer portage version, it has improved output. And post your emerge --info.
Created attachment 376134 [details] emerge --info
(In reply to Sebastian Luther (few) from comment #7) > What happens if you try to reinstall > dev-python/sqlalchemy-0.7.10? > > emerge -1 --ignore-default-opts =dev-python/sqlalchemy-0.7.10 emerge -1 --ignore-default-opts -q =dev-python/sqlalchemy-0.7.10 >>> Verifying ebuild manifests >>> Emerging (1 of 1) dev-python/sqlalchemy-0.7.10 >>> Installing (1 of 1) dev-python/sqlalchemy-0.7.10
(In reply to Sebastian Luther (few) from comment #7) > It looks to me like dev-python/sqlalchemy-0.7.10 should only have > PYTHON_TARGETS. So, you are saying neutron (and others) should have: >=dev-python/sqlalchemy-0.7.8[${PYTHON_USEDEP}] <dev-python/sqlalchemy-0.9.99[${PYTHON_USEDEP}] and pull dev-python/mysql-python as well, because sqlalchemy will not? mysql use flag is not used in >=dev-python/sqlalchemy-0.8 anymore (Why?)
fixed in the tree.
