Bug 478973

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Would building 1.9.1 which is now considered stable by upstream be an option for you?

Geh, seemed to have replied on a cached page that still had 1.8.7 in the title ;-)

is it ASSIGNED ? or should I close it ?


-thanks-

I'm working on it to see what plans I can come up with. I guess ON_DEV would be the appropriate status for this bug.

Please add/upgrade, I've tried running Ruby-TclTk programs on the current release and every program crashes on linking a variable to a GUI.

This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Latest status is this fails to build on i?86. See https://koji.fedoraproject.org/koji/getfile?taskID=1766348&name=build.log for more details

(In reply to comment #8)
> Latest status is this fails to build on i?86. See
> https://koji.fedoraproject.org/koji/getfile?taskID=1766348&name=build.log for
> more details  

Please provide your srpm (from koji we cannot tell what srpm
you were trying to build)

This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

The Ruby SIG still working on some of the details, but a package can be found at http://www.kanarip.com/custom/f12-ruby/ or http://www.kanarip.com/custom/f13-ruby/

compat packages for ruby-1.8.6 should also be there (soon).

(In reply to comment #11)
> The Ruby SIG still working on some of the details, 
(Umm... I didn't know that there is Ruby SIG, I will be happy if
 fedora-ruby-list or so will open)

> http://www.kanarip.com/custom/f13-ruby/
Well, while I have not tested your srpm yet (but anyway thank you
for your work),
what I am concerned about for ruby19 is that while we already
have many rubygem based rpms, I am not sure if rubygem works with
ruby19. Currently there are some reports on rubyforge tracker
that rubygems don't work correctly with ruby19:
http://rubyforge.org/tracker/index.php?group_id=126&atid=575
So I am not sure if for F-13 we should make ruby19  default or we
should make ruby19 optional. Note that for F-13 python3 is to be introduced
as optional.
(For now I think that making ruby18 default for F-13 is safer, however
 in such case I think we should consider to use ruby187)

(In reply to comment #12)
> (In reply to comment #11)
> > The Ruby SIG still working on some of the details, 
> (Umm... I didn't know that there is Ruby SIG,

According to http://fedoraproject.org/wiki/SIGs/Ruby, you are a member so I'm going to assume you found it ;-)

> I will be happy if
>  fedora-ruby-list or so will open)
> 

The mailing list is at https://admin.fedoraproject.org/mailman/listinfo/ruby-sig

> > http://www.kanarip.com/custom/f13-ruby/
> Well, while I have not tested your srpm yet (but anyway thank you
> for your work),
> what I am concerned about for ruby19 is that while we already
> have many rubygem based rpms, I am not sure if rubygem works with
> ruby19. Currently there are some reports on rubyforge tracker
> that rubygems don't work correctly with ruby19:
> http://rubyforge.org/tracker/index.php?group_id=126&atid=575
> So I am not sure if for F-13 we should make ruby19  default or we
> should make ruby19 optional. Note that for F-13 python3 is to be introduced
> as optional.
> (For now I think that making ruby18 default for F-13 is safer, however
>  in such case I think we should consider to use ruby187)  

Part of our goal is to also make compat- packages available for older versions of Ruby. I'm now working on www.kanarip.com/custom/f12-ruby/ which has a functional ruby-1.9.1 package.

I'm still trying to figure out how this should work in the greater perspective, more info as I go along through the Ruby SIG mailing list

This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle.
Changing version to '13'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle.
Changing version to '13'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Eric Hodel (the maintainer of RubyGems) is planning on dropping Ruby 1.8.6 support from RubyGems 1.4.x (http://blog.segment7.net/articles/2010/04/23/ruby-1-8-6-policy). Fedora should be ready to move off of Ruby 1.8.6, onto either 1.8.7, 1.9.1 or 1.9.2.

(In reply to comment #16)

> Fedora should be ready to move off of Ruby 1.8.6, onto either 1.8.7, 1.9.1 or 1.9.2.

see http://fedoraproject.org/wiki/Features/Ruby_1.9.1

Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.

New Contents:
su -c 'yum --enablerepo=updates-testing update sharutils'.  You can provide

(In reply to comment #18)
> Technical note added. If any revisions are required, please edit the "Technical
> Notes" field
> accordingly. All revisions will be proofread by the Engineering Content
> Services team.
> 
> New Contents:
> su -c 'yum --enablerepo=updates-testing update sharutils'.  You can provide    

sorry, C&P fault.

Closed.

I'm sorry, I'm going to delete my bz count.