On Wed, Jan 26, 2022 at 2:00 PM Vít Ondruch <vondr...@redhat.com> wrote: > > So Fedora mass rebuild has finished (although I am not sure how does it > look with the signing of the packages), therefore we should be good to > go. I have requested side tag: > > > ~~~ > > $ fedpkg request-side-tag > Side tag 'f36-build-side-49941' (id 49941) created. > Use 'fedpkg build --target=f36-build-side-49941' to use it. > Use 'koji wait-repo f36-build-side-49941' to wait for the build repo to > be generated. > > ~~~ > > > and Ruby 3.1 is already built there as you can see at: > > > https://koji.fedoraproject.org/koji/builds?inherited=0&tagID=49941&order=-build_id&latest=1 > > > or using: > > > ~~~ > $ koji list-tagged f36-build-side-49941 > ~~~ > > > 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 the package and just fire rebuild, but please ensure that > you are using f36-build-side-49941 build target, i.e. the build command > should look like: > > > ~~~ > $ fedpkg build --target f36-build-side-49941 > ~~~ > > > Please be careful, because if you, by a chance, omit the > f36-build-side-49941 target, you'll be building against Ruby 3.0 which > is not what you want. > > If you won't do it by yourself, I'll be rebuilding all packages after I > am finished with my packages. I'll be using fermig [1] to help me with > that. If you don't want me to touch your packages for whatever reason, > please let me know. > > As always, any help/testing/feedback is welcome. Hellom
I've started my mass rebuild script[1] which will build all the packages in the ruby-packagers-sig [2] and also which I own [3]. The scratch build, along with other checks[*] is done prior to that, of course. Here [4] is the list of currently targeted packages, with dependency on `libruby.so.3.0()`. Please let me know if you want me to skip some packages. [*] Previous git entries are checked for changelog entries I've encountered in previous years (see script above). The builds will retry on failure, as well as the scratch-builds will retry in another pass (in case there are dependency loops). Example builds[5][6]. [1] https://gist.github.com/154a9f1863cfdadae46c7d7ead359613 [2] https://github.com/pvalena/theprototype/blob/main/fedora/list_group_packages.sh [3] https://github.com/pvalena/theprototype/blob/main/fedora/list_owned_packages.sh [4] https://gist.github.com/pvalena/f48bce8c0e54b6222d51ecafdc421654 [5] https://koji.fedoraproject.org/koji/taskinfo?taskID=81946328 [6] https://koji.fedoraproject.org/koji/taskinfo?taskID=81946627 Regards, Pavel > > > > Vít > > > [1] https://github.com/fedora-ruby/fermig > _______________________________________________ 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
