Bug 384299 – circular dependency between dev-ruby/rspec-mocks and dev-ruby/rspec-expectations when USE=test"

• Status: RESOLVED CANTFIX
• Product: Gentoo Linux

[Description Eric Martin 2011-09-24 13:36:23 UTC]

* Error: circular dependencies:

(dev-ruby/rspec-mocks-2.6.0::gentoo, ebuild scheduled for merge) depends on
 (dev-ruby/rspec-expectations-2.6.0::gentoo, ebuild scheduled for merge) (buildtime)
  (dev-ruby/rspec-mocks-2.6.0::gentoo, ebuild scheduled for merge) (buildtime)

It might be possible to break this cycle
by applying any of the following changes:
- dev-ruby/rspec-expectations-2.6.0 (Change USE: -test)
- dev-ruby/rspec-mocks-2.6.0 (Change USE: -test)

Setting -test in /etc/make.conf doesn't work and setting -test in /etc/portage/package.use doesn't work either.

rspec-mocks-2.6.0:

ruby_add_bdepend "test? (
        >=dev-ruby/rspec-core-2.6.0:2
        dev-ruby/rspec-expectations:2
    )
    doc? ( 

rspec-expectations=2.6.0


ruby_add_bdepend "test? (
        >=dev-ruby/rspec-core-2.4.0:2
        dev-ruby/rspec-mocks:2
    )"

[Comment 1 Eric Martin 2011-09-24 16:34:19 UTC]

This bug blocks emerge -uDavN world, due to net-anaylyzer/nmap as well as app-admin/puppet.

[Comment 2 Alex Legler (RETIRED) 2011-09-24 19:26:55 UTC]

If you need a quick fix to be able to perform your updates, don't build them with FEATURES="test". Seeing you not knowing this, I guess you're using a developer profile which -- as the handbook clearly states -- is intended for Gentoo developers, not people doing general software development on Gentoo.

I don't see how this could be fixed properly. Some PDEPEND hacks maybe, but I don't see them being worth implementing. Hans, what's your take?

[Comment 3 Eric Martin 2011-09-24 20:19:16 UTC]

Sorry, I didn't realize I had left my machine on the developer profile.

[Comment 4 Hans de Graaff 2011-09-26 19:35:22 UTC]

(In reply to comment #2)

> I don't see how this could be fixed properly. Some PDEPEND hacks maybe, but I
> don't see them being worth implementing. Hans, what's your take?

I don't think it's possible with PDEPENDs since the package are so interlocked. We already try to relax the test dependencies so that a new version can be tested with an older version if possible. I think that is the maximum we can do.