I have just noticed, that Ruby in Rawhide got broken with ruby-3.3.1-8.fc41. It seems that generators do not work properly and we don't have generated `rubygem()` provides in e.g. ruby-default-gems. I suspect that this might be related to RPM 4.20, because I am not aware of any other changes.
I have asked to untag that build https://pagure.io/releng/issue/12150 and investigate tomorrow.
Sorry for inconvenience
Vít
This is the problem:
~~~
... snip ...
Processing files: ruby-default-gems-3.3.1-8.fc41.noarch make: *** /builddir/build/BUILD/ruby-3.3.1/redhat-linux-build: No such file or directory. Stop.
... snip ...
~~~
Vít
Dne 06. 06. 24 v 19:36 Vít Ondruch napsal(a):
I have just noticed, that Ruby in Rawhide got broken with ruby-3.3.1-8.fc41. It seems that generators do not work properly and we don't have generated `rubygem()` provides in e.g. ruby-default-gems. I suspect that this might be related to RPM 4.20, because I am not aware of any other changes.
I have asked to untag that build https://pagure.io/releng/issue/12150 and investigate tomorrow.
Sorry for inconvenience
Vít
The ruby-3.3.1-8.fc41 was untagged a while ago and now I have pushed fix into Ruby 3.3.2 PR:
https://src.fedoraproject.org/fork/vondruch/rpms/ruby/c/42b0e43e5a8ef84cfc2a...
In short, due to changes in RPM 4.20, the `%{_builddir}` macro expands differently on different places of RPM. I have reported this upstream:
https://github.com/rpm-software-management/rpm/issues/3151
Vít
Dne 06. 06. 24 v 20:11 Vít Ondruch napsal(a):
This is the problem:
... snip ... Processing files: ruby-default-gems-3.3.1-8.fc41.noarch make: *** /builddir/build/BUILD/ruby-3.3.1/redhat-linux-build: No such file or directory. Stop. ... snip ...
Vít
Dne 06. 06. 24 v 19:36 Vít Ondruch napsal(a):
I have just noticed, that Ruby in Rawhide got broken with ruby-3.3.1-8.fc41. It seems that generators do not work properly and we don't have generated `rubygem()` provides in e.g. ruby-default-gems. I suspect that this might be related to RPM 4.20, because I am not aware of any other changes.
I have asked to untag that build https://pagure.io/releng/issue/12150 and investigate tomorrow.
Sorry for inconvenience
Vít
This is resolved now.
Vít
Dne 07. 06. 24 v 12:35 Vít Ondruch napsal(a):
The ruby-3.3.1-8.fc41 was untagged a while ago and now I have pushed fix into Ruby 3.3.2 PR:
https://src.fedoraproject.org/fork/vondruch/rpms/ruby/c/42b0e43e5a8ef84cfc2a...
In short, due to changes in RPM 4.20, the `%{_builddir}` macro expands differently on different places of RPM. I have reported this upstream:
https://github.com/rpm-software-management/rpm/issues/3151
Vít
Dne 06. 06. 24 v 20:11 Vít Ondruch napsal(a):
This is the problem:
... snip ... Processing files: ruby-default-gems-3.3.1-8.fc41.noarch make: *** /builddir/build/BUILD/ruby-3.3.1/redhat-linux-build: No such file or directory. Stop. ... snip ...
Vít
Dne 06. 06. 24 v 19:36 Vít Ondruch napsal(a):
I have just noticed, that Ruby in Rawhide got broken with ruby-3.3.1-8.fc41. It seems that generators do not work properly and we don't have generated `rubygem()` provides in e.g. ruby-default-gems. I suspect that this might be related to RPM 4.20, because I am not aware of any other changes.
I have asked to untag that build https://pagure.io/releng/issue/12150 and investigate tomorrow.
Sorry for inconvenience
Vít
ruby-sig@lists.fedoraproject.org