On 9/20/23 19:41, Pavel Valena wrote:
Hello,
I decided to do some more testing, and found out that gem install
doesn't work:
```
<...snip...>
$ gem install rails
<internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:128:in
`require': libruby.so.3.2: cannot open shared object file: No such
file or directory - /usr/lib64/gems/ruby/stringio-3.0.8/stringio.so
(LoadError)
^ Not sure how, but stringio is probably the wrong binary version? Some
env pollution?
Trying locally in a rawhide Fedora container with your copr (skipping
setting up the copr...):
```
$ podman run --rm -it registry.fedoraproject.org/fedora:rawhide
# dnf install -y ruby.3.3.0~20230905git7c8932365f-182.fc40
# gem install rails
Fetching zeitwerk-2.6.11.gem
Successfully installed zeitwerk-2.6.11
Fetching thor-1.2.2.gem
Successfully installed thor-1.2.2
<...snip... It fails later due to missing build deps>
```
Regards,
Jarek
from
<internal:/usr/share/rubygems/rubygems/core_ext/kernel_require.rb>:128:in
`require'
<...snip...>
I didn't try with your latest version.
Regards,
Pavel
On Mon, Sep 18, 2023 at 6:24 PM Vít Ondruch <vondr...@redhat.com> wrote:
Hi,
Ruby 3.3 Preview 2 was released last week and here I am with the
updated
version. You can find the changes in my PR:
https://src.fedoraproject.org/rpms/ruby/pull-request/159
and here is the associated scratch build:
https://koji.fedoraproject.org/koji/taskinfo?taskID=106353657
I have not noticed anything particularly interesting in that release.
However, I have fixed and improved the macros I was talking about.
For
clarity (and probably backport), I have extracted them into
separate commit:
https://src.fedoraproject.org/fork/vondruch/rpms/ruby/c/d500de24cdcb4d848ab3df29d76f711104b3683e
This commit introduces `%{gem_name_version}` macro, which by default
does `%{gem_name}-%{version}%{?prerelease}`. Or if called with custom
gem name, such as `%gem_name_version foo`, the action is
`%{1}-%{expand:%{%{1}_version}}%{?prerelease}`. This assumes that
there
is `%{foo_version}` defined for correct output.
This macro is later reused in all `%gem_` macros, which now also
accept
custom gem name.
There is also additional `-d` option for `%gem_spec` macro, which
refers
to the .gemspec of default gems.
As always, feedback is appreciated via all common channels.
Vít
_______________________________________________
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-sig mailing list --ruby-sig@lists.fedoraproject.org
To unsubscribe send an email toruby-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-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
