Fwd: Re: #5463: Koji tag for Ruby 2.0.0 / JRuby 1.7

[Vít Ondruch]

Hi everybody,

We obtained side tag for Ruby 2.0.0 rebuild. So these are steps which 
will follow:

1) Build rubypick
2) Merge my ruby-2.0 branch into master, update to the latest revision 
available in ruby_2_0_0 branch. I would like to ask you for a review of 
the spec. There are not all patches, namely the webrick test suite 
failure [1] (on the other hand, I did not met this issue recently).
3) Bootstrap RSpec
4) Bootstrap other test frameworks
5) Build all other libraries.

Please do not update your libraries or build them into the side tag 
during this period.

Please note that there might arise need to upgrade or fix your library 
to fix the compatibility or other build issues. If needed, I will do so.

If you don't want me to touch your packages, please speak out now.

And of course, any help with rebuild is appreciated, since the rebuild 
should be done before branching F19, it is roughly in 3 weeks.

I'll try to keep you informed about all steps I'll do.

Thank you

Vít

[1] https://bugs.ruby-lang.org/issues/6573

-------- Původní zpráva --------
Předmět: 	Re: #5463: Koji tag for Ruby 2.0.0 / JRuby 1.7
Datum: 	Wed, 20 Feb 2013 15:46:36 -0000
Od: 	Fedora Release Engineering 
Komu: 	undisclosed-recipients:;

#5463: Koji tag for Ruby 2.0.0 / JRuby 1.7
------------------------------+----------------------
   Reporter:  vondruch         |      Owner:  ausil
       Type:  task             |     Status:  assigned
  Milestone:  Fedora 19 Alpha  |  Component:  koji
Resolution:                   |   Keywords:
Blocked By:                   |   Blocking:
------------------------------+----------------------
Changes (by ausil):

* owner:  rel-eng@… => ausil
  * status:  new => assigned

Comment:

f19-ruby tag and target created,  you will need to do "fedpkg build
  --target=f19-ruby"  please let us know when you are done so we can merge
  it back in

[Mamoru TASAKA]

Vít Ondruch wrote, at 02/21/2013 01:03 AM +9:00:
> Hi everybody,
>
> We obtained side tag for Ruby 2.0.0 rebuild. So these are steps which will follow:
> Build rubypick
> Merge my ruby-2.0 branch into master, update to the latest revision available in
>
> ruby_2_0_0 branch. I would like to ask you for a review of the spec. There are not
> all patches, namely the webrick test suite failure [1] (on the other hand, I did not met this issue recently).
> 3) Bootstrap RSpec
> 4) Bootstrap other test frameworks
> 5) Build all other libraries.

Again you must fix rubygems_version or so. rpm treats
2.0.0.rc.2 is _higher_ than 2.0.0, so when rubygems is upgraded
to formal 2.0.0, rpm won't upgrade rubygems rpm (or so).

Regards,
Mamoru

[Vít Ondruch]

Dne 20.2.2013 23:08, Mamoru TASAKA napsal(a):
> Vít Ondruch wrote, at 02/21/2013 01:03 AM +9:00:
> > Hi everybody,
> >
> > We obtained side tag for Ruby 2.0.0 rebuild. So these are steps which 
> > will follow:
> > Build rubypick
> > Merge my ruby-2.0 branch into master, update to the latest
> >
> > revision available in
> > ruby_2_0_0 branch. I would like to ask you for a review of the spec. 
> > There are not
> > all patches, namely the webrick test suite failure [1] (on the other 
> > hand, I did not met this issue recently).
> > 3) Bootstrap RSpec
> > 4) Bootstrap other test frameworks
> > 5) Build all other libraries.
>
> Again you must fix rubygems_version or so. rpm treats
> 2.0.0.rc.2 is _higher_ than 2.0.0, so when rubygems is upgraded
> to formal 2.0.0, rpm won't upgrade rubygems rpm (or so).

I will. It should be already fixed in Ruby's trunk if I am not mistaken. 
I was a bit lazy ;)

Vit

[Mamoru TASAKA]

Vít Ondruch wrote, at 02/21/2013 01:03 AM +9:00:
> Hi everybody,
>
> We obtained side tag for Ruby 2.0.0 rebuild. So these are steps which will follow:
> Build rubypick
> Merge my ruby-2.0 branch into master, update to the latest revision available in ruby_2_0_0 branch. I would like to ask you for a review of the spec. There are not all patches, namely the webrick test suite failure [1] (on the other hand, I did not met this issue recently).
> Bootstrap RSpec
> Bootstrap other test frameworks
> Build all other libraries.

Also, while
https://fedoraproject.org/wiki/Features/Ruby_2.0.0
says "Requires rebuilding numerous packages that depend on ruby.
All these packages have to be updated to support new virtual provides.",
the following page
https://github.com/jruby/jruby/wiki/C-Extension-Alternatives
says jruby does not support C extensions at all and lots of
rubygems packages and ruby-based GUI programs contain / use
C extensions. Would you make it clear how to package these?
( https://fedoraproject.org/wiki/Features/JRuby_1.7#Scope
   does not seem useful )

