Discussion:
rails 3.0.x in F15
Mohammed Morsi
2010-12-18 01:48:04 UTC
Permalink
Based on my discussions with the community and various parties that
have a vested interest in this, I feel that it is a good idea to move
the rubygem-rails packages to rails 3.0.x for F15 so that we don't get
left behind and stay up to date w/ the latest / greatest upstream releases.

Unfortunately this process isn't as simple as updating the 6 rails
packages (rails itself and the active/action* packages), there are many
various gems which will need to be updated as well to work with Rails 3.
Based on my findings w/ deltacloud [1], the update process itself isn't
so difficult, but some of the following gems will need to be updated in
Fedora for things to properly work. Most likely more will need to be as
well, these are just the ones that I've found, but conversely all of
these may not need to be updated, as I installed Rails 3 via gem which
pulled in the latest version of all these packages.

* rails, activesupport, activerecord, actionpack, activeresource, actionmailer - 2.3.8 -> 3.0.1 (mmorsi)
* compass - 0.8.17 -> 0.10.6 (mmorsi)
* cucumber - 0.9.0 -> 0.9.3 (kanarip, mfojtik, mkent, stahnma)
* erubis - 2.6.5 -> 2.6.6 (mkent)
* gherkin - 2.2.4 -> 2.2.9 (mfojtik)
* haml - 3.0.17 -> 3.0.23 (mkent, kanarip)
* polyglot - 0.2.5 -> 0.3.1 (kanarip, stahnma)
* rack - 1.1.0 -> 1.2.1 (kanarip, stahnma)
* rack-test - 0.5.4 -> 0.5.6 (mfojtik)
* rspec - 1.3.0 -> 2.0.1 (stahnma)
* simple-navigation - 3.0.0 -> 3.0.2 (mfojtik)
* sinatra - 1.0 -> 1.1.0 (mfojtik)
* sqlite3-ruby - 1.2.4 -> 1.3.2 (kanarip, stahnma)
* term-ansicolor - 1.0.3 -> 1.0.5 (hpejakle, mfojtik)
* thor - 0.13.6 -> 0.14.3 (mkent)
* treetop - 1.3.0 -> 1.4.8 (stahnma)


Also the following are new gems which will need to be packaged

* arel (1.0.1)
* autotest (4.4.2)
* bundler (1.0.3)
* database_cleaner (0.6.0)
* factory_girl_rails (1.0)
* i18n (0.4.2)
* mail (2.2.29)
* tilt (1.1)
* timecop (0.3.5)
* rack-mount (0.6.13)
* railties (3.0.1)
* rspec-core, rspec-expectations, rspec-mocks, rspec-rails (2.0.1)
* tzinfo (0.3.23)


In the upcoming weeks (most likely starting after the new year) I will
be looking to updating the rails packages themselves and coordinating
updates with the owners of these gems. I also think it might be a good
idea to submit a feature request for Fedora 15 for Rails 3.

Thoughts, comments, and help with any and all of this would be very much
appreciated. Thanks alot.

-Mo

[1] http://mo.morsi.org/blog/node/331
Mamoru Tasaka
2010-12-18 07:12:45 UTC
Permalink
Hello, Mohammed:

First of all, thank you for analyzing what to be done for rails 3.0.
Post by Mohammed Morsi
Based on my discussions with the community and various parties that
have a vested interest in this, I feel that it is a good idea to move
the rubygem-rails packages to rails 3.0.x for F15 so that we don't get
left behind and stay up to date w/ the latest / greatest upstream releases.
Unfortunately this process isn't as simple as updating the 6 rails
packages (rails itself and the active/action* packages), there are many
various gems which will need to be updated as well to work with Rails 3.
Based on my findings w/ deltacloud [1], the update process itself isn't
so difficult, but some of the following gems will need to be updated in
Fedora for things to properly work. Most likely more will need to be as
well, these are just the ones that I've found, but conversely all of
these may not need to be updated, as I installed Rails 3 via gem which
pulled in the latest version of all these packages.
* rails, activesupport, activerecord, actionpack, activeresource, actionmailer - 2.3.8 -> 3.0.1 (mmorsi)
* compass - 0.8.17 -> 0.10.6 (mmorsi)
* cucumber - 0.9.0 -> 0.9.3 (kanarip, mfojtik, mkent, stahnma)
* erubis - 2.6.5 -> 2.6.6 (mkent)
* gherkin - 2.2.4 -> 2.2.9 (mfojtik)
* haml - 3.0.17 -> 3.0.23 (mkent, kanarip)
* polyglot - 0.2.5 -> 0.3.1 (kanarip, stahnma)
* rack - 1.1.0 -> 1.2.1 (kanarip, stahnma)
* rack-test - 0.5.4 -> 0.5.6 (mfojtik)
* rspec - 1.3.0 -> 2.0.1 (stahnma)
- rspec 1.3.0 and rspec 2.0.1 have large difference, and it seems that
many packages depends on rspec 1.3.0 (I may be wrong). So maybe we want
to package rspec 2.0.1 as rubygem-rspec-2 (correct me if I am wrong).
Also please check bug650283
Post by Mohammed Morsi
* simple-navigation - 3.0.0 -> 3.0.2 (mfojtik)
* sinatra - 1.0 -> 1.1.0 (mfojtik)
* sqlite3-ruby - 1.2.4 -> 1.3.2 (kanarip, stahnma)
* term-ansicolor - 1.0.3 -> 1.0.5 (hpejakle, mfojtik)
* thor - 0.13.6 -> 0.14.3 (mkent)
https://bugzilla.redhat.com/show_bug.cgi?id=649028
Post by Mohammed Morsi
* treetop - 1.3.0 -> 1.4.8 (stahnma)
I hope these won't be too difficult.
Post by Mohammed Morsi
Also the following are new gems which will need to be packaged
* arel (1.0.1)
* autotest (4.4.2)
- I have local srpm and if needed I guess I can submit
review request for rubygem-autotest quickly
Post by Mohammed Morsi
* bundler (1.0.3)
https://bugzilla.redhat.com/show_bug.cgi?id=646836
- blocked by bug 649028 (update thor to 0.14.x)
Post by Mohammed Morsi
* database_cleaner (0.6.0)
https://bugzilla.redhat.com/show_bug.cgi?id=641957
- blocked by bundler review request
Post by Mohammed Morsi
* factory_girl_rails (1.0)
- already in Fedora
Post by Mohammed Morsi
* i18n (0.4.2)
- already in Fedora
Post by Mohammed Morsi
* mail (2.2.29)
* tilt (1.1)
* timecop (0.3.5)
- already in Fedora
Post by Mohammed Morsi
* rack-mount (0.6.13)
* railties (3.0.1)
* rspec-core, rspec-expectations, rspec-mocks, rspec-rails (2.0.1)
https://bugzilla.redhat.com/show_bug.cgi?id=650280
https://bugzilla.redhat.com/show_bug.cgi?id=650282
https://bugzilla.redhat.com/show_bug.cgi?id=650283
(all submitted by me), will check rspec-rails
Post by Mohammed Morsi
* tzinfo (0.3.23)
In the upcoming weeks (most likely starting after the new year) I will
be looking to updating the rails packages themselves and coordinating
updates with the owners of these gems. I also think it might be a good
idea to submit a feature request for Fedora 15 for Rails 3.
Thoughts, comments, and help with any and all of this would be very much
appreciated. Thanks alot.
-Mo
[1] http://mo.morsi.org/blog/node/331
Regards,
Mamoru
Mamoru Tasaka
2010-12-18 10:21:03 UTC
Permalink
Post by Mamoru Tasaka
Post by Mohammed Morsi
* factory_girl_rails (1.0)
- already in Fedora
Oops, factory_girl is, but factory_girl_rails is not.

