Thank you! I’ve waived the CoreOS test with the following message:
OK based on discussion in the CoreOS Matrix channel. The glibc version required by the rust-afterburn rebuild is current in Rawhide, but CoreOS lags four days at the moment. Tests passed in https://jenkins-coreos-ci.apps.ocp.fedoraproject.org/job/test-override/1441 with a glibc override, so CoreOS contributors felt waiving was appropriate.
It looks like the coreos test fails because rust-afterburn was built with glibc-2.44.9000-6.fc46, Requires glibc >= 2.44.9000-6, but that version was not available in the test environment (yet), and so the package failed to install?
Hmm, I wonder what can be done about that.
Gating tests failed due to infrastructure flakiness. I need to re-trigger the tests, but I am unable to do so (even in the Bodhi CLI) until the update is in testing status.
This update has been unpushed.
This update has been unpushed.
A scratch-build of rust-askalono-cli in the side tag (after a wait-repo) succeeded, https://koji.fedoraproject.org/koji/taskinfo?taskID=151985689.
Thanks for the follow-up!
Thanks for the follow-up!
Works for a test build of https://src.fedoraproject.org/rpms/rust-zip/pull-request/13 with zstd 0.15 and a test-rebuild of rust-askalono-cli with zstd 0.14.
Works for a test build of https://src.fedoraproject.org/rpms/rust-zip/pull-request/13 with zstd 0.15 and a test-rebuild of rust-askalono-cli with zstd 0.14.
Works for a test build of https://src.fedoraproject.org/rpms/rust-zip/pull-request/13 with zstd 0.15 and a test-rebuild of rust-askalono-cli with zstd 0.14.
Works for a test build of https://src.fedoraproject.org/rpms/rust-zip/pull-request/13 with zstd 0.15 and a test-rebuild of rust-askalono-cli with zstd 0.14.
Works for a test build of https://src.fedoraproject.org/rpms/rust-zip/pull-request/13 with zstd 0.15 and a test-rebuild of rust-askalono-cli with zstd 0.14.
The same update works well in Rawhide, F45, F44, and EPEL10. I’m going to go out on a limb and say that the F43 version will be fine, too.
Nothing in EPEL10 is quite ready for PyO3 0.30, but this works to test-build python-watchfiles with the PyO3 0.29 compat package.
This works to build python-jiter 0.18.0 with PyO3 0.30; it also works to test-rebuild python-crate-ingredients with PyO3 0.29.
This works to build python-jiter 0.18.0 with PyO3 0.30; it also works to rebuild python-pydantic-core with PyO3 0.29.
Unable to install hatch-1.15.1-7.el10_2 due to missing dependency: python3.12dist(hatchling) >= 1.26.3. No matching provider found in enabled repositories, including epel-testing.
The python3-hatchling package is in RHEL 10, in the CRB repo. Do you have that enabled? In general, EPEL packages may depend on CRB packages.
This update has been unpushed.
There are other packages that would need to be rebuilt:
fedrq wrsrc -s simdjson -b f45 -F nameturns upada-urlandgroonga, andfedrq wr 'libsimdjson.so*' -b f45shows that at leastgroongaactually ships something linked against this and would fail to install if not rebuilt.Plus, an ABI-breaking update like this in a stable release (or after Final Freze) is against the Updates Policy, so this needs a FESCo-granted exception.