Re: rpms/ruby rawhide starting to fail on OpenSSL related failure

2023-11-10 Thread Jun Aruga (he / him) 
The PR was merged. Now Koschei passes.
https://src.fedoraproject.org/rpms/ruby/pull-request/163

> But my question was if the patch was backported for Ruby 3.2 and
possibly older.

I opened the backport request ticket below in the Ruby project.
https://bugs.ruby-lang.org/issues/2

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  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

Re: rpms/ruby rawhide starting to fail on OpenSSL related failure

2023-11-09 Thread Jun Aruga (he / him) 
On Thu, Nov 9, 2023 at 5:01 PM Vít Ondruch  wrote:
>
>
> Dne 09. 11. 23 v 16:41 Jun Aruga (he / him) napsal(a):
> > On Thu, Nov 9, 2023 at 10:03 AM Vít Ondruch  wrote:
> >>
> >> Dne 08. 11. 23 v 18:31 Jun Aruga (he / him) napsal(a):
> >>> Hello folks in Ruby SIG.
> >>>
> >>> I just want to share that right now rpms/ruby started to fail in
> >>> Fedora rawhide after the dependent openssl version was upgraded from
> >>> openssl 1:3.1.1-4.fc40 to 1:3.1.4-1.fc40.
> >>> https://koschei.fedoraproject.org/package/ruby?collection=f40
> >>>
> >>> ```
> >>> 1) Failure:
> >>> OpenSSL::TestFIPS#test_fips_mode_get_is_true_on_fips_mode_enabled
> >>> [/builddir/build/BUILD/ruby-3.2.2/test/openssl/test_fips.rb:12]:
> >>> assert_separately failed with error message
> >>> pid 93922 exit 1
> >>> | 
> >>> /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/pkey.rb:132:in
> >>> `initialize': could not parse pkey (OpenSSL::PKey::DHError)
> >>> | from 
> >>> /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/pkey.rb:132:in
> >>> `new'
> >>> | from 
> >>> /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/pkey.rb:132:in
> >>> `new'
> >>> | from 
> >>> /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/ssl.rb:37:in
> >>> `'
> >>> | from 
> >>> /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/ssl.rb:23:in
> >>> `'
> >>> | from 
> >>> /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/ssl.rb:22:in
> >>> `'
> >>> | from 
> >>> /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/ssl.rb:21:in
> >>> `'
> >>> | from 
> >>> /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl.rb:21:in
> >>> `require_relative'
> >>> | from 
> >>> /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl.rb:21:in
> >>> `'
> >>> | from -:in `require'
> >>> 2) Failure:
> >>> OpenSSL::TestFIPS#test_fips_mode_get_with_fips_mode_set
> >>> [/builddir/build/BUILD/ruby-3.2.2/test/openssl/test_fips.rb:38]:
> >>> assert_separately failed with error message
> >>> pid 93924 exit 1
> >>> | 
> >>> /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/pkey.rb:132:in
> >>> `initialize': could not parse pkey (OpenSSL::PKey::DHError)
> >>> | from 
> >>> /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/pkey.rb:132:in
> >>> `new'
> >>> | from 
> >>> /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/pkey.rb:132:in
> >>> `new'
> >>> | from 
> >>> /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/ssl.rb:37:in
> >>> `'
> >>> | from 
> >>> /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/ssl.rb:23:in
> >>> `'
> >>> | from 
> >>> /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/ssl.rb:22:in
> >>> `'
> >>> | from 
> >>> /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/ssl.rb:21:in
> >>> `'
> >>> | from 
> >>> /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl.rb:21:in
> >>> `require_relative'
> >>> | from 
> >>> /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl.rb:21:in
> >>> `'
> >>> | from -:in `require'
> >>> ```
> >>>
> >>> It seems that we need to apply the following patch that I applied to
> >>> CentOS 9 stream and RHEL 9 into Fedora too. I will work on it to pass
> >>> the tests on the current rawhide.
> >>> https://gitlab.com/redhat/centos-stream/rpms/ruby/-/commit/59242d8ce8261a9759dfb2bd8db673e55061a28b
> >>
> >> Thx!
> >>
> >>
> >>> As a note, we can remove this patch after upgrading Ruby to 3.3.0.
> >>
> >> BTW could you also please check the patch was backported into upstream
> >> Ruby 3.2 or older? That way we could eventually drop it from everywhere.
> >> Thx.
> > I sent the PR. I need to test it by myself. But please review.

Re: rpms/ruby rawhide starting to fail on OpenSSL related failure

2023-11-09 Thread Jun Aruga (he / him) 
On Thu, Nov 9, 2023 at 10:03 AM Vít Ondruch  wrote:
>
>
> Dne 08. 11. 23 v 18:31 Jun Aruga (he / him) napsal(a):
> > Hello folks in Ruby SIG.
> >
> > I just want to share that right now rpms/ruby started to fail in
> > Fedora rawhide after the dependent openssl version was upgraded from
> > openssl 1:3.1.1-4.fc40 to 1:3.1.4-1.fc40.
> > https://koschei.fedoraproject.org/package/ruby?collection=f40
> >
> > ```
> >1) Failure:
> > OpenSSL::TestFIPS#test_fips_mode_get_is_true_on_fips_mode_enabled
> > [/builddir/build/BUILD/ruby-3.2.2/test/openssl/test_fips.rb:12]:
> > assert_separately failed with error message
> > pid 93922 exit 1
> > | 
> > /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/pkey.rb:132:in
> > `initialize': could not parse pkey (OpenSSL::PKey::DHError)
> > | from 
> > /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/pkey.rb:132:in
> > `new'
> > | from 
> > /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/pkey.rb:132:in
> > `new'
> > | from 
> > /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/ssl.rb:37:in
> > `'
> > | from 
> > /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/ssl.rb:23:in
> > `'
> > | from 
> > /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/ssl.rb:22:in
> > `'
> > | from 
> > /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/ssl.rb:21:in
> > `'
> > | from 
> > /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl.rb:21:in
> > `require_relative'
> > | from 
> > /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl.rb:21:in
> > `'
> > | from -:in `require'
> >2) Failure:
> > OpenSSL::TestFIPS#test_fips_mode_get_with_fips_mode_set
> > [/builddir/build/BUILD/ruby-3.2.2/test/openssl/test_fips.rb:38]:
> > assert_separately failed with error message
> > pid 93924 exit 1
> > | 
> > /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/pkey.rb:132:in
> > `initialize': could not parse pkey (OpenSSL::PKey::DHError)
> > | from 
> > /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/pkey.rb:132:in
> > `new'
> > | from 
> > /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/pkey.rb:132:in
> > `new'
> > | from 
> > /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/ssl.rb:37:in
> > `'
> > | from 
> > /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/ssl.rb:23:in
> > `'
> > | from 
> > /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/ssl.rb:22:in
> > `'
> > | from 
> > /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/ssl.rb:21:in
> > `'
> > | from 
> > /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl.rb:21:in
> > `require_relative'
> > | from 
> > /builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl.rb:21:in
> > `'
> > | from -:in `require'
> > ```
> >
> > It seems that we need to apply the following patch that I applied to
> > CentOS 9 stream and RHEL 9 into Fedora too. I will work on it to pass
> > the tests on the current rawhide.
> > https://gitlab.com/redhat/centos-stream/rpms/ruby/-/commit/59242d8ce8261a9759dfb2bd8db673e55061a28b
>
>
> Thx!
>
>
> >
> > As a note, we can remove this patch after upgrading Ruby to 3.3.0.
>
>
> BTW could you also please check the patch was backported into upstream
> Ruby 3.2 or older? That way we could eventually drop it from everywhere.
> Thx.

