# How do I work around a 'can't activate gem xxx version 1.2.3, because gem xxx version 2.3.4 is alrea

**URL:** <https://www.ruby-forum.com/t/how-do-i-work-around-a-cant-activate-gem-xxx-version-1-2-3-because-gem-xxx-version-2-3-4-is-alrea/172827>\
**Category:** Ruby\
**Created:** [July 28, 2009, 5:41pm UTC](https://www.ruby-forum.com/t/how-do-i-work-around-a-cant-activate-gem-xxx-version-1-2-3-because-gem-xxx-version-2-3-4-is-alrea/172827 "2009-07-28T17:41:30Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![lycanthrope](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/a88e57/32.png) [@lycanthrope](https://www.ruby-forum.com/u/lycanthrope)\
**Post date:** [July 28, 2009, 5:41pm UTC](https://www.ruby-forum.com/t/how-do-i-work-around-a-cant-activate-gem-xxx-version-1-2-3-because-gem-xxx-version-2-3-4-is-alrea/172827/1 "2009-07-28T17:41:30Z")

</div>

How can i work around this error? Is it possible to force ruport to use  
1.5.0?

can’t activate fastercsv (= 1.2.3, runtime) for [“ruport-1.6.1”],  
already activated fastercsv-1.5.0 for [] (Gem::LoadError)

Thanks,  
reid

---

<div class="post-metadata">

**Author:** ![lycanthrope](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/a88e57/32.png) [@lycanthrope](https://www.ruby-forum.com/u/lycanthrope)\
**Post date:** [July 28, 2009, 8:13pm UTC](https://www.ruby-forum.com/t/how-do-i-work-around-a-cant-activate-gem-xxx-version-1-2-3-because-gem-xxx-version-2-3-4-is-alrea/172827/2 "2009-07-28T20:13:44Z")

</div>

On Jul 28, 2009, at 08:40 , Reid T. wrote:

> How can i work around this error? Is it possible to force ruport to  
> use  
> 1.5.0?
> 
> can’t activate fastercsv (= 1.2.3, runtime) for [“ruport-1.6.1”],  
> already activated fastercsv-1.5.0 for [] (Gem::LoadError)

that latter “for []” doesn’t help, or it is (poorly) stating that YOU  
activated fastercsv. I’m gonna guess the latter. So, either activate  
it with a version specifier that matches:

gem ‘fastercsv’, ‘= 1.2.3’

or activate ruport before you require fastercsv.

We really need to stop using ‘= x.y.z’ because of problems like this.  
In this case tho, it looks like ruport is falling behind on  
maintenance (or you’re using an old version, which is another way for  
you to fix this if so)

---

<div class="post-metadata">

**Author:** ![lycanthrope](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/a88e57/32.png) [@lycanthrope](https://www.ruby-forum.com/u/lycanthrope)\
**Post date:** [July 29, 2009, 1:25am UTC](https://www.ruby-forum.com/t/how-do-i-work-around-a-cant-activate-gem-xxx-version-1-2-3-because-gem-xxx-version-2-3-4-is-alrea/172827/3 "2009-07-29T01:25:44Z")

</div>

Ryan D. wrote:

> that latter “for []” doesn’t help, or it is (poorly) stating that YOU  
> so)

Thanks for your response.

This was ruport installed today via gem - so should be the latest  
version.  
How do I activate ruport before requiring fastercsv, is it simply  
requiring  
ruport before fastercsv, or is there more involved?

I would hope that ruport would work with fastercsv \>=1.2.3 w/o issue and  
that  
there would be a simple way to make it do so???

reid

---

<div class="post-metadata">

**Author:** ![lycanthrope](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/a88e57/32.png) [@lycanthrope](https://www.ruby-forum.com/u/lycanthrope)\
**Post date:** [July 29, 2009, 2:32am UTC](https://www.ruby-forum.com/t/how-do-i-work-around-a-cant-activate-gem-xxx-version-1-2-3-because-gem-xxx-version-2-3-4-is-alrea/172827/4 "2009-07-29T02:32:26Z")

</div>

On Jul 28, 2009, at 16:25, Reid T. wrote:

> > activate it with a version specifier that matches:  
> > How do I activate ruport before requiring fastercsv, is it simply  
> > requiring ruport before fastercsv, or is there more involved?

require ‘ruport’ before require ‘fastercsv’ should be sufficient.

> I would hope that ruport would work with fastercsv \>=1.2.3 w/o issue  
> and that there would be a simple way to make it do so???

$ gem dep -r ruport  
Gem ruport-1.6.1  
fastercsv (= 1.2.3, runtime)  
pdf-writer (= 1.1.8, runtime)

[…]  
$ gem list -r fastercsv

\*\*\* REMOTE GEMS \*\*\*

fastercsv (1.5.0)

Looks like it’s locked down, it should probably be ‘~\> 1.2’ or similar  
instead. Greg?

---

<div class="post-metadata">

**Author:** ![lycanthrope](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/a88e57/32.png) [@lycanthrope](https://www.ruby-forum.com/u/lycanthrope)\
**Post date:** [July 29, 2009, 2:41am UTC](https://www.ruby-forum.com/t/how-do-i-work-around-a-cant-activate-gem-xxx-version-1-2-3-because-gem-xxx-version-2-3-4-is-alrea/172827/5 "2009-07-29T02:41:48Z")

</div>

On Tue, Jul 28, 2009 at 8:32 PM, Eric H.[removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:  
stercsv (1.5.0)

> Looks like it’s locked down, it should probably be ‘~\> 1.2’ or similar  
> instead. Greg?

Yeah, I think that’d be fine. Actually, Ruport should work with  
basically “Any fastercsv”, I just haven’t gotten around to fixing and  
releasing.  
It was a mistake to lock this way in the first place.

-greg