Hi again,
I’ve been packaging more and more stuff that is using RSpec 3 in test suites. We currently have RSpec 2.14.1 even in rawhide. Is anyone working on an upgrade? Or providing RSpec 3 in parallel?
I realize it’s a big undertaking to do this, but it sucks not to be able to run tests in %check because of all the breaking changes.
- Julian
[ Julian C. Dunn jdunn@aquezada.com * Sorry, I'm ] [ WWW: http://www.aquezada.com/staff/julian * only Web 1.0 ] [ gopher://sdf.org/1/users/keymaker/ * compliant! ] [ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9 ]
Julian C. Dunn wrote, at 06/27/2014 11:00 PM +9:00:
Hi again,
I’ve been packaging more and more stuff that is using RSpec 3 in test suites. We currently have RSpec 2.14.1 even in rawhide. Is anyone working on an upgrade? Or providing RSpec 3 in parallel?
I realize it’s a big undertaking to do this, but it sucks not to be able to run tests in %check because of all the breaking changes.
I plan to update rspec series to 3.x on F-22, but not on F-21. When people are working hard to fix FTBFS which already appears on many rubygems related packages, introducing another breakage at this timing is not I am going to do. Perhaps on F-22 I will make compat-package for rspec 2 series (review requests needed, I will create these), and maybe I will keep these compat-package even on F-23.
Regards, Mamoru
Dne 27.6.2014 16:31, Mamoru TASAKA napsal(a):
Julian C. Dunn wrote, at 06/27/2014 11:00 PM +9:00:
Hi again,
I’ve been packaging more and more stuff that is using RSpec 3 in test suites. We currently have RSpec 2.14.1 even in rawhide. Is anyone working on an upgrade? Or providing RSpec 3 in parallel?
I realize it’s a big undertaking to do this, but it sucks not to be able to run tests in %check because of all the breaking changes.
How big differences are between RSpec 2.x and 3.x?
I plan to update rspec series to 3.x on F-22, but not on F-21.
+1 for F22
When people are working hard to fix FTBFS which already appears on many rubygems related packages, introducing another breakage at this timing is not I am going to do. Perhaps on F-22 I will make compat-package for rspec 2 series (review requests needed, I will create these), and maybe I will keep these compat-package even on F-23.
Sounds like a good plan.
Vít
On Fri, Jun 27, 2014 at 12:46 PM, Vít Ondruch vondruch@redhat.com wrote:
Dne 27.6.2014 16:31, Mamoru TASAKA napsal(a):
Julian C. Dunn wrote, at 06/27/2014 11:00 PM +9:00:
Hi again,
I’ve been packaging more and more stuff that is using RSpec 3 in test suites. We currently have RSpec 2.14.1 even in rawhide. Is anyone working on an upgrade? Or providing RSpec 3 in parallel?
I realize it’s a big undertaking to do this, but it sucks not to be able to run tests in %check because of all the breaking changes.
How big differences are between RSpec 2.x and 3.x?
There are an enormous number of breaking changes.
http://myronmars.to/n/dev-blog/2013/07/the-plan-for-rspec-3
- Julian
I realize it’s a big undertaking to do this, but it sucks not to be able to run tests in %check because of all the breaking changes.
I could also use it already.
I plan to update rspec series to 3.x on F-22
Makes sense to me. We were fixing a lot recently.
Josef
----- Original Message ----- From: "Mamoru TASAKA" mtasaka@fedoraproject.org To: "Ruby SIG mailing list" ruby-sig@lists.fedoraproject.org Sent: Friday, 27 June, 2014 4:31:20 PM Subject: Re: RSpec 3
Julian C. Dunn wrote, at 06/27/2014 11:00 PM +9:00:
Hi again,
I’ve been packaging more and more stuff that is using RSpec 3 in test suites. We currently have RSpec 2.14.1 even in rawhide. Is anyone working on an upgrade? Or providing RSpec 3 in parallel?
I realize it’s a big undertaking to do this, but it sucks not to be able to run tests in %check because of all the breaking changes.
I plan to update rspec series to 3.x on F-22, but not on F-21. When people are working hard to fix FTBFS which already appears on many rubygems related packages, introducing another breakage at this timing is not I am going to do. Perhaps on F-22 I will make compat-package for rspec 2 series (review requests needed, I will create these), and maybe I will keep these compat-package even on F-23.
Regards, Mamoru
_______________________________________________ ruby-sig mailing list ruby-sig@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
A little late to the game but a colleague was updating some of our gems using transpec: http://yujinakayama.me/transpec/
Please do see their excellent readme here: https://github.com/yujinakayama/transpec
And an excellent summary of the process that was needed here: https://github.com/ManageIQ/manageiq/pull/188#issuecomment-49909262
And some example PRs on github to upgrade the gems to rspec 3: https://github.com/ManageIQ/linux_admin/pull/105 https://github.com/ManageIQ/more_core_extensions/pull/16 https://github.com/ManageIQ/ovirt_metrics/pull/4 https://github.com/ManageIQ/binary_struct/pull/4
Joe
----- Original Message -----
I realize it’s a big undertaking to do this, but it sucks not to be able to run tests in %check because of all the breaking changes.
I could also use it already.
I plan to update rspec series to 3.x on F-22
Makes sense to me. We were fixing a lot recently.
Josef
----- Original Message ----- From: "Mamoru TASAKA" mtasaka@fedoraproject.org To: "Ruby SIG mailing list" ruby-sig@lists.fedoraproject.org Sent: Friday, 27 June, 2014 4:31:20 PM Subject: Re: RSpec 3
Julian C. Dunn wrote, at 06/27/2014 11:00 PM +9:00:
Hi again,
I’ve been packaging more and more stuff that is using RSpec 3 in test suites. We currently have RSpec 2.14.1 even in rawhide. Is anyone working on an upgrade? Or providing RSpec 3 in parallel?
I realize it’s a big undertaking to do this, but it sucks not to be able to run tests in %check because of all the breaking changes.
I plan to update rspec series to 3.x on F-22, but not on F-21. When people are working hard to fix FTBFS which already appears on many rubygems related packages, introducing another breakage at this timing is not I am going to do. Perhaps on F-22 I will make compat-package for rspec 2 series (review requests needed, I will create these), and maybe I will keep these compat-package even on F-23.
Regards, Mamoru
ruby-sig mailing list ruby-sig@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/ruby-sig _______________________________________________ ruby-sig mailing list ruby-sig@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
Dne 27.6.2014 16:31, Mamoru TASAKA napsal(a):
Julian C. Dunn wrote, at 06/27/2014 11:00 PM +9:00:
Hi again,
I’ve been packaging more and more stuff that is using RSpec 3 in test suites. We currently have RSpec 2.14.1 even in rawhide. Is anyone working on an upgrade? Or providing RSpec 3 in parallel?
I realize it’s a big undertaking to do this, but it sucks not to be able to run tests in %check because of all the breaking changes.
I plan to update rspec series to 3.x on F-22, but not on F-21. When people are working hard to fix FTBFS which already appears on many rubygems related packages, introducing another breakage at this timing is not I am going to do. Perhaps on F-22 I will make compat-package for rspec 2 series (review requests needed, I will create these), and maybe I will keep these compat-package even on F-23.
Regards, Mamoru
Hi Mamoru,
What is the state of this affair? Should I prepare updated RSpec 3.x packages for review? Or do you have something already?
Vít
Vít Ondruch wrote on 09/01/2014 10:10 PM:
Dne 27.6.2014 16:31, Mamoru TASAKA napsal(a):
Julian C. Dunn wrote, at 06/27/2014 11:00 PM +9:00:
Hi again,
I’ve been packaging more and more stuff that is using RSpec 3 in test suites. We currently have RSpec 2.14.1 even in rawhide. Is anyone working on an upgrade? Or providing RSpec 3 in parallel?
I realize it’s a big undertaking to do this, but it sucks not to be able to run tests in %check because of all the breaking changes.
I plan to update rspec series to 3.x on F-22, but not on F-21. When people are working hard to fix FTBFS which already appears on many rubygems related packages, introducing another breakage at this timing is not I am going to do. Perhaps on F-22 I will make compat-package for rspec 2 series (review requests needed, I will create these), and maybe I will keep these compat-package even on F-23.
Regards, Mamoru
Hi Mamoru,
What is the state of this affair? Should I prepare updated RSpec 3.x packages for review? Or do you have something already?
Well, srpms are actually ready, just I have to do is to submit them for review and to look for reviewer. Will do today, so please wait, thank you for pinging.
Mamoru
Mamoru TASAKA wrote on 09/02/2014 06:34 AM:
Vít Ondruch wrote on 09/01/2014 10:10 PM:
Dne 27.6.2014 16:31, Mamoru TASAKA napsal(a):
Julian C. Dunn wrote, at 06/27/2014 11:00 PM +9:00:
Hi again,
I’ve been packaging more and more stuff that is using RSpec 3 in test suites. We currently have RSpec 2.14.1 even in rawhide. Is anyone working on an upgrade? Or providing RSpec 3 in parallel?
I realize it’s a big undertaking to do this, but it sucks not to be able to run tests in %check because of all the breaking changes.
I plan to update rspec series to 3.x on F-22, but not on F-21. When people are working hard to fix FTBFS which already appears on many rubygems related packages, introducing another breakage at this timing is not I am going to do. Perhaps on F-22 I will make compat-package for rspec 2 series (review requests needed, I will create these), and maybe I will keep these compat-package even on F-23.
Regards, Mamoru
Hi Mamoru,
What is the state of this affair? Should I prepare updated RSpec 3.x packages for review? Or do you have something already?
Well, srpms are actually ready, just I have to do is to submit them for review and to look for reviewer. Will do today, so please wait, thank you for pinging.
Hello, all:
Now for F-22 rspec2 (re-)review requests are ready: https://bugzilla.redhat.com/show_bug.cgi?id=1136384 rubygem-rspec2-expectations https://bugzilla.redhat.com/show_bug.cgi?id=1136385 rubygem-rspec2-mocks https://bugzilla.redhat.com/show_bug.cgi?id=1136389 rubygem-rspec2-core https://bugzilla.redhat.com/show_bug.cgi?id=1136390 rubygem-rspec2
If these reviews pass, I will update rspec suite on F-22 to 3.0.x (i.e. on F-22 rspec 3 series will be default). Note that srpms are ready and if you want to try please feel to take them from:
https://mtasaka.fedorapeople.org/Review_request/rspec3/
Swap reviews are welcome!
Regards, Mamoru
Dne 2.9.2014 15:32, Mamoru TASAKA napsal(a):
What is this good for:
Provides: rubygem(%{rpmgem_name}) = %{version}-%{release}
Especially where does the %{rpmgem_name} come from? Am I missing something?
Vít
Hi:
Vít Ondruch wrote on 09/02/2014 11:15 PM:
Dne 2.9.2014 15:32, Mamoru TASAKA napsal(a):
What is this good for:
Provides: rubygem(%{rpmgem_name}) = %{version}-%{release}
Especially where does the %{rpmgem_name} come from? Am I missing something?
Ah, that's just a copy / paste mistake from rubygem-rspec2 spec. Not needed for rspec(3) side rpms, will fix, thanks.
Mamoru
https://bugzilla.redhat.com/show_bug.cgi?id=1136384 rubygem-rspec2-expectations https://bugzilla.redhat.com/show_bug.cgi?id=1136385 rubygem-rspec2-mocks https://bugzilla.redhat.com/show_bug.cgi?id=1136389 rubygem-rspec2-core https://bugzilla.redhat.com/show_bug.cgi?id=1136390 rubygem-rspec2
I will look into it.
Swap reviews are welcome!
You could help me with those:
https://bugzilla.redhat.com/show_bug.cgi?id=1122941 https://bugzilla.redhat.com/show_bug.cgi?id=1122944 https://bugzilla.redhat.com/show_bug.cgi?id=1122939
Thanks Josef
----- Original Message ----- From: "Mamoru TASAKA" mtasaka@fedoraproject.org To: "Ruby SIG mailing list" ruby-sig@lists.fedoraproject.org Sent: Tuesday, September 2, 2014 3:32:10 PM Subject: Re: RSpec 3
Mamoru TASAKA wrote on 09/02/2014 06:34 AM:
Vít Ondruch wrote on 09/01/2014 10:10 PM:
Dne 27.6.2014 16:31, Mamoru TASAKA napsal(a):
Julian C. Dunn wrote, at 06/27/2014 11:00 PM +9:00:
Hi again,
I’ve been packaging more and more stuff that is using RSpec 3 in test suites. We currently have RSpec 2.14.1 even in rawhide. Is anyone working on an upgrade? Or providing RSpec 3 in parallel?
I realize it’s a big undertaking to do this, but it sucks not to be able to run tests in %check because of all the breaking changes.
I plan to update rspec series to 3.x on F-22, but not on F-21. When people are working hard to fix FTBFS which already appears on many rubygems related packages, introducing another breakage at this timing is not I am going to do. Perhaps on F-22 I will make compat-package for rspec 2 series (review requests needed, I will create these), and maybe I will keep these compat-package even on F-23.
Regards, Mamoru
Hi Mamoru,
What is the state of this affair? Should I prepare updated RSpec 3.x packages for review? Or do you have something already?
Well, srpms are actually ready, just I have to do is to submit them for review and to look for reviewer. Will do today, so please wait, thank you for pinging.
Hello, all:
Now for F-22 rspec2 (re-)review requests are ready: https://bugzilla.redhat.com/show_bug.cgi?id=1136384 rubygem-rspec2-expectations https://bugzilla.redhat.com/show_bug.cgi?id=1136385 rubygem-rspec2-mocks https://bugzilla.redhat.com/show_bug.cgi?id=1136389 rubygem-rspec2-core https://bugzilla.redhat.com/show_bug.cgi?id=1136390 rubygem-rspec2
If these reviews pass, I will update rspec suite on F-22 to 3.0.x (i.e. on F-22 rspec 3 series will be default). Note that srpms are ready and if you want to try please feel to take them from:
https://mtasaka.fedorapeople.org/Review_request/rspec3/
Swap reviews are welcome!
Regards, Mamoru
_______________________________________________ ruby-sig mailing list ruby-sig@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/ruby-sig
ruby-sig@lists.fedoraproject.org
-
Joe Rafaniello -
Josef Stribny -
Julian C. Dunn -
Mamoru TASAKA -
Vít Ondruch