I sent the PR. I need to test it by myself. But please review.
https://src.fedoraproject.org/rpms/ruby/pull-request/163

Yes, the patch is already upstream below.  I expect that the patch is
included in Ruby 3.3.0.
https://github.com/ruby/ruby/commit/b6d7cdc2bad0eadbca73f3486917f0ec7a475814

-- 
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

rpms/ruby rawhide starting to fail on OpenSSL related failure

2023-11-08 Thread Jun Aruga (he / him) 
Hello folks in Ruby SIG.

I just want to share that right now rpms/ruby started to fail in
Fedora rawhide after the dependent openssl version was upgraded from
openssl 1:3.1.1-4.fc40 to 1:3.1.4-1.fc40.
https://koschei.fedoraproject.org/package/ruby?collection=f40

```
  1) Failure:
OpenSSL::TestFIPS#test_fips_mode_get_is_true_on_fips_mode_enabled
[/builddir/build/BUILD/ruby-3.2.2/test/openssl/test_fips.rb:12]:
assert_separately failed with error message
pid 93922 exit 1
| 
/builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/pkey.rb:132:in
`initialize': could not parse pkey (OpenSSL::PKey::DHError)
| from 
/builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/pkey.rb:132:in
`new'
| from 
/builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/pkey.rb:132:in
`new'
| from 
/builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/ssl.rb:37:in
`'
| from 
/builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/ssl.rb:23:in
`'
| from 
/builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/ssl.rb:22:in
`'
| from 
/builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/ssl.rb:21:in
`'
| from 
/builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl.rb:21:in
`require_relative'
| from 
/builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl.rb:21:in
`'
| from -:in `require'
  2) Failure:
OpenSSL::TestFIPS#test_fips_mode_get_with_fips_mode_set
[/builddir/build/BUILD/ruby-3.2.2/test/openssl/test_fips.rb:38]:
assert_separately failed with error message
pid 93924 exit 1
| 
/builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/pkey.rb:132:in
`initialize': could not parse pkey (OpenSSL::PKey::DHError)
| from 
/builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/pkey.rb:132:in
`new'
| from 
/builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/pkey.rb:132:in
`new'
| from 
/builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/ssl.rb:37:in
`'
| from 
/builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/ssl.rb:23:in
`'
| from 
/builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/ssl.rb:22:in
`'
| from 
/builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl/ssl.rb:21:in
`'
| from 
/builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl.rb:21:in
`require_relative'
| from 
/builddir/build/BUILD/ruby-3.2.2/redhat-linux-build/.ext/common/openssl.rb:21:in
`'
| from -:in `require'
```

It seems that we need to apply the following patch that I applied to
CentOS 9 stream and RHEL 9 into Fedora too. I will work on it to pass
the tests on the current rawhide.
https://gitlab.com/redhat/centos-stream/rpms/ruby/-/commit/59242d8ce8261a9759dfb2bd8db673e55061a28b

As a note, we can remove this patch after upgrading Ruby to 3.3.0.

Jun

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  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

Re: rpms/ruby rawhide FTBFS by checksec

2023-09-08 Thread Jun Aruga (he / him) 
Thanks for the info about the Bugzilla ticket.

I think that the situation is a bit different from the things reported
on the ticket.
For example, the checksec command is failing in x86_64 build below.

https://koji.fedoraproject.org/koji/taskinfo?taskID=105910750
https://kojipkgs.fedoraproject.org//work/tasks/750/105910750/build.log
+ checksec --file=redhat-linux-build/libruby.so.3.2.2
/var/tmp/rpm-tmp.GFaqBt: line 48: 85686 Aborted (core
dumped) checksec --file=redhat-linux-build/libruby.so.3.2.2
RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.GFaqBt (%check)

I tried to check which RPM package version of the checksec is used.
However it doesn't show the version of the installed checksec. It's
not convenient. Maybe because it is already installed in the build
environment? I think we can add the `rpm -q checksec` somewhere for
debugging purposes in ruby.spec
https://kojipkgs.fedoraproject.org//work/tasks/750/105910750/root.log

Anyway, I will consider commenting on the ticket.

Jun

On Fri, Sep 8, 2023 at 6:09 PM Vít Ondruch  wrote:
>
> But reading the ticket, it seems to be related after all :) It seems
> there was done some change, but properly not tested on Rawhide properly.
> Feel free to update the ticket.
>
>
> V.
>
>
> Dne 08. 09. 23 v 18:07 Vít Ondruch napsal(a):
> > Although, the dependency issue is new to me. Chm. Sorry for being to
> > fast replying without reading carefully.
> >
> >
> > V.
> >
> >
> > Dne 08. 09. 23 v 18:05 Vít Ondruch napsal(a):
> >> https://bugzilla.redhat.com/show_bug.cgi?id=2235760
> >>
> >>
> >> V.
> >>
> >>
> >> Dne 08. 09. 23 v 17:59 Jun Aruga (he / him) napsal(a):
> >>> Note that I am trying to fix the FTBFS on the current rpms/ruby
> >>> rawhide.
> >>>
> >>> Below is the scratch build with the modification to print the output
> >>> of the checksec command below.
> >>> https://koji.fedoraproject.org/koji/taskinfo?taskID=105910607
> >>>
> >>> ```
> >>> diff --git a/ruby.spec b/ruby.spec
> >>> index 51ada32..f61c3fe 100644
> >>> --- a/ruby.spec
> >>> +++ b/ruby.spec
> >>> @@ -855,6 +855,7 @@ rm -rf
> >>> %{buildroot}%{gem_dir}/gems/rake-%{rake_version}/.github
> >>>   %check
> >>>   %if 0%{?with_hardening_test}
> >>>   # Check Ruby hardening.
> >>> +checksec --file=%{_vpath_builddir}/libruby.so.%{ruby_version}
> >>>   checksec --file=%{_vpath_builddir}/libruby.so.%{ruby_version} | \
> >>> grep "Full RELRO.*Canary found.*NX enabled.*DSO.*No RPATH.*No
> >>> RUNPATH.*Yes.*\d*.*\d*.*libruby.so.%{ruby_version}"
> >>>   %endif
> >>> ```
> >>>
> >>> On only s390x build, there is another error in root.log. I am asking
> >>> how to fix it on devel@ mailing list now.
> >>>
> >>> https://kojipkgs.fedoraproject.org//work/tasks/753/105910753/root.log
> >>>
> >>> ```
> >>> DEBUG util.py:442:  No matches found for the following disable plugin
> >>> patterns: local, spacewalk, versionlock
> >>> DEBUG util.py:442:  Error:-
> >>> DEBUG util.py:442:   Problem: conflicting requests
> >>> DEBUG util.py:442:- nothing provides nm needed by
> >>> checksec-2.6.0-5.fc40.noarch from build
> >>> DEBUG util.py:442:- nothing provides python3.12dist(unicorn) >=
> >>> 1.0.2~rc1 needed by python3-pwntools-4.9.0-4.fc39.noarch from build
> >>> ```
> >>>
> ___
> 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