Regards,
Mamoru

#5463: Koji tag for Ruby 2.0.0 / JRuby 1.7

[Bohuslav Kabrda]

----- Original Message -----
> Vít Ondruch wrote, at 02/21/2013 01:03 AM +9:00:
> > Hi everybody,
> >
> > We obtained side tag for Ruby 2.0.0 rebuild. So these are steps
> > which will follow:
> > Build rubypick
> > Merge my ruby-2.0 branch into master, update to the latest
> >
> > revision available in ruby_2_0_0 branch. I would like to ask you
> > for a review of the spec. There are not all patches, namely the
> > webrick test suite failure [1] (on the other hand, I did not met
> > this issue recently).
> > 3) Bootstrap RSpec
> > 4) Bootstrap other test frameworks
> > 5) Build all other libraries.
>
> Also, while
> https://fedoraproject.org/wiki/Features/Ruby_2.0.0
> says "Requires rebuilding numerous packages that depend on ruby.
> All these packages have to be updated to support new virtual
> provides.",
> the following page
> https://github.com/jruby/jruby/wiki/C-Extension-Alternatives
> says jruby does not support C extensions at all and lots of
> rubygems packages and ruby-based GUI programs contain / use
> C extensions. Would you make it clear how to package these?

Packaging these for MRI will stay the way it is (except for the general change in requiring ruby(release) instead of ruby(abi)).
Packaging for JRuby hasn't been sorted out yet completely, but here are the most important points:
- I don't consider packaging C extensions for JRuby supportable, so libraries with C extensions shouldn't be packaged for JRuby at all.
- Platform independent gems are shared between MRI and JRuby.
- There are currently no guidelines for packaging JRuby extension gems, so these won't reach F19. The target of creating these guidelines is F20.

Does that answer your questions?
Slavek.
> ( https://fedoraproject.org/wiki/Features/JRuby_1.7#Scope
>    does not seem useful )
>
> Regards,
> Mamoru

#5463: Koji tag for Ruby 2.0.0 / JRuby 1.7

[Michal Fojtik]

On 02/21, Bohuslav Kabrda wrote:
> ----- Original Message -----
> > Vít Ondruch wrote, at 02/21/2013 01:03 AM +9:00:
> > > Hi everybody,
> > >
> > > We obtained side tag for Ruby 2.0.0 rebuild. So these are steps
> > > which will follow:
> > > Build rubypick
> > > Merge my ruby-2.0 branch into master, update to the latest
> > >
> > > revision available in ruby_2_0_0 branch. I would like to ask you
> > > for a review of the spec. There are not all patches, namely the
> > > webrick test suite failure [1] (on the other hand, I did not met
> > > this issue recently).
> > > 3) Bootstrap RSpec
> > > 4) Bootstrap other test frameworks
> > > 5) Build all other libraries.
> >
> > Also, while
> > https://fedoraproject.org/wiki/Features/Ruby_2.0.0
> > says "Requires rebuilding numerous packages that depend on ruby.
> > All these packages have to be updated to support new virtual
> > provides.",
> > the following page
> > https://github.com/jruby/jruby/wiki/C-Extension-Alternatives
> > says jruby does not support C extensions at all and lots of
> > rubygems packages and ruby-based GUI programs contain / use
> > C extensions. Would you make it clear how to package these?
>
> Packaging these for MRI will stay the way it is (except for the general change in requiring ruby(release) instead of ruby(abi)).
> Packaging for JRuby hasn't been sorted out yet completely, but here are the most important points:
> I don't consider packaging C extensions for JRuby supportable, so libraries with C extensions shouldn't be packaged for JRuby at all.

What about gems like nokogiri that ships both C and Java extensions?
> Platform independent gems are shared between MRI and JRuby.
> There are currently no guidelines for packaging JRuby extension gems, so these won't reach F19. The target of creating these guidelines is F20.
>
> Does that answer your questions?
> Slavek.
> > ( https://fedoraproject.org/wiki/Features/JRuby_1.7#Scope
> >    does not seem useful )
> >
> > Regards,
> > Mamoru
>
> -- 
> Regards,
> Bohuslav "Slavek" Kabrda.
> _______________________________________________
> ruby-sig mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/ruby-sig

#5463: Koji tag for Ruby 2.0.0 / JRuby 1.7

[Bohuslav Kabrda]

