[
https://issues.apache.org/jira/browse/BUILDR-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794803#action_12794803
]
Otto Hilska commented on BUILDR-351:
------------------------------------
Somehow it seems that this problem is more on the rubygems side. I didn't have
time to investigate it any further, but looks like rubygems is using @gems
internally sometimes as a hash and sometimes as an array.
You could try doing the following change in rubygems/source_index.rb (line 410):
410c410
< @gems.replace(new_index.gems)
---
> @gems = Hash[*new_index.flatten]
> Buildr's automatic gem installer does not work if gemcutter is a source
> -----------------------------------------------------------------------
>
> Key: BUILDR-351
> URL: https://issues.apache.org/jira/browse/BUILDR-351
> Project: Buildr
> Issue Type: Bug
> Components: Core features
> Affects Versions: 1.3.3, 1.3.5
> Environment: OS X 10.5, system ruby 1.8.6, rubygems 1.3.5 (does not
> seem environment-specific, though)
> Reporter: Rhett Sutphin
>
> If you have gemcutter configured as a gem source and a reference to an
> non-installed gem in build.yaml, buildr's automatic gem installer fails with
> this error:
> $ buildr
> Buildr aborted!
> bad response Forbidden 403 (http://gemcutter.org/Marshal.4.8)
> /Library/Ruby/Gems/1.8/gems/buildr-1.3.5/lib/buildr/core/application.rb:215:in
> `load_buildfile'
> /Library/Ruby/Gems/1.8/gems/buildr-1.3.5/lib/buildr/core/application.rb:213:in
> `load_buildfile'
> Workaround: manually install any required gems.
> The page http://gemcutter.org/Marshal.4.8 says "please update your rubygems,"
> but this happens with the most recent rubygems installed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
