Hi all,
Pavel and I have been working bringing the new rubygem-cucumber 7.1.0 into Fedora.
We have working updates available in a copr repo [0] that you can try out (as to "how", see the proposal [1]).
There are some new dependencies (and renames) that need a review done in order to get the packages into Fedora:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2010235 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2010263 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2010313 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2010350
Also feel free to take a look at the PRs:
https://src.fedoraproject.org/rpms/rubygem-cucumber-wire/pull-request/2 https://src.fedoraproject.org/rpms/rubygem-cucumber/pull-request/4 https://src.fedoraproject.org/rpms/rubygem-cucumber-core/pull-request/4 https://src.fedoraproject.org/rpms/rubygem-childprocess/pull-request/2 https://src.fedoraproject.org/rpms/rubygem-aruba/pull-request/2
Once we have all the required packages updated we will start rebuilding them in a side-tag.
Regards, Jarek
[0] https://copr.fedorainfracloud.org/coprs/pvalena/rubygems/ [1] https://fedoraproject.org/wiki/Changes/rubygem-cucumber_7.1.0#How_To_Test
Hi Jarek,
Dne 15. 12. 21 v 22:17 Jarek Prokop napsal(a):
Hi all,
Pavel and I have been working bringing the new rubygem-cucumber 7.1.0 into Fedora.
We have working updates available in a copr repo [0] that you can try out (as to "how", see the proposal [1]).
There are some new dependencies (and renames) that need a review done in order to get the packages into Fedora:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2010235 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2010263 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2010313 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=2010350
Also feel free to take a look at the PRs:
https://src.fedoraproject.org/rpms/rubygem-cucumber-wire/pull-request/2 https://src.fedoraproject.org/rpms/rubygem-cucumber/pull-request/4 https://src.fedoraproject.org/rpms/rubygem-cucumber-core/pull-request/4 https://src.fedoraproject.org/rpms/rubygem-childprocess/pull-request/2 https://src.fedoraproject.org/rpms/rubygem-aruba/pull-request/2
Considering the Aruba ticket ^^, I am not sure if every party understands that you are testing the changes in the side-tag (am I correct, right?), you are unspecifically referring bellow. So what side-tag are you using?
Thx
Vít
Once we have all the required packages updated we will start rebuilding them in a side-tag.
Regards, Jarek
[0] https://copr.fedorainfracloud.org/coprs/pvalena/rubygems/ [1] https://fedoraproject.org/wiki/Changes/rubygem-cucumber_7.1.0#How_To_Test _______________________________________________ ruby-sig mailing list -- ruby-sig@lists.fedoraproject.org To unsubscribe send an email to ruby-sig-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ruby-sig@lists.fedoraproject.o... Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Hi,
On 1/12/22 12:34, Vít Ondruch wrote:
Hi Jarek,
https://src.fedoraproject.org/rpms/rubygem-aruba/pull-request/2
Considering the Aruba ticket ^^, I am not sure if every party understands that you are testing the changes in the side-tag (am I correct, right?), you are unspecifically referring bellow. So what side-tag are you using?
Right, changes are built & tested using the side-tag: f36-build-side-49108
Already built packages can be viewed here: https://koji.fedoraproject.org/koji/builds?order=-tag_name&tagID=49108&a... https://koji.fedoraproject.org/koji/builds?order=-tag_name&tagID=49108&inherited=0&latest=1
Regards, Jarek
Hello, all:
Jarek Prokop wrote on 2022/01/13 2:17:
Hi,
On 1/12/22 12:34, Vít Ondruch wrote:
Hi Jarek,
https://src.fedoraproject.org/rpms/rubygem-aruba/pull-request/2
Considering the Aruba ticket ^^, I am not sure if every party understands that you are testing the changes in the side-tag (am I correct, right?), you are unspecifically referring bellow. So what side-tag are you using?
Right, changes are built & tested using the side-tag: f36-build-side-49108
Already built packages can be viewed here: https://koji.fedoraproject.org/koji/builds?order=-tag_name&tagID=49108&a... https://koji.fedoraproject.org/koji/builds?order=-tag_name&tagID=49108&inherited=0&latest=1
Now I've pushed rubygem-aruba-2.0.0-2.fc36 into f36-build-side-49108 . Thanks (especially to Pavel and Jarek) for paying attention to this. (And sorry for pushing new aruba late.)
I am now trying to rebuild several packages. Note that as Jarek has pointed out (on rubygem-aruba PR), cucumber 7 now refuses "--tag ~@foo" usage: several rpms fails to build with cucumber 7 due to this change and need fixing, e.g. https://src.fedoraproject.org/rpms/rubygem-rake-compiler/c/c645a03053d3722a5...
Regards, Jarek
Regards, Mamoru
On 1/14/22 12:40, Mamoru TASAKA wrote:
Hello, all:
Jarek Prokop wrote on 2022/01/13 2:17:
Hi,
On 1/12/22 12:34, Vít Ondruch wrote:
Hi Jarek,
https://src.fedoraproject.org/rpms/rubygem-aruba/pull-request/2
Considering the Aruba ticket ^^, I am not sure if every party understands that you are testing the changes in the side-tag (am I correct, right?), you are unspecifically referring bellow. So what side-tag are you using?
Right, changes are built & tested using the side-tag: f36-build-side-49108
Already built packages can be viewed here: https://koji.fedoraproject.org/koji/builds?order=-tag_name&tagID=49108&a... https://koji.fedoraproject.org/koji/builds?order=-tag_name&tagID=49108&inherited=0&latest=1
Now I've pushed rubygem-aruba-2.0.0-2.fc36 into f36-build-side-49108 . Thanks (especially to Pavel and Jarek) for paying attention to this. (And sorry for pushing new aruba late.)
I am now trying to rebuild several packages. Note that as Jarek has pointed out (on rubygem-aruba PR), cucumber 7 now refuses "--tag ~@foo" usage: several rpms fails to build with cucumber 7 due to this change and need fixing, e.g. https://src.fedoraproject.org/rpms/rubygem-rake-compiler/c/c645a03053d3722a5...
Thanks!
I will start rebuilding the cucumber dependencies with the features tests enabled.
Regards, Jarek
Regards, Mamoru
Jarek Prokop wrote on 2022/01/17 7:40:
On 1/14/22 12:40, Mamoru TASAKA wrote:
Hello, all:
Jarek Prokop wrote on 2022/01/13 2:17:
Hi,
On 1/12/22 12:34, Vít Ondruch wrote:
Hi Jarek,
https://src.fedoraproject.org/rpms/rubygem-aruba/pull-request/2
Considering the Aruba ticket ^^, I am not sure if every party understands that you are testing the changes in the side-tag (am I correct, right?), you are unspecifically referring bellow. So what side-tag are you using?
Right, changes are built & tested using the side-tag: f36-build-side-49108
Already built packages can be viewed here: https://koji.fedoraproject.org/koji/builds?order=-tag_name&tagID=49108&a... https://koji.fedoraproject.org/koji/builds?order=-tag_name&tagID=49108&inherited=0&latest=1
Now I've pushed rubygem-aruba-2.0.0-2.fc36 into f36-build-side-49108 . Thanks (especially to Pavel and Jarek) for paying attention to this. (And sorry for pushing new aruba late.)
I am now trying to rebuild several packages. Note that as Jarek has pointed out (on rubygem-aruba PR), cucumber 7 now refuses "--tag ~@foo" usage: several rpms fails to build with cucumber 7 due to this change and need fixing, e.g. https://src.fedoraproject.org/rpms/rubygem-rake-compiler/c/c645a03053d3722a5...
Thanks!
I will start rebuilding the cucumber dependencies with the features tests enabled.
Currently, 2 packages are seeing trouble. But I think now f36-build-side-49108 sidetag can be merged into f36 main buildroot.
1. rubygem-nifti Executing rspec and cucumber test suites causes test failure on s390x only (note that srpm itself is noarch), very likely big endian related, so rebuilding rubygem-nifti causes build failure if build happens on s390x arch:
https://koji.fedoraproject.org/koji/taskinfo?taskID=81341629
2. rubygem-cucumber-rails This seems difficult for me... cucumber testsuite fails (even if I relax gemspec dependency) in the way seemingly difficult.
cucumber testsuite seems to be failing basically by the following code: ``` $ ruby -e "require 'aruba/cucumber'" /usr/share/gems/gems/aruba-2.0.0/lib/aruba/cucumber/hooks.rb:4:in `<top (required)>': undefined method `World' for main:Object (NoMethodError) from internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:85:in `require' from internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:85:in `require' from /usr/share/gems/gems/aruba-2.0.0/lib/aruba/cucumber.rb:4:in `<top (required)>' from internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:160:in `require' from internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:160:in `rescue in require' from internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:149:in `require' from -e:1:in `<main>' internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:85:in `require': cannot load such file -- aruba/cucumber (LoadError) from internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:85:in `require' from -e:1:in `<main>' ``` Looks like some initialization is needed before "require 'aruba/cucumber'", however currently I have no idea. Maybe updating to the latest cucumber-rails fixes cucumber test, I hope someone would investigate this further.
Again thanks for work on cucumber update.
Regards, Mamoru
Dne 17. 01. 22 v 8:03 Mamoru TASAKA napsal(a):
Jarek Prokop wrote on 2022/01/17 7:40:
On 1/14/22 12:40, Mamoru TASAKA wrote:
Hello, all:
Jarek Prokop wrote on 2022/01/13 2:17:
Hi,
On 1/12/22 12:34, Vít Ondruch wrote:
Hi Jarek,
https://src.fedoraproject.org/rpms/rubygem-aruba/pull-request/2
Considering the Aruba ticket ^^, I am not sure if every party understands that you are testing the changes in the side-tag (am I correct, right?), you are unspecifically referring bellow. So what side-tag are you using?
Right, changes are built & tested using the side-tag: f36-build-side-49108
Already built packages can be viewed here: https://koji.fedoraproject.org/koji/builds?order=-tag_name&tagID=49108&a... https://koji.fedoraproject.org/koji/builds?order=-tag_name&tagID=49108&inherited=0&latest=1
Now I've pushed rubygem-aruba-2.0.0-2.fc36 into f36-build-side-49108 . Thanks (especially to Pavel and Jarek) for paying attention to this. (And sorry for pushing new aruba late.)
I am now trying to rebuild several packages. Note that as Jarek has pointed out (on rubygem-aruba PR), cucumber 7 now refuses "--tag ~@foo" usage: several rpms fails to build with cucumber 7 due to this change and need fixing, e.g. https://src.fedoraproject.org/rpms/rubygem-rake-compiler/c/c645a03053d3722a5...
Thanks!
I will start rebuilding the cucumber dependencies with the features tests enabled.
Currently, 2 packages are seeing trouble. But I think now f36-build-side-49108 sidetag can be merged into f36 main buildroot.
Tomorrow should start Fedora mass rebuild, therefore I support the merge (although, I should check with rel-engs due to Ruby mass rebuild, the timing is not ideal, sigh).
- rubygem-nifti
Executing rspec and cucumber test suites causes test failure on s390x only (note that srpm itself is noarch), very likely big endian related, so rebuilding rubygem-nifti causes build failure if build happens on s390x arch:
https://koji.fedoraproject.org/koji/taskinfo?taskID=81341629
Checking Koshei [1], there were some build failures. But hard to tell what was the reason.
[1] https://koschei.fedoraproject.org/package/rubygem-nifti
- rubygem-cucumber-rails
This seems difficult for me... cucumber testsuite fails (even if I relax gemspec dependency) in the way seemingly difficult.
cucumber testsuite seems to be failing basically by the following code:
$ ruby -e "require 'aruba/cucumber'" /usr/share/gems/gems/aruba-2.0.0/lib/aruba/cucumber/hooks.rb:4:in `<top (required)>': undefined method `World' for main:Object (NoMethodError) from <internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:85:in `require' from <internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:85:in `require' from /usr/share/gems/gems/aruba-2.0.0/lib/aruba/cucumber.rb:4:in `<top (required)>' from <internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:160:in `require' from <internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:160:in `rescue in require' from <internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:149:in `require' from -e:1:in `<main>' <internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:85:in `require': cannot load such file -- aruba/cucumber (LoadError) from <internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:85:in `require' from -e:1:in `<main>'Looks like some initialization is needed before "require 'aruba/cucumber'", however currently I have no idea. Maybe updating to the latest cucumber-rails fixes cucumber test, I hope someone would investigate this further.
The build fails already for almost a year :/ I'll see what is the situation after the cucumber is updated.
Vít
On Mon, Jan 17, 2022 at 9:50 AM Vít Ondruch vondruch@redhat.com wrote:
Dne 17. 01. 22 v 8:03 Mamoru TASAKA napsal(a):
Jarek Prokop wrote on 2022/01/17 7:40:
On 1/14/22 12:40, Mamoru TASAKA wrote:
Hello, all:
Jarek Prokop wrote on 2022/01/13 2:17:
Hi,
On 1/12/22 12:34, Vít Ondruch wrote:
Hi Jarek, > https://src.fedoraproject.org/rpms/rubygem-aruba/pull-request/2
Considering the Aruba ticket ^^, I am not sure if every party understands that you are testing the changes in the side-tag (am I correct, right?), you are unspecifically referring bellow. So what side-tag are you using?
Right, changes are built & tested using the side-tag: f36-build-side-49108
Already built packages can be viewed here: https://koji.fedoraproject.org/koji/builds?order=-tag_name&tagID=49108&a... https://koji.fedoraproject.org/koji/builds?order=-tag_name&tagID=49108&inherited=0&latest=1
Now I've pushed rubygem-aruba-2.0.0-2.fc36 into f36-build-side-49108 . Thanks (especially to Pavel and Jarek) for paying attention to this. (And sorry for pushing new aruba late.)
I am now trying to rebuild several packages. Note that as Jarek has pointed out (on rubygem-aruba PR), cucumber 7 now refuses "--tag ~@foo" usage: several rpms fails to build with cucumber 7 due to this change and need fixing, e.g. https://src.fedoraproject.org/rpms/rubygem-rake-compiler/c/c645a03053d3722a5...
Thanks!
I will start rebuilding the cucumber dependencies with the features tests enabled.
Currently, 2 packages are seeing trouble. But I think now f36-build-side-49108 sidetag can be merged into f36 main buildroot.
Hello, thanks for all the good work!
I've re-checked (scratch-built) all the packages that depend on cucumber, and I can confirm there are no more failures.
Tomorrow should start Fedora mass rebuild, therefore I support the merge (although, I should check with rel-engs due to Ruby mass rebuild, the timing is not ideal, sigh).
I agree it would be best to merge it now, prior to mass rebuild.
- rubygem-nifti
Executing rspec and cucumber test suites causes test failure on s390x only (note that srpm itself is noarch), very likely big endian related, so rebuilding rubygem-nifti causes build failure if build happens on s390x arch:
https://koji.fedoraproject.org/koji/taskinfo?taskID=81341629
Checking Koshei [1], there were some build failures. But hard to tell what was the reason.
[1] https://koschei.fedoraproject.org/package/rubygem-nifti
- rubygem-cucumber-rails
This seems difficult for me... cucumber testsuite fails (even if I relax gemspec dependency) in the way seemingly difficult.
cucumber testsuite seems to be failing basically by the following code:
$ ruby -e "require 'aruba/cucumber'" /usr/share/gems/gems/aruba-2.0.0/lib/aruba/cucumber/hooks.rb:4:in `<top (required)>': undefined method `World' for main:Object (NoMethodError) from <internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:85:in `require' from <internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:85:in `require' from /usr/share/gems/gems/aruba-2.0.0/lib/aruba/cucumber.rb:4:in `<top (required)>' from <internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:160:in `require' from <internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:160:in `rescue in require' from <internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:149:in `require' from -e:1:in `<main>' <internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:85:in `require': cannot load such file -- aruba/cucumber (LoadError) from <internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:85:in `require' from -e:1:in `<main>'Looks like some initialization is needed before "require 'aruba/cucumber'", however currently I have no idea. Maybe updating to the latest cucumber-rails fixes cucumber test, I hope someone would investigate this further.
I will update cucumber-rails along with RoR 7.0 (I've successfully built 7.0.0 in my COPR now). Self-contained change coming soon.
Pavel
The build fails already for almost a year :/ I'll see what is the situation after the cucumber is updated.
Vít
Hi all,
I've merged the side-tag into rawhide: https://bodhi.fedoraproject.org/updates/FEDORA-2022-a4ef1a7470
Thanks for help with this update.
Regards, Jarek
Nice and congratulations!
V.
Dne 17. 01. 22 v 16:54 Jarek Prokop napsal(a):
Hi all,
I've merged the side-tag into rawhide: https://bodhi.fedoraproject.org/updates/FEDORA-2022-a4ef1a7470
Thanks for help with this update.
Regards, Jarek _______________________________________________ ruby-sig mailing list -- ruby-sig@lists.fedoraproject.org To unsubscribe send an email to ruby-sig-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ruby-sig@lists.fedoraproject.o... Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
ruby-sig@lists.fedoraproject.org