Bug #8037
rdoc issues preventing docs generating after ruby was compiled
| Status: | Assigned | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assignee: |  Eric Hodel | ||
| ruby -v: | 2.0.0 | Backport: | 1.9.3: DONTNEED, 2.0.0: REQUIRED |
Description
I have reported two issues for rdoc but there was no response, forwarding here as ruby is involved:
Thanks, Michal
History
#1
Updated by Tomoyuki Chikanaga almost 2 years ago
- Tracker changed from Backport to Bug
- Project changed from Backport200 to Ruby trunk
- Status changed from Open to Assigned
- Assignee set to Eric Hodel
#2
Updated by Zachary Scott almost 2 years ago
- Status changed from Assigned to Closed
- ruby -v set to 2.0.0
These issues seemed to have been resolved in the RDoc tracker, please update the ticket there if you still experience this issue. Thank you!
#3
Updated by Michal Papis almost 2 years ago
it's fixed in rdoc but not in ruby, ruby-2.0.0-p195 is still shipped with the broken rdoc 4.0.0
#4
Updated by Michal Papis over 1 year ago
this is still not fixed in https://github.com/ruby/ruby/blob/ruby_2_0_0/lib/rdoc.rb#L67 any chance in backporting it to ruby 2.0.0?
#5
Updated by Marcus Stollsteimer over 1 year ago
This has been fixed in rdoc 4.0.1, but trunk and ruby_2_0_0 still use rdoc 4.0.0, apparently. Could they be updated?
#6
Updated by Zachary Scott over 1 year ago
@stomar That's up to Eric, could you open a backport ticket?
#7
Updated by Marcus Stollsteimer over 1 year ago
Sorry, I don't understand. Why backport? If I'm not wrong, trunk still uses rdoc 4.0.0, too.
Update: See #8613.
#8
Updated by Zachary Scott over 1 year ago
- Category set to lib
- Status changed from Closed to Assigned
- Backport set to 1.9.3: DONTNEED, 2.0.0: REQUIRED
@stomar Oops, you are correct!
I think Eric is working on another release of RDoc, so hopefully he can merge soon.