Mamoru
Mohammed Morsi
2010-12-21 03:15:23 UTC
Permalink
Post by Mamoru Tasaka
First of all, thank you for analyzing what to be done for rails 3.0.
No problem. Appreciate your feedback / comments.
Post by Mamoru Tasaka
Post by Mohammed Morsi
Based on my discussions with the community and various parties that
have a vested interest in this, I feel that it is a good idea to move
the rubygem-rails packages to rails 3.0.x for F15 so that we don't get
left behind and stay up to date w/ the latest / greatest upstream releases.
Unfortunately this process isn't as simple as updating the 6 rails
packages (rails itself and the active/action* packages), there are many
various gems which will need to be updated as well to work with Rails 3.
Based on my findings w/ deltacloud [1], the update process itself isn't
so difficult, but some of the following gems will need to be updated in
Fedora for things to properly work. Most likely more will need to be as
well, these are just the ones that I've found, but conversely all of
these may not need to be updated, as I installed Rails 3 via gem which
pulled in the latest version of all these packages.
* rails, activesupport, activerecord, actionpack, activeresource, actionmailer - 2.3.8 -> 3.0.1 (mmorsi)
* compass - 0.8.17 -> 0.10.6 (mmorsi)
* cucumber - 0.9.0 -> 0.9.3 (kanarip, mfojtik, mkent, stahnma)
* erubis - 2.6.5 -> 2.6.6 (mkent)
* gherkin - 2.2.4 -> 2.2.9 (mfojtik)
* haml - 3.0.17 -> 3.0.23 (mkent, kanarip)
* polyglot - 0.2.5 -> 0.3.1 (kanarip, stahnma)
* rack - 1.1.0 -> 1.2.1 (kanarip, stahnma)
* rack-test - 0.5.4 -> 0.5.6 (mfojtik)
* rspec - 1.3.0 -> 2.0.1 (stahnma)
- rspec 1.3.0 and rspec 2.0.1 have large difference, and it seems that
many packages depends on rspec 1.3.0 (I may be wrong). So maybe we want
to package rspec 2.0.1 as rubygem-rspec-2 (correct me if I am wrong).
Also please check bug650283
I would be fine w/ this, but would like to make sure it needs to be done
before we create a new package as doing so involves more work. Perhaps
instead we can convince the maintainers of the dependent gems to update
their packages
Post by Mamoru Tasaka
<snip>
Thanks for the rest of your feedback, going over it, it seems that
updating to Rails 3.0.x seems doable, even if it involves a bit of work.
At least it doesn't seem like there won't be any major blockers as we
get this ball rolling (famous last words, might find some when we
actually do this). In the upcoming days/weeks look for update requests
in bugzilla as well as preliminary Rails 3 packages here.

-Mo
Mohammed Morsi
2010-12-21 03:18:02 UTC
Permalink
Post by Mamoru Tasaka
<snip>
Post by Mamoru Tasaka
- rspec 1.3.0 and rspec 2.0.1 have large difference, and it seems that
many packages depends on rspec 1.3.0 (I may be wrong). So maybe we want
to package rspec 2.0.1 as rubygem-rspec-2 (correct me if I am wrong).
Also please check bug650283
I would be fine w/ this, but would like to make sure it needs to be done
before we create a new package as doing so involves more work. Perhaps
instead we can convince the maintainers of the dependent gems to update
their packages
$ repoquery --whatrequires rubygem-rspec
rubygem-rspec-0:1.3.0-2.fc13.noarch
rubygem-merb-core-0:1.0.15-1.fc13.noarch
rubygem-rack-restful_submit-0:1.1.1-1.fc13.noarch


Unless I missed something (does --whatrequires query the
BuildRequires?), it doesn't seem too bad. So long as we ensure those
packages work with the new rspec, we should be good.

-Mo
Mamoru Tasaka
2010-12-21 06:55:03 UTC
Permalink
Post by Mohammed Morsi
Post by Mamoru Tasaka
<snip>
Post by Mamoru Tasaka
- rspec 1.3.0 and rspec 2.0.1 have large difference, and it seems that
many packages depends on rspec 1.3.0 (I may be wrong). So maybe we want
to package rspec 2.0.1 as rubygem-rspec-2 (correct me if I am wrong).
Also please check bug650283
I would be fine w/ this, but would like to make sure it needs to be done
before we create a new package as doing so involves more work. Perhaps
instead we can convince the maintainers of the dependent gems to update
their packages
$ repoquery --whatrequires rubygem-rspec
rubygem-rspec-0:1.3.0-2.fc13.noarch
rubygem-merb-core-0:1.0.15-1.fc13.noarch
rubygem-rack-restful_submit-0:1.1.1-1.fc13.noarch
Unless I missed something (does --whatrequires query the
BuildRequires?), it doesn't seem too bad. So long as we ensure those
packages work with the new rspec, we should be good.
-Mo
I guess rubygem-rspec is used usually for %check and not needed
on runtime.
For srpm / BuildRequires check, some different usage is needed and

# repoquery --archlist=src --disablerepo=\* --enablerepo=rawhide-source --whatrequires 'rubygem(rspec)' | sort
rubygem-bcrypt-ruby-0:2.1.2-2.fc15.src
rubygem-boxgrinder-build-0:0.7.0-1.fc15.src
rubygem-boxgrinder-build-fedora-os-plugin-0:0.0.6-1.fc15.src
rubygem-boxgrinder-build-local-delivery-plugin-0:0.0.6-1.fc15.src
rubygem-boxgrinder-build-rpm-based-os-plugin-0:0.0.9-1.fc15.src
rubygem-boxgrinder-build-vmware-platform-plugin-0:0.0.6-1.fc15.src
rubygem-boxgrinder-core-0:0.1.5-1.fc15.src
rubygem-commander-0:4.0.3-3.fc15.src
rubygem-cucumber-0:0.9.0-4.fc15.src
rubygem-cucumber-rails-0:0.3.2-5.fc15.src
rubygem-extlib-0:0.9.13-5.fc13.src
rubygem-facon-0:0.4.1-2.fc15.src
rubygem-factory_girl-0:1.3.2-3.fc15.src
rubygem-ffi-0:0.6.3-1.fc14.src
rubygem-linode-0:0.6.2-1.fc15.src
rubygem-mixlib-authentication-0:1.1.2-2.fc14.src
rubygem-mixlib-cli-0:1.1.0-3.fc14.src
rubygem-mixlib-config-0:1.1.0-4.fc14.src
rubygem-mixlib-log-0:1.1.0-3.fc14.src
rubygem-mustache-0:0.11.2-4.fc15.src
rubygem-ohai-0:0.5.0-1.fc14.src
rubygem-rack-restful_submit-0:1.1.2-1.fc15.src
rubygem-rack-test-0:0.5.4-1.fc15.src
rubygem-rake-compiler-0:0.7.5-2.fc15.src
rubygem-rerun-0:0.5.2-3.fc15.src
rubygem-scruffy-0:0.2.6-2.fc15.src
rubygem-simple-navigation-0:3.0.0-3.fc15.src
rubygem-stomp-0:1.1.6-1.fc15.src
rubygem-templater-0:1.0.0-1.fc13.src
rubygem-thin-0:1.2.7-1.fc15.src
rubygem-typhoeus-0:0.1.31-3.fc15.src
rubygem-uuidtools-0:2.1.1-1.fc14.src
rubygem-yard-0:0.5.3-3.fc14.src

Regards,
Mamoru
Mohammed Morsi
2010-12-29 02:25:33 UTC
Permalink
OK thanks for this Mamoru, I appended the packager(s) onto each
package so we know who to bug to update. I will try to get to updating
and sending out the rails package this week but am on time off and have
alot of other things going on, so it might not get to it. If not next
week (and year!) I'll get to this and will start syncing the various
update efforts.

-Mo
Post by Mamoru Tasaka
# repoquery --archlist=src --disablerepo=\* --enablerepo=rawhide-source --whatrequires 'rubygem(rspec)' | sort
rubygem-bcrypt-ruby-0:2.1.2-2.fc15.src (mmorsi)
rubygem-boxgrinder-build-0:0.7.0-1.fc15.src (goldmann)
rubygem-boxgrinder-build-fedora-os-plugin-0:0.0.6-1.fc15.src (goldmann)
rubygem-boxgrinder-build-local-delivery-plugin-0:0.0.6-1.fc15.src (goldmann)
rubygem-boxgrinder-build-rpm-based-os-plugin-0:0.0.9-1.fc15.src (goldmann)
rubygem-boxgrinder-build-vmware-platform-plugin-0:0.0.6-1.fc15.src (goldmann)
rubygem-boxgrinder-core-0:0.1.5-1.fc15.src (goldmann)
rubygem-commander-0:4.0.3-3.fc15.src (mfojtik)
rubygem-cucumber-0:0.9.0-4.fc15.src (kanarip, mfojtik, mkent, stahnma)
rubygem-cucumber-rails-0:0.3.2-5.fc15.src (mfojtik)
rubygem-extlib-0:0.9.13-5.fc13.src (mkent)
rubygem-facon-0:0.4.1-2.fc15.src (stahnma)
rubygem-factory_girl-0:1.3.2-3.fc15.src (mfojtik)
rubygem-ffi-0:0.6.3-1.fc14.src (bkearny)
rubygem-linode-0:0.6.2-1.fc15.src (stahnma)
rubygem-mixlib-authentication-0:1.1.2-2.fc14.src (mkent)
rubygem-mixlib-cli-0:1.1.0-3.fc14.src (mkent)
rubygem-mixlib-config-0:1.1.0-4.fc14.src (mkent)
rubygem-mixlib-log-0:1.1.0-3.fc14.src (mkent)
rubygem-mustache-0:0.11.2-4.fc15.src (jzigmund)
rubygem-ohai-0:0.5.0-1.fc14.src (mkent)
rubygem-rack-restful_submit-0:1.1.2-1.fc15.src (jzigmund)
rubygem-rack-test-0:0.5.4-1.fc15.src (mfojtik)
rubygem-rake-compiler-0:0.7.5-2.fc15.src (mtasaka)
rubygem-rerun-0:0.5.2-3.fc15.src (mfojtik)
rubygem-scruffy-0:0.2.6-2.fc15.src (mmorsi)
rubygem-simple-navigation-0:3.0.0-3.fc15.src (mfojtik)
rubygem-stomp-0:1.1.6-1.fc15.src (stahnma)
rubygem-templater-0:1.0.0-1.fc13.src (mkent)
rubygem-thin-0:1.2.7-1.fc15.src (mfojtik)
rubygem-typhoeus-0:0.1.31-3.fc15.src (mfojtik)
rubygem-uuidtools-0:2.1.1-1.fc14.src (mkent)
rubygem-yard-0:0.5.3-3.fc14.src (mmorsi)
Vít Ondruch
2011-01-07 16:04:51 UTC
Permalink
Post by Mamoru Tasaka
First of all, thank you for analyzing what to be done for rails 3.0.
Post by Mohammed Morsi
Based on my discussions with the community and various parties that
have a vested interest in this, I feel that it is a good idea to move
the rubygem-rails packages to rails 3.0.x for F15 so that we don't get
left behind and stay up to date w/ the latest / greatest upstream releases.
Unfortunately this process isn't as simple as updating the 6 rails
packages (rails itself and the active/action* packages), there are many
various gems which will need to be updated as well to work with Rails 3.
Based on my findings w/ deltacloud [1], the update process itself isn't
so difficult, but some of the following gems will need to be updated in
Fedora for things to properly work. Most likely more will need to be as
well, these are just the ones that I've found, but conversely all of
these may not need to be updated, as I installed Rails 3 via gem which
pulled in the latest version of all these packages.
* rails, activesupport, activerecord, actionpack, activeresource, actionmailer - 2.3.8 -> 3.0.1 (mmorsi)
* compass - 0.8.17 -> 0.10.6 (mmorsi)
* cucumber - 0.9.0 -> 0.9.3 (kanarip, mfojtik, mkent, stahnma)
* erubis - 2.6.5 -> 2.6.6 (mkent)
* gherkin - 2.2.4 -> 2.2.9 (mfojtik)
* haml - 3.0.17 -> 3.0.23 (mkent, kanarip)
* polyglot - 0.2.5 -> 0.3.1 (kanarip, stahnma)
* rack - 1.1.0 -> 1.2.1 (kanarip, stahnma)
* rack-test - 0.5.4 -> 0.5.6 (mfojtik)
* rspec - 1.3.0 -> 2.0.1 (stahnma)
- rspec 1.3.0 and rspec 2.0.1 have large difference, and it seems that
many packages depends on rspec 1.3.0 (I may be wrong). So maybe we want
to package rspec 2.0.1 as rubygem-rspec-2 (correct me if I am wrong).
Also please check bug650283
Post by Mohammed Morsi
* simple-navigation - 3.0.0 -> 3.0.2 (mfojtik)
* sinatra - 1.0 -> 1.1.0 (mfojtik)
* sqlite3-ruby - 1.2.4 -> 1.3.2 (kanarip, stahnma)
* term-ansicolor - 1.0.3 -> 1.0.5 (hpejakle, mfojtik)
* thor - 0.13.6 -> 0.14.3 (mkent)
https://bugzilla.redhat.com/show_bug.cgi?id=649028
Post by Mohammed Morsi
* treetop - 1.3.0 -> 1.4.8 (stahnma)
I hope these won't be too difficult.
Post by Mohammed Morsi
Also the following are new gems which will need to be packaged
* arel (1.0.1)
* autotest (4.4.2)
- I have local srpm and if needed I guess I can submit
review request for rubygem-autotest quickly
Post by Mohammed Morsi
* bundler (1.0.3)
https://bugzilla.redhat.com/show_bug.cgi?id=646836
- blocked by bug 649028 (update thor to 0.14.x)
Post by Mohammed Morsi
* database_cleaner (0.6.0)
https://bugzilla.redhat.com/show_bug.cgi?id=641957
- blocked by bundler review request
Post by Mohammed Morsi
* factory_girl_rails (1.0)
- already in Fedora
Post by Mohammed Morsi
* i18n (0.4.2)
- already in Fedora
Post by Mohammed Morsi
* mail (2.2.29)
* tilt (1.1)
* timecop (0.3.5)
- already in Fedora
Post by Mohammed Morsi
* rack-mount (0.6.13)
I have prepared "rack-mount" if somebody is interested:
https://bugzilla.redhat.com/show_bug.cgi?id=667997

Vit
Post by Mamoru Tasaka
Post by Mohammed Morsi
* railties (3.0.1)
* rspec-core, rspec-expectations, rspec-mocks, rspec-rails (2.0.1)
https://bugzilla.redhat.com/show_bug.cgi?id=650280
https://bugzilla.redhat.com/show_bug.cgi?id=650282
https://bugzilla.redhat.com/show_bug.cgi?id=650283
(all submitted by me), will check rspec-rails
Post by Mohammed Morsi
* tzinfo (0.3.23)
In the upcoming weeks (most likely starting after the new year) I will
be looking to updating the rails packages themselves and coordinating
updates with the owners of these gems. I also think it might be a good
idea to submit a feature request for Fedora 15 for Rails 3.
Thoughts, comments, and help with any and all of this would be very much
appreciated. Thanks alot.
-Mo
[1] http://mo.morsi.org/blog/node/331
Regards,
Mamoru
_______________________________________________
ruby-sig mailing list
ruby-sig at lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
Minnikhanov
2011-01-07 21:11:42 UTC
Permalink
Post by Mamoru Tasaka
First of all, thank you for analyzing what to be done for rails 3.0.
Post by Mohammed Morsi
Based on my discussions with the community and various parties that
have a vested interest in this, I feel that it is a good idea to move
the rubygem-rails packages to rails 3.0.x for F15 so that we don't get
left behind and stay up to date w/ the latest / greatest upstream releases.
Also the following are new gems which will need to be packaged
* railties (3.0.1)
Hi. I have prepared "railties" (3.0.3). Check it, please.
https://bugzilla.redhat.com/show_bug.cgi?id=668090
Post by Mamoru Tasaka
Regards,
Mamoru
_______________________________________________
ruby-sig mailing list
ruby-sig at lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
Best regards.
Minnikhanov
2011-01-07 21:56:02 UTC
Permalink
Post by Mamoru Tasaka
First of all, thank you for analyzing what to be done for rails 3.0.
Post by Mohammed Morsi
Based on my discussions with the community and various parties that
have a vested interest in this, I feel that it is a good idea to move
the rubygem-rails packages to rails 3.0.x for F15 so that we don't get
left behind and stay up to date w/ the latest / greatest upstream releases.
Also the following are new gems which will need to be packaged
* tzinfo (0.3.23)
Hi. I have prepared "tzinfo" (0.3.23). Check it, please.
https://bugzilla.redhat.com/show_bug.cgi?id=668098
Post by Mamoru Tasaka
Regards,
Mamoru
_______________________________________________
ruby-sig mailing list
ruby-sig at lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
Best regards.
Vít Ondruch
2011-02-16 15:52:59 UTC
Permalink
* rspec - 1.3.0 -> 2.0.1 (stahnma)
Post by Mamoru Tasaka
- rspec 1.3.0 and rspec 2.0.1 have large difference, and it seems that
many packages depends on rspec 1.3.0 (I may be wrong). So maybe we want
to package rspec 2.0.1 as rubygem-rspec-2 (correct me if I am wrong).
Also please check bug650283
Post by Mohammed Morsi
* rspec-core, rspec-expectations, rspec-mocks, rspec-rails (2.0.1)
https://bugzilla.redhat.com/show_bug.cgi?id=650280
https://bugzilla.redhat.com/show_bug.cgi?id=650282
https://bugzilla.redhat.com/show_bug.cgi?id=650283
(all submitted by me), will check rspec-rails
Could we push this forward? Can I help somehow? It is quite late for F15
unfortunately, is it wort of trying? RSpec 1.3 are not very useful for
Rails 3 IMO.


Vit
Michal Fojtik
2011-02-16 16:00:11 UTC
Permalink
Post by Mohammed Morsi
* rspec - 1.3.0 -> 2.0.1 (stahnma)
Post by Mamoru Tasaka
- rspec 1.3.0 and rspec 2.0.1 have large difference, and it seems that
many packages depends on rspec 1.3.0 (I may be wrong). So maybe we want
to package rspec 2.0.1 as rubygem-rspec-2 (correct me if I am wrong).
Also please check bug650283
Post by Mohammed Morsi
* rspec-core, rspec-expectations, rspec-mocks, rspec-rails (2.0.1)
https://bugzilla.redhat.com/show_bug.cgi?id=650280
https://bugzilla.redhat.com/show_bug.cgi?id=650282
https://bugzilla.redhat.com/show_bug.cgi?id=650283
(all submitted by me), will check rspec-rails
Could we push this forward? Can I help somehow? It is quite late for F15
unfortunately, is it wort of trying? RSpec 1.3 are not very useful for
Rails 3 IMO.
Keep in mind that many packages are using 1.3 tests which are in some way
incompatible with 2.0, so before pushing this be sure it will not break all
builds which are using 1.3 ;-)


-- Michal
Post by Mohammed Morsi
Vit
_______________________________________________
ruby-sig mailing list
ruby-sig at lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
--
--------------------------------------------------------
Michal Fojtik, mfojtik at redhat.com
Deltacloud API: http://deltacloud.org
--------------------------------------------------------
Michael Stahnke
2011-02-16 16:14:15 UTC
Permalink
Post by Michal Fojtik
* rspec ? ? ? ? - ?1.3.0 ? ?-> ? ?2.0.1 ?(stahnma)
Post by Mamoru Tasaka
- rspec 1.3.0 and rspec 2.0.1 have large difference, and it seems that
? ? many packages depends on rspec 1.3.0 (I may be wrong). So maybe we want
? ? to package rspec 2.0.1 as rubygem-rspec-2 (correct me if I am wrong).
? ? Also please check bug650283
Post by Mohammed Morsi
* rspec-core, rspec-expectations, rspec-mocks, rspec-rails (2.0.1)
https://bugzilla.redhat.com/show_bug.cgi?id=650280
https://bugzilla.redhat.com/show_bug.cgi?id=650282
https://bugzilla.redhat.com/show_bug.cgi?id=650283
(all submitted by me), will check rspec-rails
Could we push this forward? Can I help somehow? It is quite late for F15
unfortunately, is it wort of trying? RSpec 1.3 are not very useful for
Rails 3 IMO.
Keep in mind that many packages are using 1.3 tests which are in some way
incompatible with 2.0, so before pushing this be sure it will not break all
builds which are using 1.3 ;-)
?-- Michal
Vit
_______________________________________________
ruby-sig mailing list
ruby-sig at lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
--
--------------------------------------------------------
Michal Fojtik, mfojtik at redhat.com
Deltacloud API: http://deltacloud.org
--------------------------------------------------------
_______________________________________________
ruby-sig mailing list
ruby-sig at lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
We may want to look at doing rspec2 as a new package. Lots of things
are still using rspec 1.x, specifically many gems not related to
rails. I should probably do some research on this and see how many
are left on 1.x.

Either way, I'll see if I can get a scratch build of rspec 2 going.
I'm also completely willing to give co-maintainer rights to anybody
who wishes to help out.

stahnma
Mamoru Tasaka
2011-02-16 16:40:37 UTC
Permalink
Post by Michael Stahnke
Post by Michal Fojtik
* rspec - 1.3.0 -> 2.0.1 (stahnma)
Post by Mamoru Tasaka
- rspec 1.3.0 and rspec 2.0.1 have large difference, and it seems that
many packages depends on rspec 1.3.0 (I may be wrong). So maybe we want
to package rspec 2.0.1 as rubygem-rspec-2 (correct me if I am wrong).
Also please check bug650283
Post by Mohammed Morsi
* rspec-core, rspec-expectations, rspec-mocks, rspec-rails (2.0.1)
https://bugzilla.redhat.com/show_bug.cgi?id=650280
https://bugzilla.redhat.com/show_bug.cgi?id=650282
https://bugzilla.redhat.com/show_bug.cgi?id=650283
(all submitted by me), will check rspec-rails
Could we push this forward? Can I help somehow? It is quite late for F15
unfortunately, is it wort of trying? RSpec 1.3 are not very useful for
Rails 3 IMO.
Keep in mind that many packages are using 1.3 tests which are in some way
incompatible with 2.0, so before pushing this be sure it will not break all
builds which are using 1.3 ;-)
-- Michal
Vit
_______________________________________________
ruby-sig mailing list
ruby-sig at lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
We may want to look at doing rspec2 as a new package. Lots of things
are still using rspec 1.x, specifically many gems not related to
rails. I should probably do some research on this and see how many
are left on 1.x.
Either way, I'll see if I can get a scratch build of rspec 2 going.
I'm also completely willing to give co-maintainer rights to anybody
who wishes to help out.
stahnma
First, I will update the above 3 review requests (to use version 2.5.0).

Note that rspec-{core,expectations,mocks} 2.x can be installed in parallel with
rspec 1.3.0 (even in rpm form). Only rspec 2.x has to be renamed as rubygem-rspec2
(for example), or rubygem-rspec1 srpm has to be newly imported.

Regards,
Mamoru
Vít Ondruch
2011-02-17 07:57:28 UTC
Permalink
Post by Mamoru Tasaka
Post by Michael Stahnke
Post by Michal Fojtik
* rspec - 1.3.0 -> 2.0.1 (stahnma)
Post by Mamoru Tasaka
- rspec 1.3.0 and rspec 2.0.1 have large difference, and it seems that
many packages depends on rspec 1.3.0 (I may be wrong). So maybe we want
to package rspec 2.0.1 as rubygem-rspec-2 (correct me if I am wrong).
Also please check bug650283
Post by Mohammed Morsi
* rspec-core, rspec-expectations, rspec-mocks, rspec-rails (2.0.1)
https://bugzilla.redhat.com/show_bug.cgi?id=650280
https://bugzilla.redhat.com/show_bug.cgi?id=650282
https://bugzilla.redhat.com/show_bug.cgi?id=650283
(all submitted by me), will check rspec-rails
Could we push this forward? Can I help somehow? It is quite late for F15
unfortunately, is it wort of trying? RSpec 1.3 are not very useful for
Rails 3 IMO.
Keep in mind that many packages are using 1.3 tests which are in some way
incompatible with 2.0, so before pushing this be sure it will not break all
builds which are using 1.3 ;-)
I know. And I keep it in mind. It seems there is currently 42 packages
that depends on RSpec. That is why I am a bit afraid of pushing them to F15.
Post by Mamoru Tasaka
Post by Michael Stahnke
Post by Michal Fojtik
-- Michal
Vit
_______________________________________________
ruby-sig mailing list
ruby-sig at lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
We may want to look at doing rspec2 as a new package. Lots of things
are still using rspec 1.x, specifically many gems not related to
rails. I should probably do some research on this and see how many
are left on 1.x.
Well since we upgraded Rails 3 without fallback, I am fan of upgrading
RSpec without fallback. Anything else complicates maintenance in the
future. Moreover, I have packaged some packages (bundler, delayed_job)
which have specs written in RSpec2 and they could be with minor effort
executed by RSpec1 without any issues. So I hope also the opposite
direction should not be big issue. In theory, it should be even easier.
Post by Mamoru Tasaka
Post by Michael Stahnke
Either way, I'll see if I can get a scratch build of rspec 2 going.
I'm also completely willing to give co-maintainer rights to anybody
who wishes to help out.
stahnma
First, I will update the above 3 review requests (to use version 2.5.0).
Note that rspec-{core,expectations,mocks} 2.x can be installed in parallel with
rspec 1.3.0 (even in rpm form). Only rspec 2.x has to be renamed as rubygem-rspec2
(for example), or rubygem-rspec1 srpm has to be newly imported.
Thank you. I'll do rspec-rails once these gems are packaged.

Vit
Vít Ondruch
2011-02-17 07:59:35 UTC
Permalink
Post by Vít Ondruch
Well since we upgraded Rails 3 without fallback, I am fan of upgrading
RSpec without fallback. Anything else complicates maintenance in the
future.
At least we should try it I mean.


Vit
Mamoru Tasaka
2011-02-18 20:40:11 UTC
Permalink
* rspec - 1.3.0 -> 2.0.1 (stahnma)
Post by Mamoru Tasaka
- rspec 1.3.0 and rspec 2.0.1 have large difference, and it seems that
many packages depends on rspec 1.3.0 (I may be wrong). So maybe we want
to package rspec 2.0.1 as rubygem-rspec-2 (correct me if I am wrong).
Also please check bug650283
Post by Mohammed Morsi
* rspec-core, rspec-expectations, rspec-mocks, rspec-rails (2.0.1)
https://bugzilla.redhat.com/show_bug.cgi?id=650280
https://bugzilla.redhat.com/show_bug.cgi?id=650282
https://bugzilla.redhat.com/show_bug.cgi?id=650283
(all submitted by me), will check rspec-rails
Could we push this forward? Can I help somehow? It is quite late for F15
unfortunately, is it wort of trying? RSpec 1.3 are not very useful for
Rails 3 IMO.
Now I've updated these 3 review requests (now using 2.5.x).
Review swaps welcomed.

Regards,
Mamoru
Vít Ondruch
2011-02-23 12:37:26 UTC
Permalink
Post by Mamoru Tasaka
Now I've updated these 3 review requests (now using 2.5.x).
Review swaps welcomed.
Regards,
Mamoru
_______________________________________________
ruby-sig mailing list
ruby-sig at lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
Ok, so I did the reviews. I expect that these packages will be pushed
into the rawhide soon. After that, I propose following steps:

1) Update the rubygem-rspec to rspec 2.5.0 in rawhide
2) Fix every gem which depends on rspec in rawhide (see the list below)
3) Backport into F15

Vit



[vondruch at dhcp-25-1 ~]$ repoquery --archlist=src --disablerepo=\*
--enablerepo=rawhide-source --whatrequires 'rubygem(rspec)' | sort | wc -l
42
[vondruch at dhcp-25-1 ~]$ repoquery --archlist=src --disablerepo=\*
--enablerepo=rawhide-source --whatrequires 'rubygem(rspec)' | sort
rubygem-bcrypt-ruby-0:2.1.2-2.fc15.src
rubygem-boxgrinder-build-ebs-delivery-plugin-0:0.0.4-2.fc15.src
rubygem-boxgrinder-build-ec2-platform-plugin-0:0.0.8-2.fc15.src
rubygem-boxgrinder-build-fedora-os-plugin-0:0.0.6-2.fc15.src
rubygem-boxgrinder-build-local-delivery-plugin-0:0.0.6-2.fc15.src
rubygem-boxgrinder-build-rpm-based-os-plugin-0:0.0.10-2.fc15.src
rubygem-boxgrinder-build-sftp-delivery-plugin-0:0.0.5-2.fc15.src
rubygem-boxgrinder-build-s3-delivery-plugin-0:0.0.5-2.fc15.src
rubygem-boxgrinder-build-vmware-platform-plugin-0:0.0.6-2.fc15.src
rubygem-boxgrinder-build-0:0.7.1-2.fc15.src
rubygem-boxgrinder-core-0:0.1.5-2.fc15.src
rubygem-commander-0:4.0.3-4.fc15.src
rubygem-cucumber-rails-0:0.3.2-5.fc15.src
rubygem-cucumber-0:0.10.0-5.fc15.src
rubygem-extlib-0:0.9.13-5.fc13.src
rubygem-facon-0:0.4.1-2.fc15.src
rubygem-factory_girl-0:1.3.2-3.fc15.src
rubygem-ffi-0:0.6.3-2.fc15.src
rubygem-fssm-0:0.2.2-4.fc15.src
rubygem-linode-0:0.6.2-1.fc15.src
rubygem-mail-0:2.2.15-2.fc15.src
rubygem-mixlib-authentication-0:1.1.2-2.fc14.src
rubygem-mixlib-cli-0:1.1.0-3.fc14.src
rubygem-mixlib-config-0:1.1.0-4.fc14.src
rubygem-mixlib-log-0:1.1.0-3.fc14.src
rubygem-multimap-0:1.1.2-3.fc15.src
rubygem-mustache-0:0.11.2-5.fc15.src
rubygem-ohai-0:0.5.0-1.fc14.src
rubygem-rack-restful_submit-0:1.1.2-2.fc15.src
rubygem-rack-test-0:0.5.4-1.fc15.src
rubygem-rake-compiler-0:0.7.6-2.fc15.src
rubygem-regin-0:0.3.7-3.fc15.src
rubygem-rerun-0:0.5.2-4.fc15.src
rubygem-scruffy-0:0.2.6-2.fc15.src
rubygem-simple-navigation-0:3.0.0-3.fc15.src
rubygem-stomp-0:1.1.6-2.fc15.src
rubygem-templater-0:1.0.0-1.fc13.src
rubygem-thin-0:1.2.7-2.fc15.src
rubygem-typhoeus-0:0.2.0-2.fc15.src
rubygem-uuidtools-0:2.1.1-1.fc14.src
rubygem-warden-0:1.0.3-4.fc15.src
rubygem-yard-0:0.5.3-3.fc14.src
Marek Goldmann
2011-03-05 16:11:54 UTC
Permalink
Hi all,

As a side note for RSpec2...

Pushed rubygem-rake-0.9.0-0.1.beta.0.fc15 to F15 breaks the integration with RSpec 1.3.0 which is currently the latest RSpec version in F15. The required file was renamed:

https://github.com/jimweirich/rake/commit/321178d888ecbce99a1ef3bfad80324e30f4c469#diff-4

Should we:

1. Push 1.3.x package with patch?
2. Push 2.5.x now?

I created a small patch [1] and a diff [2] for 1.3.0. This also upgrades it to 1.3.1.

[1] https://gist.github.com/856469
[2] https://gist.github.com/856471

--Marek
Post by Vít Ondruch
Post by Mamoru Tasaka
Now I've updated these 3 review requests (now using 2.5.x).
Review swaps welcomed.
Regards,
Mamoru
_______________________________________________
ruby-sig mailing list
ruby-sig at lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
Ok, so I did the reviews. I expect that these packages will be pushed
1) Update the rubygem-rspec to rspec 2.5.0 in rawhide
2) Fix every gem which depends on rspec in rawhide (see the list below)
3) Backport into F15
Vit
[vondruch at dhcp-25-1 ~]$ repoquery --archlist=src --disablerepo=\*
--enablerepo=rawhide-source --whatrequires 'rubygem(rspec)' | sort | wc -l
42
[vondruch at dhcp-25-1 ~]$ repoquery --archlist=src --disablerepo=\*
--enablerepo=rawhide-source --whatrequires 'rubygem(rspec)' | sort
rubygem-bcrypt-ruby-0:2.1.2-2.fc15.src
rubygem-boxgrinder-build-ebs-delivery-plugin-0:0.0.4-2.fc15.src
rubygem-boxgrinder-build-ec2-platform-plugin-0:0.0.8-2.fc15.src
rubygem-boxgrinder-build-fedora-os-plugin-0:0.0.6-2.fc15.src
rubygem-boxgrinder-build-local-delivery-plugin-0:0.0.6-2.fc15.src
rubygem-boxgrinder-build-rpm-based-os-plugin-0:0.0.10-2.fc15.src
rubygem-boxgrinder-build-sftp-delivery-plugin-0:0.0.5-2.fc15.src
rubygem-boxgrinder-build-s3-delivery-plugin-0:0.0.5-2.fc15.src
rubygem-boxgrinder-build-vmware-platform-plugin-0:0.0.6-2.fc15.src
rubygem-boxgrinder-build-0:0.7.1-2.fc15.src
rubygem-boxgrinder-core-0:0.1.5-2.fc15.src
rubygem-commander-0:4.0.3-4.fc15.src
rubygem-cucumber-rails-0:0.3.2-5.fc15.src
rubygem-cucumber-0:0.10.0-5.fc15.src
rubygem-extlib-0:0.9.13-5.fc13.src
rubygem-facon-0:0.4.1-2.fc15.src
rubygem-factory_girl-0:1.3.2-3.fc15.src
rubygem-ffi-0:0.6.3-2.fc15.src
rubygem-fssm-0:0.2.2-4.fc15.src
rubygem-linode-0:0.6.2-1.fc15.src
rubygem-mail-0:2.2.15-2.fc15.src
rubygem-mixlib-authentication-0:1.1.2-2.fc14.src
rubygem-mixlib-cli-0:1.1.0-3.fc14.src
rubygem-mixlib-config-0:1.1.0-4.fc14.src
rubygem-mixlib-log-0:1.1.0-3.fc14.src
rubygem-multimap-0:1.1.2-3.fc15.src
rubygem-mustache-0:0.11.2-5.fc15.src
rubygem-ohai-0:0.5.0-1.fc14.src
rubygem-rack-restful_submit-0:1.1.2-2.fc15.src
rubygem-rack-test-0:0.5.4-1.fc15.src
rubygem-rake-compiler-0:0.7.6-2.fc15.src
rubygem-regin-0:0.3.7-3.fc15.src
rubygem-rerun-0:0.5.2-4.fc15.src
rubygem-scruffy-0:0.2.6-2.fc15.src
rubygem-simple-navigation-0:3.0.0-3.fc15.src
rubygem-stomp-0:1.1.6-2.fc15.src
rubygem-templater-0:1.0.0-1.fc13.src
rubygem-thin-0:1.2.7-2.fc15.src
rubygem-typhoeus-0:0.2.0-2.fc15.src
rubygem-uuidtools-0:2.1.1-1.fc14.src
rubygem-warden-0:1.0.3-4.fc15.src
rubygem-yard-0:0.5.3-3.fc14.src
_______________________________________________
ruby-sig mailing list
ruby-sig at lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
Mamoru Tasaka
2011-03-06 17:28:31 UTC
Permalink
Post by Marek Goldmann
Hi all,
As a side note for RSpec2...
https://github.com/jimweirich/rake/commit/321178d888ecbce99a1ef3bfad80324e30f4c469#diff-4
1. Push 1.3.x package with patch?
2. Push 2.5.x now?
I created a small patch [1] and a diff [2] for 1.3.0. This also upgrades it to 1.3.1.
[1] https://gist.github.com/856469
[2] https://gist.github.com/856471
--Marek
For now I have incorporated your fixes into Fedora's rubygem-rspec (1.x) to unbreak
things anyway, thank you.

Regards,
Mamoru

Ohad Levy
2010-12-19 09:18:45 UTC
Permalink
Post by Mohammed Morsi
* rack - 1.1.0 -> 1.2.1 (kanarip, stahnma)
* sinatra - 1.0 -> 1.1.0 (mfojtik)
afaik, these two version are not working together[1].

Ohad

