You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Rhett Sutphin (JIRA)" <ji...@apache.org> on 2009/11/30 18:38:20 UTC
[jira] Created: (BUILDR-351) Buildr's automatic gem installer does
not work if gemcutter is a source
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.5, 1.3.3
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.
[jira] Commented: (BUILDR-351) Buildr's automatic gem installer
does not work if gemcutter is a source
Posted by "Otto Hilska (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (BUILDR-351) Buildr's automatic gem installer
does not work if gemcutter is a source
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787217#action_12787217 ]
Alex Boisvert commented on BUILDR-351:
--------------------------------------
I can't reproduce this, and it looks like http://gemcutter.org/Marshal.4.8 has been updated.
Do you still have the same error?
> 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.
[jira] Commented: (BUILDR-351) Buildr's automatic gem installer
does not work if gemcutter is a source
Posted by "Rhett Sutphin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787569#action_12787569 ]
Rhett Sutphin commented on BUILDR-351:
--------------------------------------
Yes, that's what I'm seeing now, too.
> 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.
[jira] Commented: (BUILDR-351) Buildr's automatic gem installer
does not work if gemcutter is a source
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787219#action_12787219 ]
Alex Boisvert commented on BUILDR-351:
--------------------------------------
I'm now getting:
boisvert@smudge:~/tmp/buildr-gem$ b13 --trace
Bulk updating Gem source index for: http://gems.rubyforge.org/
Buildr aborted!
undefined method `gems' for #<Array:0xb760c928>
/usr/local/lib/site_ruby/1.8/rubygems/source_index.rb:410:in `update'
/usr/local/lib/site_ruby/1.8/rubygems/source_info_cache_entry.rb:42:in `refresh'
/usr/local/lib/site_ruby/1.8/rubygems/source_info_cache.rb:249:in `refresh'
/usr/local/lib/site_ruby/1.8/rubygems/source_info_cache.rb:242:in `each'
/usr/local/lib/site_ruby/1.8/rubygems/source_info_cache.rb:242:in `refresh'
/usr/local/lib/site_ruby/1.8/rubygems/source_info_cache.rb:41:in `cache'
/usr/local/lib/site_ruby/1.8/rubygems/source_info_cache.rb:78:in `search'
/home/boisvert/svn/buildr-trunk/lib/buildr/core/util.rb:129:in `install'
/home/boisvert/svn/buildr-trunk/lib/buildr/core/util.rb:129:in `map'
/home/boisvert/svn/buildr-trunk/lib/buildr/core/util.rb:129:in `install'
/home/boisvert/svn/buildr-trunk/lib/buildr/core/application.rb:407:in `load_gems'
/home/boisvert/svn/buildr-trunk/lib/buildr/core/application.rb:215:in `load_buildfile'
/home/boisvert/svn/buildr-trunk/lib/buildr/core/application.rb:502:in `standard_exception_handling'
/home/boisvert/svn/buildr-trunk/lib/buildr/core/application.rb:213:in `load_buildfile'
/home/boisvert/svn/buildr-trunk/lib/buildr/core/application.rb:137:in `run'
/home/boisvert/svn/buildr-trunk/lib/buildr/core/application.rb:502:in `standard_exception_handling'
/home/boisvert/svn/buildr-trunk/lib/buildr/core/application.rb:135:in `run'
/home/boisvert/svn/buildr-trunk/_buildr:29
> 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.