Re: Sprout error

[Luke Bayes]

Just got had a discussion off list, that I thought I'd forward it to
be sure everyone saw it.

------------------------------

> I've been using sprouts for a while now, and I went update to see if
> sprouts had been updated for air, It was to my suprose but when I
> installed the update things broke.
>
> I've had problems that you helped me through before so I I wanted to
> see if this was caused by the same issues as before before I submited
> any bugs.
>
> The following are the errors I've got.
> >
> C:\SVN\TLBflash>gem install sprout
> Select which gem to install for your platform (i386-mswin32)
> 1. sprout 0.7.167 (ruby)
> 2. sprout 0.7.167 (x86-linux)
> 3. sprout 0.7.167 (darwin)
> 4. sprout 0.7.167 (mswin32)
> 5. Skip this gem
> 6. Cancel installation
> > 1
> Successfully installed sprout-0.7.167
> Installing ri documentation for sprout-0.7.167...
> Installing RDoc documentation for sprout-0.7.167...
> C:\SVN\TLBflash>cd c:\tmp
> C:\tmp>sprout -n as2 SomeProject
> C:/Program Files/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in
> `gem_original_require': no such file to load -- rubygems/digest/md5
> (LoadError)
> from C:/Program
> Files/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in
> `require'
> from C:/Program
> Files/ruby/lib/ruby/gems/1.8/gems/sprout-0.7.167/lib/sprout.rb:29
> from C:/Program
> Files/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in
> `gem_original_require'
> from C:/Program
> Files/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:32:in
> `require'
> from C:/Program
> Files/ruby/lib/ruby/gems/1.8/gems/sprout-0.7.167/bin/sprout:13
> from C:/Program Files/ruby/bin/sprout:16:in `load'
> from C:/Program Files/ruby/bin/sprout:16
> C:\tmp>

> Signed, Anonymous Sprout User

------------------------------

Ouch!

My first suspicion is that this is caused by an older version of RubyGems.

I've been building and testing with the latest version (1.0.1).

I'll file a bug to look further into this, but to get you up and
running, you should be able to update RubyGems and get productive
again.

Just run:

gem update --system

Thanks!

Luke Bayes

---------------------------------

OK -

I just filed this as a bug:

http://code.google.com/p/projectsprouts/issues/detail?id=119

You can subscribe by starring the bug and you'll be notified when it gets fixed.

If you get a chance, please change the status to 'verified' after I
mark it as 'Fixed' - if you get a build that actually addresses the
issue.

Thanks,

Luke Bayes