Opened 16 years ago
Closed 16 years ago
#18977 closed enhancement (fixed)
ruby19@1.9.1-p0 Bug #1163 - gem_prelude raise NoMethodError
| Reported by: | jonbrenner@… | Owned by: | febeling@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.7.0 |
| Keywords: | ruby19 gem_prelude nomethoderror | Cc: | |
| Port: | ruby19 |
Description
Ruby 1.9.1-p0 has a known bug in which an incorrect error breaks some code, notably Rails 2.3.2 generators. The attached portfile diff and patch corrects the issue.
Official ruby issue: http://redmine.ruby-lang.org/issues/show/1163
Attachments (2)
Change History (7)
Changed 16 years ago by jonbrenner@…
| Attachment: | gem_prelude_raise_right_error.patch added |
|---|
Changed 16 years ago by jonbrenner@…
| Attachment: | Portfile-ruby19.diff added |
|---|
comment:1 Changed 16 years ago by jmroot (Joshua Root)
| Owner: | changed from macports-tickets@… to febeling@… |
|---|
comment:2 Changed 16 years ago by febeling@…
comment:3 Changed 16 years ago by febeling@…
I cannot find this problem in the rails bug tracker, and I think it has to be discussed there first. Please link if you know where it is.
comment:4 Changed 16 years ago by (none)
| Milestone: | Port Enhancements |
|---|
Milestone Port Enhancements deleted
comment:5 Changed 16 years ago by febeling@…
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
This has been fixed upstream and is in p129.
Note: See
TracTickets for help on using
tickets.
I understand that it can be very annoying if something like this breaks the dominant web framework, but it is not obvious to me that this is a "known bug' in the sense that it has been acknowledged. This is what the ruby redmine entry looks like when you auto-translate it from japanese:
http://babelfish.yahoo.com/translate_url?doit=done&tt=url&intl=1&fr=bf-home&trurl=http%3A%2F%2Fredmine.ruby-lang.org%2Fissues%2Fshow%2F1163&lp=ja_en&btnTrUrl=Translate
Basically rubygems, part of standard library breaks some rails behaviour. You could also come to the conclusion, that this is a rails bug introduced by an incompatible change in stdlib. Anyway. I'll look for the rails bug tracker and see what it says.