-- 
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

rpms/ruby rawhide FTBFS by checksec

2023-09-08 Thread Jun Aruga (he / him) 
Note that I am trying to fix the FTBFS on the current rpms/ruby rawhide.

Below is the scratch build with the modification to print the output
of the checksec command below.
https://koji.fedoraproject.org/koji/taskinfo?taskID=105910607

```
diff --git a/ruby.spec b/ruby.spec
index 51ada32..f61c3fe 100644
--- a/ruby.spec
+++ b/ruby.spec
@@ -855,6 +855,7 @@ rm -rf
%{buildroot}%{gem_dir}/gems/rake-%{rake_version}/.github
 %check
 %if 0%{?with_hardening_test}
 # Check Ruby hardening.
+checksec --file=%{_vpath_builddir}/libruby.so.%{ruby_version}
 checksec --file=%{_vpath_builddir}/libruby.so.%{ruby_version} | \
   grep "Full RELRO.*Canary found.*NX enabled.*DSO.*No RPATH.*No
RUNPATH.*Yes.*\d*.*\d*.*libruby.so.%{ruby_version}"
 %endif
```

On only s390x build, there is another error in root.log. I am asking
how to fix it on devel@ mailing list now.

https://kojipkgs.fedoraproject.org//work/tasks/753/105910753/root.log

```
DEBUG util.py:442:  No matches found for the following disable plugin
patterns: local, spacewalk, versionlock
DEBUG util.py:442:  Error:-
DEBUG util.py:442:   Problem: conflicting requests
DEBUG util.py:442:- nothing provides nm needed by
checksec-2.6.0-5.fc40.noarch from build
DEBUG util.py:442:- nothing provides python3.12dist(unicorn) >=
1.0.2~rc1 needed by python3-pwntools-4.9.0-4.fc39.noarch from build
```

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  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

Re: Fedora 37 Ruby 3.1.4 and URI.parse FTBFS gems

2023-05-30 Thread Jun Aruga (he / him) 
On Mon, May 29, 2023 at 4:54 PM Jarek Prokop  wrote:
>
> Hi all,
>
> JFYI, latest Fedora 37 Ruby rebase broke a few Ruby package builds due to 
> change in the URI gem.
>
> recently I did a rebase for Ruby 3.1.4 to address 2 CVEs among other things.
> For one of those CVEs (ReDoS vulnerability in URI [0]), upstream merged URI 
> gem v0.12.0[1] and later to v0.12.1 [2] (full 3.1.3 -> 3.1.4 diff: [3]).
>
> The 0.12.0 brought a change, where URI.parse now returns empty string instead 
> of `nil` for empty host, this resulted in a few newly FTBFS packages.
> I have hit this recently with vagrant-libvirt and found out it is more than 
> that package, though not by much.
>
> Looking at koschei [4] FTBFS for rubygems on Fedora 37, there aren't that 
> many and some have been failing on F37 for longer time than Ruby 3.1.4 is in 
> Fedora 37.
> The current package set that is FTBFS in koschei on Fedora 37 for one reason 
> or another:
> rubygem-clockwork  rubygem-eventmachine rubygem-excon
> rubygem-hiredisrubygem-loofah   rubygem-memfs
> rubygem-multi_json rubygem-mysql2   rubygem-net-ssh
> rubygem-nifti  rubygem-rails-html-sanitizer rubygem-rake-contrib
> rubygem-rdoc   rubygem-redisrubygem-rest-client
> rubygem-ronn-ngrubygem-rubyzip  rubygem-selenium-webdriver
> rubygem-slim   rubygem-sprocketsrubygem-websocket-extensions
>
> Regards,
> Jarek
>
>
> [0] https://www.ruby-lang.org/en/news/2023/03/28/redos-in-uri-cve-2023-28755/
> [1] 
> https://github.com/ruby/ruby/commit/da27583cf364c0d69c085db4abf358c334a8eca1
> [2] 
> https://github.com/ruby/ruby/commit/8ce4ab146498879b65e22f1be951b25eebb79300
> [3] https://github.com/ruby/ruby/compare/v3_1_3...v3_1_4
> [4] 
> https://koschei.fedoraproject.org/search?q=rubygem-%2A_by=state-f37%2Crunning%2Cfailing%2Cname

Hi Jarek,
Thank you for the useful and detailed report! When we fix it, we may
find the upstream patch to pass the test with Ruby 3.1.4 on the
package upstream projects.

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  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

Re: SPDX Status for Rubygems in Fedora as of 2023-04-20

2023-04-25 Thread Jun Aruga (he / him) 
> Would it make sense to also add other committers/admins to the list as they 
> also have rights to push the SPDX "fix"?

It makes sense to me!

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  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

Re: WASM from Ruby - Lightning Chess Web App

2023-01-11 Thread Jun Aruga (he / him) 
Jarek, thanks for your feedback!

> Or you can go completely from source. Then you want to follow Ruby's upstream 
> README on wasm crosscompilation [4].
...
> [4] 
> https://github.com/ruby/ruby/tree/master/wasm#webassembly--wasi-port-of-ruby
...

Phillip,
I built Ruby WASM binarys following the link [4] above, building
WASM-SDK and wasmtime recently. So, I may help you if you have some
issues on the way.

It seems that there is also another way to build and run Ruby WASM
binaries with wasi-vfs.
https://www.ruby-lang.org/en/news/2022/12/25/ruby-3-2-0-released/ -
WASI based WebAssembly support
> In addition, we built a VFS on top of WASI so that we can easily pack Ruby 
> apps into a single .wasm file. This makes distribution of Ruby apps a bit 
> easier.

As Jarek said, the necessary RPM packages such as "wasi-libc" and
"wasmtime" to build and run WASM binaries are not ready. Perhaps, you
can try to build Ruby WASM binaries from source first, then you might
be able to give feedback to people who are trying to create
WebAssembly SIG.

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  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

Re: WASM from Ruby - Lightning Chess Web App

2023-01-09 Thread Jun Aruga (he / him) 
Hi Philip,
I added a Ruby SiG mailing list to TO.

Folks at Ruby SiG,
Could you take a look at the message below? Philip is trying to create
a RPM package including WASM built Ruby binaries. Your feedback is
helpful.

On Mon, Jan 9, 2023 at 11:00 AM Philip Rhoades  wrote:
>
> Jun,
>
>
> On 2023-01-09 00:36, Jun Aruga (he / him) wrote:
> > On Sun, Jan 8, 2023 at 11:51 AM Philip Rhoades via devel
> >  wrote:
> >>
> >> People,
> >>
> >> Over the holidays we had our irregular Family Lightning Chess
> >> competition (10 seconds per move) - I have not found an online web
> >> site
> >> that will work exactly with our rules and it occurs to me that this
> >> would be a nice project for me to get working via a Ruby2WASM project.
> >> If I could get that project working, it would allow the family to have
> >> at least annual electronic competitions for the times when not all the
> >> relatives can physically make it to the one place at the one time . .
> >>
> >> What do you think?
> >
> > Good idea!
>
>
> Good! - I wasn't sure if it was or note . .
>
>
> > Ruby 3.2 released a few weeks ago, started to support the WASM built
> > feature, and I guess that people want to use it easily.
>
>
> I certainly do!
>
>
> > The first choice for the packaging is to create WASM built binaries as
> > a sub package of "ruby" https://src.fedoraproject.org/rpms/ruby or to
> > create a new package with the new RPM spec file.
>
>
> I don't know about that but it would be good for me to get started with
> a "Hello World!" Ruby2WASM app and go from there . .

OK. I think trying to create a minimal RPM package such as "Hello
World" is a good idea if you have never experienced RPM packaging.
Then as your next step, you may be able to try to build by creating
your package by copying the current rpms/ruby's ruby.spec to e.g.
ruby-wasm.spec, and modifying it to build WASM binaries.

Tutorial: 
https://docs.fedoraproject.org/en-US/package-maintainers/Packaging_Tutorial_GNU_Hello/
Packaging Guide: https://docs.fedoraproject.org/en-US/packaging-guidelines/

> > We discussed if we shipped WASM binaries a bit in the ruby-sig@
> > mailing list. I can recommend you to join the list to discuss people
> > in the ruby related packages  if you like.
> >
> > * Ruby 3.2 - ruby-sig@
> >
> > https://lists.fedoraproject.org/archives/list/ruby-sig@lists.fedoraproject.org/thread/FK3XRKUICBS7HFZVEENSEGJ4ZMKCVNWF/
>
>
> Yes, I read that stuff and am subscribed to that list now.

OK. Nice!

> > Fedora WASM SIP might be launched. You can check the situation.
> >
> > * Web Assembly on Fedora: interested in a Fedora SIG to work on this?
> >
> > https://lists.fedoraproject.org/archives/list/de...@lists.fedoraproject.org/thread/JO2YYDQPC65EMQVO6UCHDV4SAKQNSGKV/
>
>
> Happy to join that list too but that is a much wider deal than the
> Ruby2WASM project?

Yes. right. I think it's about WASM things more than Ruby.
For example, it's about what you need to do to build WASM binaries of
Ruby, and which dependency RPM packages you need.

> Thanks!
>
> Phil.
> --
> Philip Rhoades
>
> PO Box 896
> Cowra  NSW  2794
> Australia
> E-mail:  p...@pricom.com.au

Thanks too!

-- 
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

Starting to use Zuul CI for other rubygem-* packages

2022-12-01 Thread Jun Aruga (he / him) 
Hi,
I just sent PR[1][2] to start to use Zuul CI for RubyGems, Bundler and
rubygem-* packages used in the Ruby module, as I can see it's useful
for rpms/ruby. I hope you are happy with it.

Perhaps we might be able to add the following packages to Zuul in the
future too.

* All the rubygem-* packages included in Koschei ruby-rails group.
  https://koschei.fedoraproject.org/groups/ruby-rails
* All the rubygem-* packages @ruby-packagers-sig

[1] https://pagure.io/fedora-project-config/pull-request/243
[2] How to add:
https://fedoraproject.org/wiki/Zuul-based-ci#Add_the_repository_into_the_Zuul_configuration

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  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

Re: gem install fails on rawhide

2022-11-12 Thread Jun Aruga (he / him) 
> But essentially we need to do something in the `ruby.spec` not to
> expose the redhat-rpm-config RPM or Red Hat specific RPMs such as
> package-notes RPM. Possible ways are below.
>
> A. Modify rbconfig.rb by such as `sed` command.
> B. Add another logic to create the `reconfig.rb` by `make rbconfig.rb`
> with extension flags, and ship it in the Ruby RPM.
> C. Update the configure script with proper arguments or command options.
>   https://src.fedoraproject.org/rpms/ruby/pull-request/117
>
> Feel free to take this task.

I think it's better to add the `gem install byebug` to Fedora CI for
the rpms/ruby.

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  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

gem install fails on rawhide

2022-11-12 Thread Jun Aruga (he / him) 
Hello,

I found the gem install  fails on the Ruby on the rawhide.

I reported it to the package-notes RPM.
https://bugzilla.redhat.com/show_bug.cgi?id=2142119

https://bugzilla.redhat.com/show_bug.cgi?id=2142119#c1

Maybe a temporary workaround we can do soon is to set the macro below
in the ruby.spec.

```
%undefine _package_note_file
```

But essentially we need to do something in the `ruby.spec` not to
expose the redhat-rpm-config RPM or Red Hat specific RPMs such as
package-notes RPM. Possible ways are below.

A. Modify rbconfig.rb by such as `sed` command.
B. Add another logic to create the `reconfig.rb` by `make rbconfig.rb`
with extension flags, and ship it in the Ruby RPM.
C. Update the configure script with proper arguments or command options.
  https://src.fedoraproject.org/rpms/ruby/pull-request/117

Feel free to take this task.

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  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

Re: Ruby 3.2

2022-11-10 Thread Jun Aruga (he / him) 
> >> I don't think that the former would be really valuable. Unless the RPM
> >> package Ruby would make it easier in some way.
> > I am suggesting that "we should rather not mention WASI, because the
> > RPM does not actually support it". That is what we did for our
> > document about the MJIT in the past in the RHEL side, as the MJIT
> > didn't work due to RHEL's hardening setting. Or just add note that
> > "the Ruby RPM doesn't support the WebAssemly. If you want to use the
> > feature, compile from the source."
> >
>
> I have dropped the section entirely. Because based on your explanation,
> I'd say that WebAssembly is currently out of scope, as long as we are
> not able to provide the WebAssembly Ruby blob.
>
>
> Thx a lot. Appreciate your help.

OK. That makes sense. Thanks.

I think the Ruby wasm's document could be improved. I just sent a PR
to improve that.

wasm/README.md: Add a note about the Ruby built for wasm.
https://github.com/ruby/ruby/pull/6707

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  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

Re: Ruby rawhide FTBFS

2022-11-09 Thread Jun Aruga (he / him) 
> I am afraid that Koschei will not pick up the builds without submitting
> updates unfortunately.

Here is a document and an upstream ticket that I am asking. But there
are priorities to be picked up or to be started.
https://fedoraproject.org/wiki/Koschei#Priorities
https://github.com/fedora-infra/koschei/issues/349

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  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

Re: Ruby 3.2

2022-11-09 Thread Jun Aruga (he / him) 
On Mon, Nov 7, 2022 at 10:44 AM Vít Ondruch  wrote:
>
>
> Dne 04. 11. 22 v 19:13 Jun Aruga (he / him) napsal(a):
> >> I have put together the change proposal:
> >>
> >> https://fedoraproject.org/wiki/Changes/Ruby_3.2
> >>
> >> Please review, although with exception of "Detailed Description"
> >> chapter, where the changes are described, it is basically just
> >> copy/paste of the Ruby 3.1 change proposal.
> >>
> >> I have marked the change as "ChangeReadyForWrangler" already. BTW
> >> everybody feel free to add yourselves as a change (co-)owner.
> > For the "WASI based WebAssembly support" feature, there is no way to
> > use this feature from Ruby RPM. Users need to build Ruby from the
> > source with a specific build target configure option. Does it make
> > sense to show the feature on the proposal page?
> >
>
> Could you please elaborate? Do you suggest we should describe how to
> prepare that build or that we should rather not mention WASI, because
> the RPM does not actually support it?

Sure. First, are you ok for the part 'For the "WASI based WebAssembly
support" feature, there is no way to use this feature from Ruby RPM.'?

That means
https://bugs.ruby-lang.org/issues/19053#note-3

When building ruby to run on the WebAssembly runtime with `configure
--host wasm32-unknown-wasi`, it works on the WebAssembly runtime
(wasmtime).

```
$ pwd
/home/jaruga/src/ruby-3.2.0-preview2_wasi_fedora

$ ./autogen.sh

$ ./configure LDFLAGS="-Xlinker -zstack-size=16777216" \
  -prefix=/usr/local/ruby-3.2.0-preview2-wasm32-wasi \
  --host wasm32-unknown-wasi \
  --with-destdir=./ruby-wasm32-wasi \
  --with-static-linked-ext \
  --with-ext=ripper,monitor

$ make
$ make install

$ wasmtime ruby-wasm32-wasi/usr/local/ruby-3.2.0-preview2-wasm32-wasi/bin/ruby
--mapdir /::./ruby-wasm32-wasi/ -- -e 'puts RUBY_PLATFORM'
wasm32-wasi
```

But the binary doesn't work on normal use.

```
$ ruby-wasm32-wasi/usr/local/ruby-3.2.0-preview2-wasm32-wasi/bin/ruby -v
bash: ruby-wasm32-wasi/usr/local/ruby-3.2.0-preview2-wasm32-wasi/bin/ruby:
cannot execute binary file: Exec format error

$ ruby-wasm32-wasi/usr/local/ruby-3.2.0-preview2-wasm32-wasi/bin/ruby
-e 'puts "a"'
bash: ruby-wasm32-wasi/usr/local/ruby-3.2.0-preview2-wasm32-wasi/bin/ruby:
cannot execute binary file: Exec format error
```

Because the binary format is different.

```
$ file /usr/bin/ruby-mri
/usr/bin/ruby-mri: ELF 64-bit LSB pie executable, x86-64, version 1
(SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2,
BuildID[sha1]=37b172d9897934e511f5e8496b7409471488a99e, for GNU/Linux
3.2.0, stripped

$ file ruby-wasm32-wasi/usr/local/ruby-3.2.0-preview2-wasm32-wasi/bin/ruby
ruby-wasm32-wasi/usr/local/ruby-3.2.0-preview2-wasm32-wasi/bin/ruby:
WebAssembly (wasm) binary module version 0x1 (MVP)
```

> I don't think that the former would be really valuable. Unless the RPM
> package Ruby would make it easier in some way.

I am suggesting that "we should rather not mention WASI, because the
RPM does not actually support it". That is what we did for our
document about the MJIT in the past in the RHEL side, as the MJIT
didn't work due to RHEL's hardening setting. Or just add note that
"the Ruby RPM doesn't support the WebAssemly. If you want to use the
feature, compile from the source."

-- 
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

Re: Ruby 3.2

2022-11-04 Thread Jun Aruga (he / him) 
> I have put together the change proposal:
>
> https://fedoraproject.org/wiki/Changes/Ruby_3.2
>
> Please review, although with exception of "Detailed Description"
> chapter, where the changes are described, it is basically just
> copy/paste of the Ruby 3.1 change proposal.
>
> I have marked the change as "ChangeReadyForWrangler" already. BTW
> everybody feel free to add yourselves as a change (co-)owner.

For the "WASI based WebAssembly support" feature, there is no way to
use this feature from Ruby RPM. Users need to build Ruby from the
source with a specific build target configure option. Does it make
sense to show the feature on the proposal page?

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  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

Re: Ruby 3.2

2022-11-04 Thread Jun Aruga (he / him) 
> Thanks for your input. I will create a pull-request to the private-ruby-3.2 
> branch to add the YJIT feature.

Here is the PR.

WIP: Enable YJIT feature.
https://src.fedoraproject.org/rpms/ruby/pull-request/139

I plan to test the YJIT and check the performance on the mock environment.
https://github.com/Shopify/yjit-bench

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  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

Re: Ruby rawhide FTBFS

2022-11-04 Thread Jun Aruga (he / him) 
On Thu, Nov 3, 2022 at 8:06 PM Jun Aruga (he / him)  wrote:
>
> > Here is the PR. Someone, please review.
> > https://src.fedoraproject.org/rpms/rubygems/pull-request/4
>
> Here is the status. Review please. Thanks.

I was able to build the all the rpms/ruby and rubygems and
rubygem-bundler. Thanks for your help.
Just note I didn't submit the rpms/ruby build on f37, f36, f35 to the
Bodhi, as it is just to fix the FTBFS.

> rpms/ruby
> * rawhide: done (built)
> * f37: https://src.fedoraproject.org/rpms/ruby/pull-request/136
> * f36: https://src.fedoraproject.org/rpms/ruby/pull-request/137
> * f35: https://src.fedoraproject.org/rpms/ruby/pull-request/138

https://koji.fedoraproject.org/koji/packageinfo?packageID=125

