Replaced by FEDORA-2025-a6ff0a5c7e.
This update replaces FEDORA-2025-f7735f9f4d and remedies its defect, as well as fixing an additional FTI bug in pgadmin4.
This update has been unpushed.
conflicts with pgadmin4-9.3.1.fc42.x86_64
@dburke Thanks for catching this! I opened https://src.fedoraproject.org/rpms/pgadmin4/pull-request/12 to try to resolve it.
Works to build rust-onefetch in EPEL9, both before and after patching Cargo.toml to allow rstest 0.26 (a change not yet pushed to dist-git).
This requires FEDORA-EPEL-2025-c2e569b591, which is not quite in stable repos yet, but has already been submitted for stable.
Works to build rust-async_http_range_reader, before and after https://src.fedoraproject.org/rpms/rust-async_http_range_reader/c/b99116ec29daff0120963d016fad751b75bedd8d?branch=rawhide updated from rstest 0.23 to rstest 0.26.
Works to build rust-async_http_range_reader, before and after https://src.fedoraproject.org/rpms/rust-async_http_range_reader/c/b99116ec29daff0120963d016fad751b75bedd8d?branch=rawhide updated from rstest 0.23 to rstest 0.26.
Works to build rust-async_http_range_reader, before and after https://src.fedoraproject.org/rpms/rust-async_http_range_reader/c/b99116ec29daff0120963d016fad751b75bedd8d?branch=rawhide updated from rstest 0.23 to rstest 0.26.
I missed including a python-tox-uv update that was required for compatibility with uv 0.8.x, so I’ve modified this update
Thanks for all the testing. I missed backporting a patch for uv 0.8 compatibility in python-tox-uv, so I’ve modified this update, and karma has been reset.
Thanks for all the testing. I missed including a python-tox-uv update that was required for compatibility with uv 0.8.x, so I’ve modified this update at the last second. Karma has been reset.
In a local mock build, combined with https://src.fedoraproject.org/rpms/rust-console/pull-request/2 and https://src.fedoraproject.org/rpms/rust-indicatif/pull-request/2 and with an initial package for https://src.fedoraproject.org/rpms/rust-unit-prefix, this worked to build uv 0.8.1 from https://src.fedoraproject.org/rpms/uv/pull-request/67, which uses toml 0.9.
In a local mock build, combined with https://src.fedoraproject.org/rpms/rust-console/pull-request/2 and https://src.fedoraproject.org/rpms/rust-indicatif/pull-request/2 and with an initial package for https://src.fedoraproject.org/rpms/rust-unit-prefix, this worked to build uv 0.8.1 from https://src.fedoraproject.org/rpms/uv/pull-request/67, which uses toml 0.9.
In a local mock build, combined with https://src.fedoraproject.org/rpms/rust-console/pull-request/2 and https://src.fedoraproject.org/rpms/rust-indicatif/pull-request/2 and with an initial package for https://src.fedoraproject.org/rpms/rust-unit-prefix, this worked to build uv 0.8.1 from https://src.fedoraproject.org/rpms/uv/pull-request/67, which uses toml 0.9.
Mock builds of rust-cargo, rust-nu-command, and atuin with --enablerepo=epel-testing -- --postinstall succeeded; together, these cover all of the updated crates in their dependency trees.
A mock build of rust-cargo with --enablerepo=epel-testing -- --postinstall succeeded using these crates in an alma+epel-10-x86_64 chroot.
Mock builds of ruff and rust-cargo with --enablerepo=epel-testing -- --postinstall succeeded; together, these cover all of the updated crates in their dependency trees, except mock_instant/mock_instant0.3, which appear to be leaves in EPEL10.1.
Mock builds of ruff, rust-cargo, and ruff-nu-command with --enablerepo=updates-testing -- --postinstall succeeded; together, these cover all of the updated crates in their dependency trees.
This release contained an error and was yanked. I will update to 0.11.4 instead. See: https://diff.rs/zerovec/0.11.3/0.11.4/src%2Fzerovec%2Fmod.rs