[1] - http://lists.fedoraproject.org/pipermail/ruby-sig/2010-September/000310.html
Mamoru Tasaka
2010-12-19 09:33:09 UTC
Permalink
Post by Ohad Levy
Post by Mohammed Morsi
* rack - 1.1.0 -> 1.2.1 (kanarip, stahnma)
* sinatra - 1.0 -> 1.1.0 (mfojtik)
afaik, these two version are not working together[1].
Ohad
[1] - http://lists.fedoraproject.org/pipermail/ruby-sig/2010-September/000310.html
My recognition is that these incompatibility came because
of the incompatibility between actionpack 2.3.5 vs rack 1.1.0
(so we patched against actionpack 2.3.5) [2]
actionpack 2.3.8 is compatible with rack 1.1.0 and now we are talking
about actionpack 3.0.x and rack 1.2.1 (although I myself have not tried
actionpack 3.0.x or rack 1.2.1)

[2] http://lists.fedoraproject.org/pipermail/ruby-sig/2010-September/000313.html

Regards,
Mamoru
Ohad Levy
2010-12-19 09:41:34 UTC
Permalink
Post by Mamoru Tasaka
My recognition is that these incompatibility came because
of the incompatibility between actionpack 2.3.5 vs rack 1.1.0
(so we patched against actionpack 2.3.5) [2]
actionpack 2.3.8 is compatible with rack 1.1.0 and now we are talking
about actionpack 3.0.x and rack 1.2.1 (although I myself have not tried
actionpack 3.0.x or rack 1.2.1)
[2] http://lists.fedoraproject.org/pipermail/ruby-sig/2010-September/000313.html
Maybe I'm wrong about this, but I remeber having this issue on ubuntu as well, googling shows its relevant for windows as well [3][4]
as far I can tell (from a very very quick look) The solution in [4] doesn't seem to be related to your patch

Thanks,
Ohad

[3] - http://ironruby.codeplex.com/workitem/5256
[4] - https://github.com/rack/rack/issues/issue/32
Mohammed Morsi
2010-12-21 03:15:33 UTC
Permalink
Post by Ohad Levy
Post by Mamoru Tasaka
My recognition is that these incompatibility came because
of the incompatibility between actionpack 2.3.5 vs rack 1.1.0
(so we patched against actionpack 2.3.5) [2]
actionpack 2.3.8 is compatible with rack 1.1.0 and now we are talking
about actionpack 3.0.x and rack 1.2.1 (although I myself have not tried
actionpack 3.0.x or rack 1.2.1)
[2] http://lists.fedoraproject.org/pipermail/ruby-sig/2010-September/000313.html
Maybe I'm wrong about this, but I remeber having this issue on ubuntu as well, googling shows its relevant for windows as well [3][4]
as far I can tell (from a very very quick look) The solution in [4] doesn't seem to be related to your patch
Thanks,
Ohad
[3] - http://ironruby.codeplex.com/workitem/5256
[4] - https://github.com/rack/rack/issues/issue/32
_______________________________________________
ruby-sig mailing list
ruby-sig at lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
It seems the fix in [4] has been applied to the upstream codebase, so if
this is still an issue in the released gem we can easily integrate a
patch fixing it.

-Mo
Vít Ondruch
2010-12-20 13:37:19 UTC
Permalink
Post by Mohammed Morsi
Based on my discussions with the community and various parties that
have a vested interest in this, I feel that it is a good idea to move
the rubygem-rails packages to rails 3.0.x for F15 so that we don't get
left behind and stay up to date w/ the latest / greatest upstream releases.
Unfortunately this process isn't as simple as updating the 6 rails
packages (rails itself and the active/action* packages), there are many
various gems which will need to be updated as well to work with Rails 3.
Based on my findings w/ deltacloud [1], the update process itself isn't
so difficult, but some of the following gems will need to be updated in
Fedora for things to properly work. Most likely more will need to be as
well, these are just the ones that I've found, but conversely all of
these may not need to be updated, as I installed Rails 3 via gem which
pulled in the latest version of all these packages.
* rails, activesupport, activerecord, actionpack, activeresource, actionmailer - 2.3.8 -> 3.0.1 (mmorsi)
* compass - 0.8.17 -> 0.10.6 (mmorsi)
* cucumber - 0.9.0 -> 0.9.3 (kanarip, mfojtik, mkent, stahnma)
* erubis - 2.6.5 -> 2.6.6 (mkent)
* gherkin - 2.2.4 -> 2.2.9 (mfojtik)
* haml - 3.0.17 -> 3.0.23 (mkent, kanarip)
* polyglot - 0.2.5 -> 0.3.1 (kanarip, stahnma)
* rack - 1.1.0 -> 1.2.1 (kanarip, stahnma)
* rack-test - 0.5.4 -> 0.5.6 (mfojtik)
* rspec - 1.3.0 -> 2.0.1 (stahnma)
* simple-navigation - 3.0.0 -> 3.0.2 (mfojtik)
* sinatra - 1.0 -> 1.1.0 (mfojtik)
* sqlite3-ruby - 1.2.4 -> 1.3.2 (kanarip, stahnma)
* term-ansicolor - 1.0.3 -> 1.0.5 (hpejakle, mfojtik)
* thor - 0.13.6 -> 0.14.3 (mkent)
* treetop - 1.3.0 -> 1.4.8 (stahnma)
Also the following are new gems which will need to be packaged
* arel (1.0.1)
I have prepared arel package here:
http://people.redhat.com/vondruch/rubygem-arel.spec
http://people.redhat.com/vondruch/rubygem-arel-2.0.6-1.fc14.src.rpm

But I did not submitted it for review yet, because:

1) It does not pass its own test suite (nevertheless the problem is
already fixed in upstream).
2) It is higher version than the one mentioned here, however, the arel
2.x should be backward compatible and much more performant.
Post by Mohammed Morsi
* autotest (4.4.2)
* bundler (1.0.3)
* database_cleaner (0.6.0)
* factory_girl_rails (1.0)
* i18n (0.4.2)
* mail (2.2.29)
* tilt (1.1)
* timecop (0.3.5)
* rack-mount (0.6.13)
* railties (3.0.1)
* rspec-core, rspec-expectations, rspec-mocks, rspec-rails (2.0.1)
* tzinfo (0.3.23)
In the upcoming weeks (most likely starting after the new year) I will
be looking to updating the rails packages themselves and coordinating
updates with the owners of these gems. I also think it might be a good
idea to submit a feature request for Fedora 15 for Rails 3.
Thoughts, comments, and help with any and all of this would be very much
appreciated. Thanks alot.
-Mo
[1] http://mo.morsi.org/blog/node/331
_______________________________________________
ruby-sig mailing list
ruby-sig at lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
Regards,

Vit
Mohammed Morsi
2010-12-21 03:15:53 UTC
Permalink
Post by Vít Ondruch
Post by Mohammed Morsi
Also the following are new gems which will need to be packaged
* arel (1.0.1)
http://people.redhat.com/vondruch/rubygem-arel.spec
http://people.redhat.com/vondruch/rubygem-arel-2.0.6-1.fc14.src.rpm
1) It does not pass its own test suite (nevertheless the problem is
already fixed in upstream).
2) It is higher version than the one mentioned here, however, the arel
2.x should be backward compatible and much more performant.
If issues have been fixed in the upstream codebase but have not made
their way into the released tarball / gem, feel free to add them as
patches in the RPM spec with a comment containing a link to the relevant
upstream commit / bug.

Also as you mentioned even if it a later version, so long as its
compatible we should be fine. I simply installed all these package via
'gem' and originally came up with this gem list a couple months back, so
some of the gems could have gone through several versions since then (as
it seems is the case w/ arel).

