On Fri, Sep 16, 2022 at 7:03 PM Vít Ondruch <vondr...@redhat.com> wrote: > > Hi everybody, > > I think it is the highest time to kick of the Ruby 3.2 thread. So here > we go. I have just pushed the first update to private-ruby-3.2 branch > [1] and here is the scratch build: > > https://koji.fedoraproject.org/koji/taskinfo?taskID=92083633 > > There is nothing what would stand out. > > Nevertheless, I was testing the `--enable-mkmf-verbose` configure option > submitted upstream by @jaruga (thx a bunch) with the ByeBug example just > to find out that ByeBug is broken due to some upstream changes [3]. So > just early heads up that there will be needed some changes for Ruby 3.2. > > As always, feedback is appreciate via regular channels. > > > Vít
Thanks for starting to prepare the new Ruby. It seems that this year, the preparation is earlier than before. I am not sure that the ByeBug issue is directly related to the `--enable-mkmf-verbose` option. I think the issue doesn't block adding the configuration option, right? Seeing your commit: https://src.fedoraproject.org/rpms/ruby/c/6a98c151e6205b6d5774d0436f6492d97c321eb4?branch=private-ruby-3.2 , I thought backporting the upstream commit to rawhide before releasing Ruby 3.2 would be good idea. And here is the pull-request I sent now. https://src.fedoraproject.org/rpms/ruby/pull-request/133 -- Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic See <https://www.worldtimebuddy.com/czech-republic-prague-to-utc> for the timezone. _______________________________________________ ruby-sig mailing list -- ruby-sig@lists.fedoraproject.org To unsubscribe send an email to ruby-sig-le...@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.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
