This project is archived and is in readonly mode.

#3372 ✓invalid
David Lee

gems:install rake task breaks if a versioned gem is required but an older version is install which satisfies another gem's dependency

Reported by David Lee | October 13th, 2009 @ 07:21 AM

If I have the gems "yourgem-1.0.0" and "mygem-1.0.0" installed, and yourgem depends on mygem >= 1.0.0, then the following configuration will break:

config.gem :mygem, :version => '2.0.0'
config.gem :yourgem, :verison => '1.0.0'

Because yourgem will activate mygem-1.0.0 and trying to activate mygem-2.0.0 will result in a version conflict:

rake aborted! can't activate , already activated mygem-1.0.0

Comments and changes to this ticket

  • Matt Jones

    Matt Jones October 16th, 2009 @ 08:36 PM

    • Assigned user set to “Matt Jones”

    Can you give a real example for this? The one you've shown doesn't make sense for several reasons:

    • since mygem is first, it will be activated first. If your environment.rb says this and you're seeing mygem-1.0.0 activated, then something else is triggering it - maybe a stray require or gem statement in environment.rb?

    • if mygem-2.0.0 is the latest version installed, then the stated dependency in yourgem will ALSO activate mygem-2.0.0, as the code (if all it has is a >= 1.0.0) will pick the highest version.

    Thanks!

  • Mike Riley

    Mike Riley June 17th, 2010 @ 01:46 AM

    • State changed from “new” to “incomplete”

    Hello David,

    I am going through some of the old tickets to see if we can get some movement on these older issues. I was curious if you had an example for this as Matt asked for previously. Let us know if you have more information so we can check this out. I am marking this as incomplete for now, but feel free to update this when you have a minute.

    thanks
    Mike Riley
    twitter.com/wdperson

  • David Lee

    David Lee June 17th, 2010 @ 01:55 AM

    Bundler should address these issues. I think it's safe to invalidate this bug.

  • Mike Riley

    Mike Riley June 17th, 2010 @ 01:59 AM

    • State changed from “incomplete” to “invalid”

    Hello David,

    Thanks for the update on this issue. I'll mark this as invalid as requested.

    Mike Riley
    twitter.com/wdperson

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2 style="font-size: 14px">Tickets have moved to Github</h2>

The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>

Pages