----- Original Message -----
> On 02/21, Bohuslav Kabrda wrote:
> > ----- Original Message -----
> > > Vít Ondruch wrote, at 02/21/2013 01:03 AM +9:00:
> > > > Hi everybody,
> > > >
> > > > We obtained side tag for Ruby 2.0.0 rebuild. So these are steps
> > > > which will follow:
> > > > Build rubypick
> > > > Merge my ruby-2.0 branch into master, update to the latest
> > > >
> > > > revision available in ruby_2_0_0 branch. I would like to ask
> > > > you
> > > > for a review of the spec. There are not all patches, namely the
> > > > webrick test suite failure [1] (on the other hand, I did not
> > > > met
> > > > this issue recently).
> > > > 3) Bootstrap RSpec
> > > > 4) Bootstrap other test frameworks
> > > > 5) Build all other libraries.
> > >
> > > Also, while
> > > https://fedoraproject.org/wiki/Features/Ruby_2.0.0
> > > says "Requires rebuilding numerous packages that depend on ruby.
> > > All these packages have to be updated to support new virtual
> > > provides.",
> > > the following page
> > > https://github.com/jruby/jruby/wiki/C-Extension-Alternatives
> > > says jruby does not support C extensions at all and lots of
> > > rubygems packages and ruby-based GUI programs contain / use
> > > C extensions. Would you make it clear how to package these?
> >
> > Packaging these for MRI will stay the way it is (except for the
> > general change in requiring ruby(release) instead of ruby(abi)).
> > Packaging for JRuby hasn't been sorted out yet completely, but here
> > are the most important points:
> > I don't consider packaging C extensions for JRuby supportable, so
> >
> > libraries with C extensions shouldn't be packaged for JRuby at
> > all.
>
> What about gems like nokogiri that ships both C and Java extensions?

That relates to the third point. There will definitely be rules for packaging them, but not in F19, unfortunately. After some discussions with Vit, we have decided that we need better understanding of extension gems for both implementations and so we would like to take some more time to do things properly.
> > Platform independent gems are shared between MRI and JRuby.
> > There are currently no guidelines for packaging JRuby extension
> >
> > gems, so these won't reach F19. The target of creating these
> > guidelines is F20.
> >
> > Does that answer your questions?
> > Slavek.
> > > ( https://fedoraproject.org/wiki/Features/JRuby_1.7#Scope
> > >    does not seem useful )
> > >
> > > Regards,
> > > Mamoru
> >
> > --
> > Regards,
> > Bohuslav "Slavek" Kabrda.
> > _______________________________________________
> > ruby-sig mailing list
> > [e-mail]
> > https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
>
> --
> Michal Fojtik 
> Deltacloud API, CloudForms
> _______________________________________________
> ruby-sig mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/ruby-sig

#5463: Koji tag for Ruby 2.0.0 / JRuby 1.7

[Vít Ondruch]

Dne 21.2.2013 11:16, Bohuslav Kabrda napsal(a):
> ----- Original Message -----
> > On 02/21, Bohuslav Kabrda wrote:
> > > ----- Original Message -----
> > > > Vít Ondruch wrote, at 02/21/2013 01:03 AM +9:00:
> > > > > Hi everybody,
> > > > >
> > > > > We obtained side tag for Ruby 2.0.0 rebuild. So these are steps
> > > > > which will follow:
> > > > > Build rubypick
> > > > > Merge my ruby-2.0 branch into master, update to the latest
> > > > >
> > > > > revision available in ruby_2_0_0 branch. I would like to ask
> > > > > you
> > > > > for a review of the spec. There are not all patches, namely the
> > > > > webrick test suite failure [1] (on the other hand, I did not
> > > > > met
> > > > > this issue recently).
> > > > > 3) Bootstrap RSpec
> > > > > 4) Bootstrap other test frameworks
> > > > > 5) Build all other libraries.
> > > >
> > > > Also, while
> > > > https://fedoraproject.org/wiki/Features/Ruby_2.0.0
> > > > says "Requires rebuilding numerous packages that depend on ruby.
> > > > All these packages have to be updated to support new virtual
> > > > provides.",
> > > > the following page
> > > > https://github.com/jruby/jruby/wiki/C-Extension-Alternatives
> > > > says jruby does not support C extensions at all and lots of
> > > > rubygems packages and ruby-based GUI programs contain / use
> > > > C extensions. Would you make it clear how to package these?
> > >
> > > Packaging these for MRI will stay the way it is (except for the
> > > general change in requiring ruby(release) instead of ruby(abi)).
> > > Packaging for JRuby hasn't been sorted out yet completely, but here
> > > are the most important points:
> > > I don't consider packaging C extensions for JRuby supportable, so
> > >
> > > libraries with C extensions shouldn't be packaged for JRuby at
> > > all.
> >
> > What about gems like nokogiri that ships both C and Java extensions?
>
> That relates to the third point. There will definitely be rules for packaging them, but not in F19, unfortunately. After some discussions with Vit, we have decided that we need better understanding of extension gems for both implementations and so we would like to take some more time to do things properly.

As a workaround, you should be able to install nokogiri locally, using 
'jgem install nokogiri' or 'gem _jruby_ install'.

Actually we deferred this topic for next release, because there are 
multiple cases, such as:

* gem with c and jruby extensions
* only jruby gem

Which creates some weird scenarios and RPM/YUM are not capable enough to 
do everything right without compromises :/

Vít

[Vít Ondruch]

You can watch progress here: 
https://koji.fedoraproject.org/koji/builds?inherited=0&tagID=232&ord...

Vít