public inbox for gentoo-openstack@lists.gentoo.org
 help / color / mirror / Atom feed
From: Homer Parker <hparker@gentoo.org>
To: gentoo-openstack@lists.gentoo.org
Subject: [gentoo-openstack] Deps
Date: Mon, 11 Mar 2013 14:43:05 -0500	[thread overview]
Message-ID: <1363030985.21898.23.camel@homer> (raw)

[-- Attachment #1: Type: text/plain, Size: 3441 bytes --]


	Running stable I'm running into:

$ emerge -pv cinder keystone quantum glance nova
......

!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:

dev-python/amqplib:0

  (dev-python/amqplib-0.6.1::gentoo, ebuild scheduled for merge) pulled in by
    =dev-python/amqplib-0.6.1 required by (sys-cluster/nova-2012.2.3-r1::gentoo, ebuild scheduled for merge)
    (and 2 more with the same problem)

  (dev-python/amqplib-1.0.2-r1::gentoo, ebuild scheduled for merge) pulled in by
    >=dev-python/amqplib-1.0.2 required by (dev-python/kombu-1.0.4::gentoo, ebuild scheduled for merge)

dev-python/routes:0

  (dev-python/routes-1.13-r1::gentoo, ebuild scheduled for merge) pulled in by
    >=dev-python/routes-1.12.3[python_targets_python2_7(-)?,-python_single_target_python2_7(-)] required by (sys-cluster/quantum-201
2.2.3::gentoo, ebuild scheduled for merge)

  (dev-python/routes-1.12.3::gentoo, ebuild scheduled for merge) pulled in by
    =dev-python/routes-1.12.3 required by (sys-cluster/cinder-2012.2.3::gentoo, ebuild scheduled for merge)
    (and 1 more with the same problem)

dev-python/pastedeploy:0

  (dev-python/pastedeploy-1.5.0-r1::gentoo, ebuild scheduled for merge) pulled in by
    =dev-python/pastedeploy-1.5.0-r1[python_targets_python2_7(-)?,-python_single_target_python2_7(-)] required by (sys-cluster/quant
um-2012.2.3::gentoo, ebuild scheduled for merge)

  (dev-python/pastedeploy-1.5.0::gentoo, ebuild scheduled for merge) pulled in by
    =dev-python/pastedeploy-1.5.0 required by (sys-cluster/nova-2012.2.3-r1::gentoo, ebuild scheduled for merge)
    (and 1 more with the same problem)

dev-python/anyjson:0

  (dev-python/anyjson-0.3.3-r1::gentoo, ebuild scheduled for merge) pulled in by
    >=dev-python/anyjson-0.3.3 required by (dev-python/kombu-1.0.4::gentoo, ebuild scheduled for merge)

  (dev-python/anyjson-0.2.4::gentoo, ebuild scheduled for merge) pulled in by
    =dev-python/anyjson-0.2.4[python_targets_python2_7(-)?,-python_single_target_python2_7(-)] required by (sys-cluster/quantum-2012
.2.3::gentoo, ebuild scheduled for merge)

dev-python/webob:0

  (dev-python/webob-1.0.8::gentoo, ebuild scheduled for merge) pulled in by
    =dev-python/webob-1.0.8 required by (sys-cluster/quantum-2012.2.3::gentoo, ebuild scheduled for merge)
    (and 1 more with the same problem)

  (dev-python/webob-1.2.3-r1::gentoo, ebuild scheduled for merge) pulled in by
    dev-python/webob[python_targets_python2_6(-)?,python_targets_python2_7(-)?,python_targets_pypy1_9(-)?,python_targets_pypy2_0(-)?
,-python_single_target_python2_6(-),-python_single_target_python2_7(-),-python_single_target_pypy1_9(-),-python_single_target_pypy2_
0(-)] required by (dev-python/routes-1.13-r1::gentoo, ebuild scheduled for merge)

dev-python/lockfile:0

  (dev-python/lockfile-0.8::gentoo, ebuild scheduled for merge) pulled in by
    =dev-python/lockfile-0.8 required by (sys-cluster/cinder-2012.2.3::gentoo, ebuild scheduled for merge)

  (dev-python/lockfile-0.9.1::gentoo, ebuild scheduled for merge) pulled in by
    >=dev-python/lockfile-0.9 required by (dev-python/python-daemon-1.6::gentoo, ebuild scheduled for merge)


	Are there reasons for requiring the old versions or could they all be
changed to versionless deps?

-- 
Homer Parker <hparker@gentoo.org>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 230 bytes --]

             reply	other threads:[~2013-03-11 19:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-11 19:43 Homer Parker [this message]
2013-03-11 20:33 ` [gentoo-openstack] Deps Matthew Thode

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1363030985.21898.23.camel@homer \
    --to=hparker@gentoo.org \
    --cc=gentoo-openstack@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox