[
https://issues.apache.org/jira/browse/BUILDR-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13670195#comment-13670195
]
tom chiverton commented on BUILDR-580:
--------------------------------------
This is still broken today in the latest
http://files.rubyforge.vm.bytemark.co.uk/rubyinstaller/rubyinstaller-1.8.7-p371.exe
download, a year later, only now it is broken immediately, not by the gem
update.
> buildr gem not loading
> ----------------------
>
> Key: BUILDR-580
> URL: https://issues.apache.org/jira/browse/BUILDR-580
> Project: Buildr
> Issue Type: Bug
> Affects Versions: 1.4.5
> Environment: Window 7 64 bit
> Reporter: Jesse Tomlinson
> Assignee: Antoine Toulme
> Priority: Blocker
> Fix For: 1.4.7
>
>
> The install documentation says to "Be sure to install Ruby 1.8.6", but after
> installing that and running "gem update --system", that will give you an
> error saying it needs to have Ruby 1.8.7. After installing 1.8.7, doing the
> "gem update --system", installing buildr, and trying any command with
> "buildr" (i.e. "buildr --version", "buildr --help", "buildr") it give the
> following error:
> C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems.rb:926:in `report_activate_error':
> RubyGem version error: buildr(1.4.5 not >= 0) (Gem::LoadError)
> from C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems.rb:244:in
> `activate_dep'
> from C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems.rb:236:in `activate'
> from C:/Ruby187/lib/ruby/site_ruby/1.8/rubygems.rb:1307:in `gem'
> from C:/Ruby187/bin/buildr:18
> C:\>gem list
> *** LOCAL GEMS ***
> atoulme-Antwrap (0.7.1)
> builder (2.1.2)
> buildr (1.4.5 x86-mswin32)
> diff-lcs (1.1.2)
> highline (1.5.1)
> hoe (2.3.3)
> json_pure (1.4.3)
> minitar (0.5.3)
> net-sftp (2.0.4)
> net-ssh (2.0.23)
> rake (0.8.7)
> rjb (1.3.2 x86-mswin32-60)
> rspec (2.1.0)
> rspec-core (2.1.0)
> rspec-expectations (2.1.0)
> rspec-mocks (2.1.0)
> rubyforge (2.0.3)
> rubygems-update (1.7.2)
> rubyzip (0.9.4)
> xml-simple (1.0.12)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