-Mo
Vít Ondruch
2011-01-07 16:06:43 UTC
Permalink
Post by Mohammed Morsi
Post by Vít Ondruch
Post by Mohammed Morsi
Also the following are new gems which will need to be packaged
* arel (1.0.1)
http://people.redhat.com/vondruch/rubygem-arel.spec
http://people.redhat.com/vondruch/rubygem-arel-2.0.6-1.fc14.src.rpm
1) It does not pass its own test suite (nevertheless the problem is
already fixed in upstream).
2) It is higher version than the one mentioned here, however, the arel
2.x should be backward compatible and much more performant.
If issues have been fixed in the upstream codebase but have not made
their way into the released tarball / gem, feel free to add them as
patches in the RPM spec with a comment containing a link to the relevant
upstream commit / bug.
Also as you mentioned even if it a later version, so long as its
compatible we should be fine. I simply installed all these package via
'gem' and originally came up with this gem list a couple months back, so
some of the gems could have gone through several versions since then (as
it seems is the case w/ arel).
-Mo
_______________________________________________
ruby-sig mailing list
ruby-sig at lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
Arel prepared for review: https://bugzilla.redhat.com/show_bug.cgi?id=667954


Vit
Minnikhanov
2010-12-23 19:37:12 UTC
Permalink
Post by Mohammed Morsi
Based on my discussions with the community and various parties that
have a vested interest in this, I feel that it is a good idea to move
the rubygem-rails packages to rails 3.0.x for F15 so that we don't get
left behind and stay up to date w/ the latest / greatest upstream releases.
Unfortunately this process isn't as simple as updating the 6 rails
packages (rails itself and the active/action* packages), there are many
various gems which will need to be updated as well to work with Rails 3.
Based on my findings w/ deltacloud [1], the update process itself isn't
so difficult, but some of the following gems will need to be updated in
Fedora for things to properly work. Most likely more will need to be as
well, these are just the ones that I've found, but conversely all of
these may not need to be updated, as I installed Rails 3 via gem which
pulled in the latest version of all these packages.
* rails, activesupport, activerecord, actionpack, activeresource, actionmailer - 2.3.8 -> 3.0.1 (mmorsi)
* compass - 0.8.17 -> 0.10.6 (mmorsi)
* cucumber - 0.9.0 -> 0.9.3 (kanarip, mfojtik, mkent, stahnma)
* erubis - 2.6.5 -> 2.6.6 (mkent)
* gherkin - 2.2.4 -> 2.2.9 (mfojtik)
* haml - 3.0.17 -> 3.0.23 (mkent, kanarip)
* polyglot - 0.2.5 -> 0.3.1 (kanarip, stahnma)
* rack - 1.1.0 -> 1.2.1 (kanarip, stahnma)
* rack-test - 0.5.4 -> 0.5.6 (mfojtik)
* rspec - 1.3.0 -> 2.0.1 (stahnma)
* simple-navigation - 3.0.0 -> 3.0.2 (mfojtik)
* sinatra - 1.0 -> 1.1.0 (mfojtik)
* sqlite3-ruby - 1.2.4 -> 1.3.2 (kanarip, stahnma)
* term-ansicolor - 1.0.3 -> 1.0.5 (hpejakle, mfojtik)
* thor - 0.13.6 -> 0.14.3 (mkent)
* treetop - 1.3.0 -> 1.4.8 (stahnma)
Also the following are new gems which will need to be packaged
* arel (1.0.1)
* autotest (4.4.2)
* bundler (1.0.3)
* database_cleaner (0.6.0)
* factory_girl_rails (1.0)
* i18n (0.4.2)
* mail (2.2.29)
May I'll prepare mail package?
Only I find ver. 2.2.13. https://rubygems.org/downloads/mail-2.2.13.gem
I made spec file and srpm, now polish they.
Google did't find for me rubygem mail ver.2.2.29.
Is anywhere link to mail (2.2.29)?

I make 1st Review Request:
rubygem-heroku - deploy apps to Heroku (Bug #661436).

Now I ready to prepare 2d Review Request:
rubygem-mail-2.2.13-1 - A Really Ruby Mail Library
Post by Mohammed Morsi
* tilt (1.1)
* timecop (0.3.5)
* rack-mount (0.6.13)
* railties (3.0.1)
* rspec-core, rspec-expectations, rspec-mocks, rspec-rails (2.0.1)
* tzinfo (0.3.23)
In the upcoming weeks (most likely starting after the new year) I will
be looking to updating the rails packages themselves and coordinating
updates with the owners of these gems. I also think it might be a good
idea to submit a feature request for Fedora 15 for Rails 3.
Thoughts, comments, and help with any and all of this would be very much
appreciated. Thanks alot.
-Mo
[1] http://mo.morsi.org/blog/node/331
_______________________________________________
ruby-sig mailing list
ruby-sig at lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
Best regards.
Mamoru Tasaka
2010-12-23 20:25:04 UTC
Permalink
Post by Minnikhanov
Post by Mohammed Morsi
Also the following are new gems which will need to be packaged
* arel (1.0.1)
* autotest (4.4.2)
* bundler (1.0.3)
* database_cleaner (0.6.0)
* factory_girl_rails (1.0)
* i18n (0.4.2)
* mail (2.2.29)
May I'll prepare mail package?
Only I find ver. 2.2.13. https://rubygems.org/downloads/mail-2.2.13.gem
I made spec file and srpm, now polish they.
Google did't find for me rubygem mail ver.2.2.29.
Is anywhere link to mail (2.2.29)?
mail does not seem to be packaged for Fedora yet so you can
package this for Fedora (and I cannot find mail 2.2.29 either).
Post by Minnikhanov
rubygem-heroku - deploy apps to Heroku (Bug #661436).
rubygem-mail-2.2.13-1 - A Really Ruby Mail Library
Regards,
Mamoru
Minnikhanov
2010-12-24 18:27:49 UTC
Permalink
Post by Mamoru Tasaka
Post by Minnikhanov
Post by Mohammed Morsi
Also the following are new gems which will need to be packaged
* mail (2.2.29)
May I'll prepare mail package?
Only I find ver. 2.2.13. https://rubygems.org/downloads/mail-2.2.13.gem
I made spec file and srpm, now polish they.
Google did't find for me rubygem mail ver.2.2.29.
Is anywhere link to mail (2.2.29)?
mail does not seem to be packaged for Fedora yet so you can
package this for Fedora (and I cannot find mail 2.2.29 either).
Post by Minnikhanov
rubygem-mail-2.2.13-1 - A Really Ruby Mail Library
Regards,
Mamoru
_______________________________________________
Hi.
Bug #665560 - Review Request: rubygem-mail - A Really Ruby Mail Library
https://bugzilla.redhat.com/show_bug.cgi?id=665560

Best regards.
Mohammed Morsi
2010-12-29 02:06:37 UTC
Permalink
Post by Mamoru Tasaka
Post by Minnikhanov
Post by Mohammed Morsi
Also the following are new gems which will need to be packaged
* arel (1.0.1)
* autotest (4.4.2)
* bundler (1.0.3)
* database_cleaner (0.6.0)
* factory_girl_rails (1.0)
* i18n (0.4.2)
* mail (2.2.29)
May I'll prepare mail package?
Only I find ver. 2.2.13. https://rubygems.org/downloads/mail-2.2.13.gem
I made spec file and srpm, now polish they.
Google did't find for me rubygem mail ver.2.2.29.
Is anywhere link to mail (2.2.29)?
mail does not seem to be packaged for Fedora yet so you can
package this for Fedora (and I cannot find mail 2.2.29 either).
OK my mistake, the version I have locally is 2.2.9 (had thrown an
extra '2' in there by mistake).

-Mo
Loading...