> rpms/rubygems
> * rawhide: https://src.fedoraproject.org/rpms/rubygems/pull-request/4
> (in review)
>
> rpms/rubygem-bundler
> * rawhide: https://src.fedoraproject.org/rpms/rubygem-bundler/pull-request/6
>   The rubygem-bundler PR should be merged and built before the
> rpms/rubygems because rubygems depends on the latest version of the
> rubygem-bundler.

The Koschei has not worked for ruby rawhide since around 1 month ago,
but after reporting to the Koschei project, it started to work again.
https://github.com/fedora-infra/koschei/issues/349
https://koschei.fedoraproject.org/package/ruby

-- 
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

Re: Ruby rawhide FTBFS

2022-11-03 Thread Jun Aruga (he / him) 
> Here is the PR. Someone, please review.
> https://src.fedoraproject.org/rpms/rubygems/pull-request/4

Here is the status. Review please. Thanks.

rpms/ruby
* rawhide: done (built)
* f37: https://src.fedoraproject.org/rpms/ruby/pull-request/136
* f36: https://src.fedoraproject.org/rpms/ruby/pull-request/137
* f35: https://src.fedoraproject.org/rpms/ruby/pull-request/138

rpms/rubygems
* rawhide: https://src.fedoraproject.org/rpms/rubygems/pull-request/4
(in review)

rpms/rubygem-bundler
* rawhide: https://src.fedoraproject.org/rpms/rubygem-bundler/pull-request/6
  The rubygem-bundler PR should be merged and built before the
rpms/rubygems because rubygems depends on the latest version of the
rubygem-bundler.

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  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

Re: Ruby rawhide FTBFS

2022-11-03 Thread Jun Aruga (he / him) 
> > Not surprisingly, RubyGems fail as well 﫤
> >
> >
> > https://koschei.fedoraproject.org/package/rubygems?collection=f38
>
> Okay, the rpms/rubygems is next after the rpms/ruby.

Here is the PR. Someone, please review.
https://src.fedoraproject.org/rpms/rubygems/pull-request/4

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  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

Re: Ruby rawhide FTBFS

2022-11-03 Thread Jun Aruga (he / him) 
> >> https://bodhi.fedoraproject.org/updates/?packages=git
> > The git 2.38.1 is on f37, f36 and f35 too.
> > Maybe it's better to push this PR commit to these fedoras too after
> > merging the rawhide PR.
> >
>
> Right, I have mentioned this in the PR but you are apparently on top of
> it. Great!

OK. I will fix this issue and build on the old Fedoras too.

> BTW if you have a spare cycles, please review the Rawhide changes which
> were committed after the F37 was branched. I guess they could be
> included into F37, but I have not checked (particularly the enabled
> package notes, not sure if the changes landed in F37, but my guess is
> that they have landed there). Thx

It seems that the rawhide specific change below should work on Fedora
37 (and 36) too. I will backport the commit to the f37 too.
https://src.fedoraproject.org/rpms/ruby/c/588a4ae9f02928d7bedbcf46a739d36b0a76e632?branch=rawhide

The issue comes from the redhat-rpm-config and it was fixed in
redhat-rpm-config-210-1 fc36, fc37, fc38 (rawhide).
https://bugzilla.redhat.com/show_bug.cgi?id=2043092#c66

So, I will test by building the rubygem-nio4r package on the built
Ruby just in case. This is a step to verify the issue that you
reported on the Bugzilla ticket.

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  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

Re: Ruby rawhide FTBFS

2022-11-02 Thread Jun Aruga (he / him) 
On Mon, Oct 31, 2022 at 6:54 PM Vít Ondruch  wrote:
>
> Good catch.

Here is the PR to the rpms/ruby rawhide.
https://src.fedoraproject.org/rpms/ruby/pull-request/135#

> Not surprisingly, RubyGems fail as well 﫤
>
>
> https://koschei.fedoraproject.org/package/rubygems?collection=f38

Okay, the rpms/rubygems is next after the rpms/ruby.

> And looking at git updates, I'd be not surprised if also older Fedoras
> get broken soon:
>
>
> https://bodhi.fedoraproject.org/updates/?packages=git

The git 2.38.1 is on f37, f36 and f35 too.
Maybe it's better to push this PR commit to these fedoras too after
merging the rawhide PR.

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  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

Ruby rawhide FTBFS

2022-10-27 Thread Jun Aruga (he / him) 
Just a quick note.
Right now the rpms/ruby rawhide is FTBFS.[1]

```
  1) Failure:
TestGemSourceGit#test_checkout_submodules
[/builddir/build/BUILD/ruby-3.1.2/test/rubygems/test_gem_source_git.rb:72]:
fatal: transport 'file' not allowed
fatal: clone of
'/builddir/build/BUILD/ruby-3.1.2/tmp/test_rubygems_20221027-81957-35u31l/git/b'
into submodule path
'/builddir/build/BUILD/ruby-3.1.2/tmp/test_rubygems_20221027-81957-35u31l/git/a/b'
failed
Finished tests in 975.746481s, 21.9330 tests/s, 2819.2661 assertions/s.
21401 tests, 2750889 assertions, 1 failures, 0 errors, 55 skips
```

The reason is the [2]. The git-core 2.38.1-1.fc38 is used as a
dependency on the rawhide now.
This failure happens on Git >= 2.38.1. This failure doesn't happen on
Git 2.28.0.[3]

The patch is [4][5]. I confirmed it passed the tests on the
private-ruby-3.2 branch.

As I will work for Fedora again next Wednesday, feel free to take and
apply the patch to the rawhide branch and backport.

[1] https://koji.fedoraproject.org/koji/taskinfo?taskID=93491139
[2] 
https://github.blog/2022-10-18-git-security-vulnerabilities-announced/#cve-2022-39253
[3] https://twitter.com/hsbt/status/1582565364700893184 (Japanese)
[4] 
https://github.com/rubygems/rubygems/commit/e29c79d1891a656ec50c8bd4ff6d8b11ca393f28
[5] https://github.com/ruby/ruby/commit/dae843f6b7502f921a7e66f39e3714a39d860181

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  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

Re: Ruby 3.2

2022-10-27 Thread Jun Aruga (he / him) 
On Thu, Oct 27, 2022 at 4:14 PM Jarek Prokop  wrote:

> Hi,
> On 10/27/22 15:14, Jun Aruga (he / him) wrote:
>
> On Fri, Oct 21, 2022 at 3:39 PM Vít Ondruch  
>  wrote:
>
> Dne 21. 10. 22 v 13:56 Mamoru TASAKA napsal(a):
>
> Vít Ondruch wrote on 2022/10/17 23:24:
>
> Hi again,
>
> Here is yet another version from Friday:
> https://koji.fedoraproject.org/koji/taskinfo?taskID=92978738
>
> Nothing really special from Ruby POV, but I have enabled
> out-of-source build, as was previously discussed here:
> https://src.fedoraproject.org/rpms/ruby/pull-request/120
> https://src.fedoraproject.org/rpms/ruby/pull-request/122
>
> So while this should not have any influence on resulting package, it
> might come handy when somebody wants to clean the source tree and
> play with e.g. different configuration options or what not.
>
>
> Vít
>
>
> Thank you.
>
> By the way, do you have some plan to bring ruby 3.2 development rpm to
> f38 buildroot earlier than 2022 Christmas (say, around 2022/11/E)?
>
> Thanks for the work.
> I am trying to build on the private-ruby-3.2 branch.
> Where is the SRPM file including the ruby-3.2.0-70bc8cc6c2.tar.xz ?
> Could you share?
>
> I have been testing Ruby 3.2.0 preview2. The outcome is 
> below.https://www.ruby-lang.org/en/news/2022/09/09/ruby-3-2-0-preview2-released/
>
> ## WebAssembly support
>
> This is one of the new features in Ruby 3.2.0, and that is to build a
> Ruby source for the WebAssembly target, and then run a Ruby code on
> the Ruby on the Web Assembly runtime.
> But this feature is exclusive from the current Ruby in the Ruby RPM.
> When building Ruby for that, we can not run the Ruby without the
> WebAssembly runtime.
> So, I think it's not realistic to include the feature in the Ruby RPM.
>
> I do not think any distribution will be able to reasonably support this.
>
> From my understanding of WASM, it is required to crosscompile everything
> needed to run the application,
> so that it is usable in browser or other WASM runtimes.
>
> It is a feature that upstream supports, which is nice from language
> usability perspective, but not something we are able to or want to
> reasonably support.
> Those who want to use it, need to crosscompile whole Ruby from source, as
> is the case with any other C application.
>
> Or, such people can download the .src.rpm unpack it and adjust the
> specfile to match their needs.
>
> I think it is comparable to mruby (the lightweight embeddable ruby):
> https://github.com/mruby/mruby
> These kinds of applications are better fine tuned by app developers
> themselves than the Linux distribution packagers.
>

Hi Jarek,
Thanks for sharing the info. For the mruby, in the past I developed an iOS
application on iPad and iPhone. In the application build process, I built
an Objective-C app with C or C++ library sources. The libraries are managed
as static libraries. So, I guess the mruby's case is something like this.
For the WASM, the application developers can build the Ruby with the WASM
target when building their applications.


> See devel@ mailing list - Subject: "Packaging a cross-compilation
> environment (wasi-libc)" for details.
>
> ## Regexp timeout
>
> I found a small issue on a new feature. Then it was 
> fixed.https://bugs.ruby-lang.org/issues/19055
>
> ## YJIT support
>
> YJIT is to improve the performance of Ruby code by using Rust. It's
> like MJIT (previously called JIT) by using gcc or clang.
>
> I think adding this feature in the Ruby RPM is realistic. So, I tested
> this feature with the upstream Ruby source code in some cases.
>
> Because in my understanding the YJIT is only available with the `ruby
> --yijt` option. It seems that it doesn't affect the current Ruby
> features. Possibly we need to add "BuildRequires rust cargo", and also
> needs a dependency rust (and cargo?) to run the `ruby --yjit`.
>
> ```
> $ ./configure --enable-yjit ...
> $ make
> $ make install
>
> $ ruby --help
> ...
> Features:
>   gemsrubygems (only for debugging, default: enabled)
> ...
>   mjitC compiler-based JIT compiler (default: disabled)
>   yjitin-process JIT compiler (default: disabled) # <=
> This line appears. And this feature is only enabled with the `ruby
> --yjit`.
> ...
>
> $ ruby --yjit my_script.rb
> ```
>
> See the following links for 
> details.https://bugs.ruby-lang.org/issues/18481https://github.com/ruby/ruby/blob/master/doc/yjit/yjit.md#installation
>
> I read that document, we should only need the `%{_bindir}/rustc`. Ruby
> upstream was successful in keeping the
> production version without any external dependencies a

Re: Ruby 3.2

2022-10-27 Thread Jun Aruga (he / him) 
> Thanks for the work.
> I am trying to build on the private-ruby-3.2 branch.
> Where is the SRPM file including the ruby-3.2.0-70bc8cc6c2.tar.xz ?
> Could you share?

I found the ruby-3.2.0-70bc8cc6c2.tar.xz at
https://koji.fedoraproject.org/koji/taskinfo?taskID=92950720 . You
already shared it.

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  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

Re: Ruby 3.2

2022-10-27 Thread Jun Aruga (he / him) 
On Fri, Oct 21, 2022 at 3:39 PM Vít Ondruch  wrote:
>
>
> Dne 21. 10. 22 v 13:56 Mamoru TASAKA napsal(a):
> > Vít Ondruch wrote on 2022/10/17 23:24:
> >> Hi again,
> >>
> >> Here is yet another version from Friday:
> >>
> >> https://koji.fedoraproject.org/koji/taskinfo?taskID=92978738
> >>
> >> Nothing really special from Ruby POV, but I have enabled
> >> out-of-source build, as was previously discussed here:
> >>
> >> https://src.fedoraproject.org/rpms/ruby/pull-request/120
> >>
> >> https://src.fedoraproject.org/rpms/ruby/pull-request/122
> >>
> >> So while this should not have any influence on resulting package, it
> >> might come handy when somebody wants to clean the source tree and
> >> play with e.g. different configuration options or what not.
> >>
> >>
> >> Vít
> >>
> >
> > Thank you.
> >
> > By the way, do you have some plan to bring ruby 3.2 development rpm to
> > f38 buildroot earlier than 2022 Christmas (say, around 2022/11/E)?

Thanks for the work.
I am trying to build on the private-ruby-3.2 branch.
Where is the SRPM file including the ruby-3.2.0-70bc8cc6c2.tar.xz ?
Could you share?

I have been testing Ruby 3.2.0 preview2. The outcome is below.
https://www.ruby-lang.org/en/news/2022/09/09/ruby-3-2-0-preview2-released/

## WebAssembly support

This is one of the new features in Ruby 3.2.0, and that is to build a
Ruby source for the WebAssembly target, and then run a Ruby code on
the Ruby on the Web Assembly runtime.
But this feature is exclusive from the current Ruby in the Ruby RPM.
When building Ruby for that, we can not run the Ruby without the
WebAssembly runtime.
So, I think it's not realistic to include the feature in the Ruby RPM.

See devel@ mailing list - Subject: "Packaging a cross-compilation
environment (wasi-libc)" for details.

## Regexp timeout

I found a small issue on a new feature. Then it was fixed.
https://bugs.ruby-lang.org/issues/19055

## YJIT support

YJIT is to improve the performance of Ruby code by using Rust. It's
like MJIT (previously called JIT) by using gcc or clang.

I think adding this feature in the Ruby RPM is realistic. So, I tested
this feature with the upstream Ruby source code in some cases.

