I am considering a PR by Vít Ondruch for cucumber-messages[1] that would build rubygem-cucumber-messages as a subpackage rather than maintaining it as a separate source package. I am generally inclined to favor the proposal, but it seems to me that it represents an exception to the “MUST” requirement to package RubyGem libraries from the released gem archives. I’ve therefore raised the issue on the Fedora Packaging Committee tracker[3]. The purpose of this email is to raise visibility of that issue among Ruby packagers, and to solicit input from knowledgeable and interested parties.
[1] https://src.fedoraproject.org/rpms/cucumber-messages/pull-request/2
[2] https://docs.fedoraproject.org/en-US/packaging-guidelines/Ruby/#_rubygems
[3] https://pagure.io/packaging-committee/issue/1512
Hi everybody,
Ruby 4.0 is out and it is time for Ruby mass rebuild. First of all, I'd
like to thank to Mamoru for the preparation and lot of work all around.
I really appreciate that.
From what I have been observing and discussing with Vít, I think we are
well prepared for the rebuild, therefore I have requested side-tag:
~~~
$ fedpkg request-side-tag
Side tag 'f44-build-side-125767' (id 125767) created.
Use 'fedpkg build --target=f44-build-side-125767' to use it.
Use 'koji wait-repo f44-build-side-125767' to wait for the build repo to
be generated.
~~~
Ruby 4.0 was merged [1] and the build is in progress:
https://koji.fedoraproject.org/koji/taskinfo?taskID=140833816
You can see the tag rebuild progress in:
https://koji.fedoraproject.org/koji/builds?inherited=0&tagID=125767&order=-…
You can alternatively also use:
~~~
$ koji list-tagged f44-build-side-125767
~~~
Now this is a list of packages, which very likely needs rebuild:
~~~
$ dnf repoquery --disablerepo=* --enablerepo=rawhide
--enablerepo=rawhide-source --arch=src --whatrequires 'ruby-devel' |
sort | uniq
~~~
You can take such package, bump the release and just fire rebuild, but
please ensure that you are using f44-build-side-125767 build target,
i.e. the build command should look like:
~~~
$ fedpkg build --target f44-build-side-125767
~~~
Please be careful, because if you, by a chance, omit the
f42-build-side-103200 target, you'll be building against Ruby 3.4 which
is not what you want.
The side tag might not get autorefreshed, it can be requested like:
~~~
$ koji wait-repo f44-build-side-125767 --build ruby-4.0.0-30.fc44
The --request option is recommended for faster results
This tag is not configured for automatic regeneration
$ koji wait-repo f44-build-side-125767 --build ruby-4.0.0-30.fc44 --request
~~~
If you won't do it by yourself, I'll be rebuilding all packages after I
am finished with my packages. I'll try to use fermig [2] to help me with
that. If you don't want me to touch your packages for whatever reason,
please let me know.
Any help/testing/feedback is welcome.
Jarek
[1] https://src.fedoraproject.org/rpms/ruby/pull-request/222
[2] https://github.com/fedora-ruby/fermig