Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Can you branch and build rapidyaml for EPEL10? Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Yes, I would like to do this. Since I’ll be stuck maintaining API/ABI compatibility indefinitely once I branch rapidyaml, I would like to get Rawhide updated to the latest version first so I can branch that. There were some regressions in 0.7.0, https://github.com/biojppm/rapidyaml/issues/440, which were mostly straightened out in 0.7.1. I’m currently working with upstream to understand some remaining issues on ppc64le, https://github.com/biojppm/rapidyaml/issues/464. It also looks like jsonnet doesn’t build with rapidyaml 0.7.1 (upstream still bundles 0.5.0), and I need to figure out if this is a significant incompatibility or just something trivial like a missing #include. Besides that… This will need c4project, c4core, c4fs, and c4log, all of which I also maintain; and c4core needs fast_float, which I was able to branch and build a couple of days ago and will soon reach EPEL10 stable, https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-646500830f. The versions of the c4* libraries that I branch needs to match rapidyaml. Let me know if you have any specific thoughts or concerns.
This also needs tomcli, bug 2306001. I could replace the tomcli invocation with a patch file, but we should have tomcli in EPEL10 soon, so there’s no need.
With a proposed patch from upstream and with https://src.fedoraproject.org/rpms/jsonnet/pull-request/3, I now have a clean impact check for updating rapidyaml to 0.7.1 in F41 and F42: https://copr.fedorainfracloud.org/coprs/music/rapidyaml/packages/ I’m waiting to see if upstream wants to make a new release with the patch, and then I can announce the update on the devel list with one week’s notice. That clears the way for EPEL10 as soon as tomcli is ready, https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-fa90bc004f.
I just announced the updates in Rawhide and F41. Unless this is particularly urgent to you, I’ll ship the initial EPEL10 packages at the same time.
I’m planning to build an initial package for EPEL10 without the Python extension, then add it back in once the dependencies for python-cmake-build-extension are ready.
FEDORA-EPEL-2024-b4aae7b8ea (c4core-0.2.2-2.el10_0, c4fs-0.0.1^20240622git59cfbae-2.el10_0, and 3 more) has been submitted as an update to Fedora EPEL 10.0. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-b4aae7b8ea
FEDORA-EPEL-2024-b4aae7b8ea (c4core-0.2.2-2.el10_0, c4fs-0.0.1^20240622git59cfbae-2.el10_0, and 3 more) has been pushed to the Fedora EPEL 10.0 stable repository. If problem still persists, please make note of it in this bug report.
I tried a scratch build of jsonnet in the side tag with rapidyaml, just to see if everything looked OK: DEBUG util.py:461: No matching package to install: 'json-devel' DEBUG util.py:461: No matching package to install: 'json-static' So you’ll need to file an EPEL10 branch request for https://src.fedoraproject.org/rpms/json as well.