| 1 |
On 03/11/13 14:43, Homer Parker wrote: |
| 2 |
> |
| 3 |
> Running stable I'm running into: |
| 4 |
> |
| 5 |
> $ emerge -pv cinder keystone quantum glance nova |
| 6 |
> ...... |
| 7 |
> |
| 8 |
> !!! Multiple package instances within a single package slot have been pulled |
| 9 |
> !!! into the dependency graph, resulting in a slot conflict: |
| 10 |
> |
| 11 |
> dev-python/amqplib:0 |
| 12 |
> |
| 13 |
> (dev-python/amqplib-0.6.1::gentoo, ebuild scheduled for merge) pulled in by |
| 14 |
> =dev-python/amqplib-0.6.1 required by (sys-cluster/nova-2012.2.3-r1::gentoo, ebuild scheduled for merge) |
| 15 |
> (and 2 more with the same problem) |
| 16 |
> |
| 17 |
> (dev-python/amqplib-1.0.2-r1::gentoo, ebuild scheduled for merge) pulled in by |
| 18 |
> >=dev-python/amqplib-1.0.2 required by (dev-python/kombu-1.0.4::gentoo, ebuild scheduled for merge) |
| 19 |
> |
| 20 |
> dev-python/routes:0 |
| 21 |
> |
| 22 |
> (dev-python/routes-1.13-r1::gentoo, ebuild scheduled for merge) pulled in by |
| 23 |
> >=dev-python/routes-1.12.3[python_targets_python2_7(-)?,-python_single_target_python2_7(-)] required by (sys-cluster/quantum-201 |
| 24 |
> 2.2.3::gentoo, ebuild scheduled for merge) |
| 25 |
> |
| 26 |
> (dev-python/routes-1.12.3::gentoo, ebuild scheduled for merge) pulled in by |
| 27 |
> =dev-python/routes-1.12.3 required by (sys-cluster/cinder-2012.2.3::gentoo, ebuild scheduled for merge) |
| 28 |
> (and 1 more with the same problem) |
| 29 |
> |
| 30 |
> dev-python/pastedeploy:0 |
| 31 |
> |
| 32 |
> (dev-python/pastedeploy-1.5.0-r1::gentoo, ebuild scheduled for merge) pulled in by |
| 33 |
> =dev-python/pastedeploy-1.5.0-r1[python_targets_python2_7(-)?,-python_single_target_python2_7(-)] required by (sys-cluster/quant |
| 34 |
> um-2012.2.3::gentoo, ebuild scheduled for merge) |
| 35 |
> |
| 36 |
> (dev-python/pastedeploy-1.5.0::gentoo, ebuild scheduled for merge) pulled in by |
| 37 |
> =dev-python/pastedeploy-1.5.0 required by (sys-cluster/nova-2012.2.3-r1::gentoo, ebuild scheduled for merge) |
| 38 |
> (and 1 more with the same problem) |
| 39 |
> |
| 40 |
> dev-python/anyjson:0 |
| 41 |
> |
| 42 |
> (dev-python/anyjson-0.3.3-r1::gentoo, ebuild scheduled for merge) pulled in by |
| 43 |
> >=dev-python/anyjson-0.3.3 required by (dev-python/kombu-1.0.4::gentoo, ebuild scheduled for merge) |
| 44 |
> |
| 45 |
> (dev-python/anyjson-0.2.4::gentoo, ebuild scheduled for merge) pulled in by |
| 46 |
> =dev-python/anyjson-0.2.4[python_targets_python2_7(-)?,-python_single_target_python2_7(-)] required by (sys-cluster/quantum-2012 |
| 47 |
> .2.3::gentoo, ebuild scheduled for merge) |
| 48 |
> |
| 49 |
> dev-python/webob:0 |
| 50 |
> |
| 51 |
> (dev-python/webob-1.0.8::gentoo, ebuild scheduled for merge) pulled in by |
| 52 |
> =dev-python/webob-1.0.8 required by (sys-cluster/quantum-2012.2.3::gentoo, ebuild scheduled for merge) |
| 53 |
> (and 1 more with the same problem) |
| 54 |
> |
| 55 |
> (dev-python/webob-1.2.3-r1::gentoo, ebuild scheduled for merge) pulled in by |
| 56 |
> dev-python/webob[python_targets_python2_6(-)?,python_targets_python2_7(-)?,python_targets_pypy1_9(-)?,python_targets_pypy2_0(-)? |
| 57 |
> ,-python_single_target_python2_6(-),-python_single_target_python2_7(-),-python_single_target_pypy1_9(-),-python_single_target_pypy2_ |
| 58 |
> 0(-)] required by (dev-python/routes-1.13-r1::gentoo, ebuild scheduled for merge) |
| 59 |
> |
| 60 |
> dev-python/lockfile:0 |
| 61 |
> |
| 62 |
> (dev-python/lockfile-0.8::gentoo, ebuild scheduled for merge) pulled in by |
| 63 |
> =dev-python/lockfile-0.8 required by (sys-cluster/cinder-2012.2.3::gentoo, ebuild scheduled for merge) |
| 64 |
> |
| 65 |
> (dev-python/lockfile-0.9.1::gentoo, ebuild scheduled for merge) pulled in by |
| 66 |
> >=dev-python/lockfile-0.9 required by (dev-python/python-daemon-1.6::gentoo, ebuild scheduled for merge) |
| 67 |
> |
| 68 |
> |
| 69 |
> Are there reasons for requiring the old versions or could they all be |
| 70 |
> changed to versionless deps? |
| 71 |
> |
| 72 |
The reason I specified the old version is because they are specified as |
| 73 |
that in the pip-requires. If the pip-requires did not specify a version |
| 74 |
then I went versionless. I have not had a chance to check if nova works |
| 75 |
against the newer libs, but would not expect it to. |
| 76 |
|
| 77 |
-- |
| 78 |
-- Matthew Thode (prometheanfire) |
Archives