From: "mame (Yusuke Endoh)" <mame@...>
Date: 2012-10-31T02:18:53+09:00
Subject: [ruby-core:48620] [ruby-trunk - Bug #5659] bug releasing a gem created with rails 3.1


Issue #5659 has been updated by mame (Yusuke Endoh).

Assignee changed from mame (Yusuke Endoh) to MartinBosslet (Martin Bosslet)

luislavena (Luis Lavena) wrote:
> mame (Yusuke Endoh) wrote:
> > Luis, do you know the status?
> > 
> 
> No, I was unable to reproduce with any of my installed versions of Ruby.

Thanks.  Then, emboss, do you know?
The trace looks similar to #6886 which was closed as 3PI.
What do you think?

-- 
Yusuke Endoh <mame@tsg.ne.jp>
----------------------------------------
Bug #5659: bug releasing a gem created with rails 3.1
https://bugs.ruby-lang.org/issues/5659#change-32033

Author: viniciusgati (Vinicius Gati)
Status: Assigned
Priority: Normal
Assignee: MartinBosslet (Martin Bosslet)
Category: 
Target version: 
ruby -v: 1.9.3-head


I made a rails engine using rails 3.1

the steps i follow was :

i created the engine with rails new plugin test_rb_bug

then i updated the gemspec

then i created a git repo and pushed: https://github.com/viniciusgati/test_rb_bug

after that i do a rake release and got the error: https://gist.github.com/1383444 obs: this gist contains the machos crash report to

the gist is the error for the first gem when i found the error.

and i reproduced the same now with a fresh engine...

system: MacOS lion
rails: 3.1.3
ruby: 1.9.3-head
rvm: 1.8.6
rubygems 1.8.10






-- 
http://bugs.ruby-lang.org/