> My guess is that the server at http://gems.rubyonrails.org needs to be
> updated. If you don't need that I'd remove it from your source list.
> You can always get gems from there with --sourcehttp://gems.rubyforge.org/on
> the command line.
>
> $ gem sources -r http://gems.rubyonrails.org
> $ g
On Wed, Sep 23, 2009 at 3:53 PM, DanS wrote:
>> Well that explains why you're not seeing --prerelease gems. What do
>> you get from this:
>>
>> gem sources
>
> *** CURRENT SOURCES ***
>
> http://gems.rubyforge.org
> http://gems.rubyonrails.org
> http://gems.github.com
>
> -This is after I followed
> Well that explains why you're not seeing --prerelease gems. What do
> you get from this:
>
> gem sources
*** CURRENT SOURCES ***
http://gems.rubyforge.org
http://gems.rubyonrails.org
http://gems.github.com
-This is after I followed Stephen Eley's advice (thanks Stephen) and
added github as a s
On Wed, Sep 23, 2009 at 3:41 PM, DanS wrote:
>> And what do you see if you type this:
>>
>> gem q -rn rspec --prerelease
>
> *** REMOTE GEMS ***
>
> ERROR: While executing gem ... (Gem::OperationNotSupportedError)
> Prereleases not supported on legacy repositories
Well that explains why you'r
> And what do you see if you type this:
>
> gem q -rn rspec --prerelease
*** REMOTE GEMS ***
ERROR: While executing gem ... (Gem::OperationNotSupportedError)
Prereleases not supported on legacy repositories
___
rspec-users mailing list
rspec-users@
On Wed, Sep 23, 2009 at 3:20 PM, DanS wrote:
>> What OS and ruby/rubygems version? The --prerelease flag is a fairly
>> recent addition and may not work everywhere yet.
>
> Mac OS X 10.5.8
> ruby 1.8.6 (2008-08-11 patchlevel 287) [universal-darwin9.0]
> gem 1.3.5
And what do you see if you type t
> What OS and ruby/rubygems version? The --prerelease flag is a fairly
> recent addition and may not work everywhere yet.
Mac OS X 10.5.8
ruby 1.8.6 (2008-08-11 patchlevel 287) [universal-darwin9.0]
gem 1.3.5
___
rspec-users mailing list
rspec-users@ru
On Wed, Sep 23, 2009 at 1:16 PM, DanS wrote:
>
> but I still get the same error after installing bmabey-fakefs. I
> notice that "gem list" command shows this as "fakefs" and not "bmabey-
> fakefs" but I don't know if this naming difference matters, or what to
> do about it if it does.
I'm glad y
On Wed, Sep 23, 2009 at 1:53 PM, DanS wrote:
> Thanks so much for the help on this.
>
>> [sudo] gem install rspec --prerelease
>
> This seemed to install version 1.2.8 not the 1.2.9.rc1 I was looking
> for.
What OS and ruby/rubygems version? The --prerelease flag is a fairly
recent addition and m
Thanks so much for the help on this.
> [sudo] gem install rspec --prerelease
This seemed to install version 1.2.8 not the 1.2.9.rc1 I was looking
for.
>
> if you clone the git rep, just install it w/ the gem command:
>
> rake gem
> [sudo] gem install pkg/rspec-1.2.9.rc1.gem
This way did the tric
Thanks so much for the help on this.
> [sudo] gem install rspec --prerelease
This seemed to install version 1.2.8 not the 1.2.9.rc1 I was looking
for.
>
> if you clone the git rep, just install it w/ the gem command:
>
> rake gem
> [sudo] gem install pkg/rspec-1.2.9.rc1.gem
This way did the tric
Thanks so much for the help on this.
> [sudo] gem install rspec --prerelease
This seemed to install version 1.2.8 not the 1.2.9.rc1 I was looking
for.
>
> if you clone the git rep, just install it w/ the gem command:
>
> rake gem
> [sudo] gem install pkg/rspec-1.2.9.rc1.gem
This way did the tric
On Wed, Sep 23, 2009 at 12:16 PM, DanS wrote:
> I'm trying to install rspec so I can work with the new book chapter.
> This what the console shows after running "rake install_gem"
>
> Successfully built RubyGem
> Name: rspec
> Version: 1.2.9.rc1
> File: rspec-1.2.9.rc1.gem
> mv rspec-1.2.9.rc1
I'm trying to install rspec so I can work with the new book chapter.
This what the console shows after running "rake install_gem"
Successfully built RubyGem
Name: rspec
Version: 1.2.9.rc1
File: rspec-1.2.9.rc1.gem
mv rspec-1.2.9.rc1.gem pkg/rspec-1.2.9.rc1.gem
sudo gem install bmabey-fake
14 matches
Mail list logo
