Forum: Ruby-core [ruby-trunk - Bug #5659][Open] bug releasing a gem created with rails 3.1

Dcf6cccdbca2194b2cfcf470d99096f2?d=identicon&s=25 Vinicius G. (vinicius_g)
on 2011-11-22 13:27
(Received via mailing list)
Issue #5659 has been reported by Vinicius Gati.

----------------------------------------
Bug #5659: bug releasing a gem created with rails 3.1
http://redmine.ruby-lang.org/issues/5659

Author: Vinicius Gati
Status: Open
Priority: Normal
Assignee:
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
E7cff3cfd41c495e1012227d7dc24202?d=identicon&s=25 Luis Lavena (luislavena)
on 2011-11-22 16:13
(Received via mailing list)
Issue #5659 has been updated by Luis Lavena.


From what it appears to be, SSL was involved in the crash.

Can you reproduce this against releases 1.9.3-p0?

Can you verify against which version of OpenSSL your Ruby installation
linked against? If was 0.9.8 please try installing OpenSSL 1.0.0 and
rebuild your Ruby to link against it.

----------------------------------------
Bug #5659: bug releasing a gem created with rails 3.1
http://redmine.ruby-lang.org/issues/5659

Author: Vinicius Gati
Status: Open
Priority: Normal
Assignee:
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
E7cff3cfd41c495e1012227d7dc24202?d=identicon&s=25 Luis Lavena (luislavena)
on 2011-11-22 16:19
(Received via mailing list)
Issue #5659 has been updated by Luis Lavena.

Status changed from Open to Feedback


----------------------------------------
Bug #5659: bug releasing a gem created with rails 3.1
http://redmine.ruby-lang.org/issues/5659

Author: Vinicius Gati
Status: Feedback
Priority: Normal
Assignee:
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
Dcf6cccdbca2194b2cfcf470d99096f2?d=identicon&s=25 Vinicius G. (vinicius_g)
on 2011-11-22 19:14
(Received via mailing list)
Issue #5659 has been updated by Vinicius Gati.


I updated the gist with the 1.9.3-p0

$ openssl version
OpenSSL 1.0.0e 6 Sep 2011

Luis Lavena wrote:
> From what it appears to be, SSL was involved in the crash.
>
> Can you reproduce this against releases 1.9.3-p0?
>
> Can you verify against which version of OpenSSL your Ruby installation linked
against? If was 0.9.8 please try installing OpenSSL 1.0.0 and rebuild your Ruby 
to
link against it.


----------------------------------------
Bug #5659: bug releasing a gem created with rails 3.1
http://redmine.ruby-lang.org/issues/5659

Author: Vinicius Gati
Status: Feedback
Priority: Normal
Assignee:
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
Dcf6cccdbca2194b2cfcf470d99096f2?d=identicon&s=25 Vinicius G. (vinicius_g)
on 2011-11-29 22:13
(Received via mailing list)
Issue #5659 has been updated by Vinicius Gati.


I paste the 1.9.3-p0 bug in another gist

https://gist.github.com/1406528
----------------------------------------
Bug #5659: bug releasing a gem created with rails 3.1
http://redmine.ruby-lang.org/issues/5659

Author: Vinicius Gati
Status: Feedback
Priority: Normal
Assignee:
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
E7cff3cfd41c495e1012227d7dc24202?d=identicon&s=25 Luis Lavena (luislavena)
on 2011-11-29 22:27
(Received via mailing list)
Issue #5659 has been updated by Luis Lavena.


Vinicius Gati wrote:
> I updated the gist with the 1.9.3-p0 log error
>
> $ openssl version
> OpenSSL 1.0.0e 6 Sep 2011
>

:connect errors can be caused by OpenSSL.

Having that version of OpenSSL in your system, are you sure is the same
Ruby is built against?

Please do:

$ ruby -v -ropenssl -e "puts OpenSSL::OPENSSL_VERSION"

Just to be sure.

I don't see in the output you provided "Pushing gem..." legend. Are you
sure the gem is being pushed to rubygems.org and no RUBYGEMS_HOST
environment variable is being set?

----------------------------------------
Bug #5659: bug releasing a gem created with rails 3.1
http://redmine.ruby-lang.org/issues/5659

Author: Vinicius Gati
Status: Feedback
Priority: Normal
Assignee:
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
Dcf6cccdbca2194b2cfcf470d99096f2?d=identicon&s=25 Vinicius G. (vinicius_g)
on 2011-12-03 14:14
(Received via mailing list)
Issue #5659 has been updated by Vinicius Gati.


$ ruby -v -ropenssl -e "puts OpenSSL::OPENSSL_VERSION"
ruby 1.9.3dev (2011-10-11 revision 33457) [x86_64-darwin11.2.0]
OpenSSL 1.0.0e 6 Sep 2011
----------------------------------------
Bug #5659: bug releasing a gem created with rails 3.1
http://redmine.ruby-lang.org/issues/5659

Author: Vinicius Gati
Status: Feedback
Priority: Normal
Assignee:
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
Dcf6cccdbca2194b2cfcf470d99096f2?d=identicon&s=25 Vinicius G. (vinicius_g)
on 2011-12-03 14:40
(Received via mailing list)
Issue #5659 has been updated by Vinicius Gati.


[viniciusgati] ~/Code/ruby/testes
$ cd test_rb_bug/

[viniciusgati] ~/Code/ruby/testes/test_rb_bug (master)
$ rvm use 1.9.2
Using /Users/viniciusgati/.rvm/gems/ruby-1.9.2-p290

[viniciusgati] ~/Code/ruby/testes/test_rb_bug (master)
$ rvm list

rvm rubies

=> ruby-1.9.2-p290 [ i386 ]
   ruby-1.9.3-head [ x86_64 ]
   ruby-1.9.3-p0 [ x86_64 ]


[viniciusgati] ~/Code/ruby/testes/test_rb_bug (master)
$ rake release
Could not find activesupport-3.1.3 in any of the sources
Run `bundle install` to install missing gems.

[viniciusgati] ~/Code/ruby/testes/test_rb_bug (master)
$ bundle
Fetching source index for http://rubygems.org/
Using rake (0.9.2.2)
Using multi_json (1.0.3)
Installing activesupport (3.1.3)
Using builder (3.0.0)
Using i18n (0.6.0)
Installing activemodel (3.1.3)
Using erubis (2.7.0)
Using rack (1.3.5)
Using rack-cache (1.1)
Using rack-mount (0.8.3)
Using rack-test (0.6.1)
Using hike (1.2.1)
Using tilt (1.3.3)
Using sprockets (2.0.3)
Installing actionpack (3.1.3)
Using mime-types (1.17.2)
Using polyglot (0.3.3)
Using treetop (1.4.10)
Using mail (2.3.0)
Installing actionmailer (3.1.3)
Using arel (2.2.1)
Using tzinfo (0.3.31)
Installing activerecord (3.1.3)
Installing activeresource (3.1.3)
Using bundler (1.0.21)
Using rack-ssl (1.3.2)
Using json (1.6.1)
Using rdoc (3.11)
Using thor (0.14.6)
Installing railties (3.1.3)
Using jquery-rails (1.0.18)
Installing rails (3.1.3)
Using sqlite3 (1.3.4)
Using test_rb_bug (0.0.1) from source at .
Your bundle is complete! Use `bundle show [gemname]` to see where a
bundled gem is installed.

[viniciusgati] ~/Code/ruby/testes/test_rb_bug (master)
$ rake release
test_rb_bug 0.0.1 built to pkg/test_rb_bug-0.0.1.gem
Tagged v0.0.1
Pushed git commits and tags
Pushed test_rb_bug 0.0.1 to rubygems.org

----------------------------------------
Bug #5659: bug releasing a gem created with rails 3.1
http://redmine.ruby-lang.org/issues/5659

Author: Vinicius Gati
Status: Feedback
Priority: Normal
Assignee:
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
F24ff61beb80aa5f13371aa22a35619c?d=identicon&s=25 mame (Yusuke Endoh) (Guest)
on 2012-10-30 17:42
(Received via mailing list)
Issue #5659 has been updated by mame (Yusuke Endoh).

Status changed from Feedback to Assigned
Assignee set to luislavena (Luis Lavena)

Luis, do you know the status?

--
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-32023

Author: viniciusgati (Vinicius Gati)
Status: Assigned
Priority: Normal
Assignee: luislavena (Luis Lavena)
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
E7cff3cfd41c495e1012227d7dc24202?d=identicon&s=25 Luis Lavena (luislavena)
on 2012-10-30 18:03
(Received via mailing list)
Issue #5659 has been updated by luislavena (Luis Lavena).

Assignee changed from luislavena (Luis Lavena) to mame (Yusuke Endoh)

mame (Yusuke Endoh) wrote:
> Luis, do you know the status?
>

No, I was unable to reproduce with any of my installed versions of Ruby.
----------------------------------------
Bug #5659: bug releasing a gem created with rails 3.1
https://bugs.ruby-lang.org/issues/5659#change-32028

Author: viniciusgati (Vinicius Gati)
Status: Assigned
Priority: Normal
Assignee: mame (Yusuke Endoh)
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
F24ff61beb80aa5f13371aa22a35619c?d=identicon&s=25 mame (Yusuke Endoh) (Guest)
on 2012-10-30 18:19
(Received via mailing list)
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
C004c7f4e637a1d63dc00c15f0d9e138?d=identicon&s=25 unknown (Guest)
on 2014-05-03 17:36
(Received via mailing list)
Issue #5659 has been updated by Sam Kottler.


@vincius do you get this error on the latest release? I can't reproduce
it on any of the machines I've got handy.

----------------------------------------
Bug #5659: bug releasing a gem created with rails 3.1
https://bugs.ruby-lang.org/issues/5659#change-46484

* Author: Vinicius Gati
* Status: Assigned
* Priority: Normal
* Assignee: Martin Bosslet
* Category:
* Target version:
* ruby -v: 1.9.3-head
* Backport:
----------------------------------------
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
This topic is locked and can not be replied to.