Because in my understanding the YJIT is only available with the `ruby
--yijt` option. It seems that it doesn't affect the current Ruby
features. Possibly we need to add "BuildRequires rust cargo", and also
needs a dependency rust (and cargo?) to run the `ruby --yjit`.

```
$ ./configure --enable-yjit ...
$ make
$ make install

$ ruby --help
...
Features:
  gemsrubygems (only for debugging, default: enabled)
...
  mjitC compiler-based JIT compiler (default: disabled)
  yjitin-process JIT compiler (default: disabled) # <=
This line appears. And this feature is only enabled with the `ruby
--yjit`.
...

$ ruby --yjit my_script.rb
```

See the following links for details.
https://bugs.ruby-lang.org/issues/18481
https://github.com/ruby/ruby/blob/master/doc/yjit/yjit.md#installation
https://github.com/Shopify/yjit-bench

Jun

--
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  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

Re: Ruby 3.2

2022-10-13 Thread Jun Aruga (he / him) 
Thanks for the work, Mamoru.

> * Removal of File.exists? / Object#=~ / "tainted"ness affects several pacakges

It seems the method was removed in Ruby 3.2.0.
https://github.com/ruby/ruby/blob/v3_2_0_preview2/NEWS.md#removed-methods

> The following deprecated methods are removed.
> ...
> * `File.exists?` [[Feature #17391]]
> ...

> * rubygem-jekyll seems to be affected by keywords / positional argument 
> treatment
>change??

Not sure.

> By the way, is it better to create "central" bugzilla ticket to keep track of 
> ruby32
> related issues for each package?

It sounds like a good idea.

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  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

Re: Embedded fonts in HTML documentation

2022-10-07 Thread Jun Aruga (he / him) 
> Can one assume that updates to the Ruby packaging process will remove
> embedded fonts from all Ruby gems with generated html documentation?
> This would help with current reviews.
>
> [1]
> https://docs.fedoraproject.org/en-US/packaging-guidelines/#_avoid_bundling_of_fonts_in_other_packages

Possibly the steps to remove fonts from Ruby gems is

1 Update rpms/ruby RPM package (including rubygem-rdoc is a
sub-package of the rpms/ruby) with the rdoc logic to avoid generating
duplicated font logic.
2. When someone will build rpms/rubygem-foo with `fedpkg build`, the
rubygem-foo's RPM is built without duplicated font files.

It's not like building all the rpms/rubygem-* packages at the same time.

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  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

Re: Ruby 3.2

2022-09-19 Thread Jun Aruga (he / him) 
On Fri, Sep 16, 2022 at 7:03 PM Vít Ondruch  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  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

Re: RubyGems 3.3.22 + Bundler 2.3.22 in Rawhide

2022-09-15 Thread Jun Aruga (he / him) 
On Thu, Sep 15, 2022 at 4:34 PM Vít Ondruch  wrote:
>
> Hi,
>
> Since the independent RubyGems package was FTBFS for some time and there
> was no Ruby update for a while, I have decided that it is probably about
> the time to try to fix and update RubyGems. Since RubyGems are nowadays
> shipped with Bundler and we enforce that Bundler has to be the same or
> newer version then sipped with them, this also forced update or Bundler.
> And here it is:
>
> https://bodhi.fedoraproject.org/updates/FEDORA-2022-8d0a0920e1
>
> Since the independent packages were not updated and used for a while,
> please give it some careful testing and report back if there is
> something wrong. Hopefully there won't be any issues, but one never know.

Wow, this is great. I guess previously the rpms/rubygem-bundler was
1.x. The independent package might be helpful to test with the new
RubyGems and Bundler.
Thanks.

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  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

Re: rpms/ruby module stream branches build failures

2022-08-16 Thread Jun Aruga (he / him) 
On Wed, Jul 27, 2022 at 4:08 PM Vít Ondruch  wrote:
>
>
> Dne 26. 07. 22 v 21:36 Jun Aruga (he / him) napsal(a):
> >>>> I'd suggest against building Ruby 3.0 on F36+
> >>> Oh thanks. I missed the part.
> >>> How about using openssl1.1-devel
> >>
> >> Is it really available? I know there were some discussions in the
> >> context of old Python support, but I was under impression that while
> >> openssl1.1 is available, the -devel packages is not.
> >>
> >> So for modules, it could be actually an option.
> > Not sure about it. We need to ask the maintainer maybe at devel@.
> >
>
> Or test it? :)

I am testing it now on the stream-ruby-2.7 branch.
https://src.fedoraproject.org/rpms/ruby/pull-request/128

The openssl1.1-devel is used from several RPMs including python3.7 and
python3.6 RPMs.
A core dump in the tests. Let me know if you know the issue and how to fix.
https://kojipkgs.fedoraproject.org//work/tasks/8548/90868548/build.log

-- 
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

Re: rpms/ruby module stream branches build failures

2022-07-26 Thread Jun Aruga (he / him) 
> >> I'd suggest against building Ruby 3.0 on F36+
> > Oh thanks. I missed the part.
> > How about using openssl1.1-devel
>
>
> Is it really available? I know there were some discussions in the
> context of old Python support, but I was under impression that while
> openssl1.1 is available, the -devel packages is not.
>
> So for modules, it could be actually an option.

Not sure about it. We need to ask the maintainer maybe at devel@.

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  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 on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: rpms/ruby module stream branches build failures

2022-07-21 Thread Jun Aruga (he / him) 
On Wed, Jul 20, 2022 at 4:04 PM Vít Ondruch  wrote:

>
> IOW this is OpenSSL 3.x issue. There is no simple way around unless you want
>
> 1) Backport the OpenSSL 3.x patches from Ruby 3.0
>
> 2) Use some other workaround such as including upstream version of
> OpenSSL gem.
>
> I'd suggest against building Ruby 3.0 on F36+

Oh thanks. I missed the part.
How about using openssl1.1-devel instead of openssl-devel in only Ruby
2.7 (stream-ruby-2.7), 2.6 (stream-ruby-2.6) and 2.5 (ruby-2.5)? I
don't see any problems in this way.

The openssl1.1 RPM is available on F34~F37(rawhide).
https://src.fedoraproject.org/rpms/openssl1.1
https://koji.fedoraproject.org/koji/packageinfo?packageID=32363

> > ## stream-ruby-2.6
> >
> > ./configure: line 4122: syntax error near unexpected token `fi'
> > ./configure: line 4122: `fi'
> >
> > ## ruby-2.5
> >
> > ./configure: line 4101: syntax error near unexpected token `fi'
> > ./configure: line 4101: `fi'
> >
>
> My guess would be some autotools compatibility or some wrongly applied
> patch? I know that at times, we need to change the autotools version.
> But this was typically done just in RHEL AFAIR.

Hmm, I didn't find any patch on RHEL. I may check more about this
issue when I have time.

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  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 on the list, report it: 
https://pagure.io/fedora-infrastructure