This seems correct. Ideally, it would have been combined into a multi-build update with FEDORA-2026-901d4ceb62, but we can expect they will land together, and there’s no great harm if they don’t.
This seems correct.
This seems correct.
This fixes the regressions I have seen, and I haven’t spotted any new ones. Thanks!
This fixes the regressions I have seen, and I haven’t spotted any new ones. Thanks!
This update has been unpushed.
This should be obsoleted by FEDORA-2026-65523b5226.
Replaced by FEDORA-2026-8b3a9f21ad.
This update has been unpushed.
Unpushing because I want to edit this one more time, but the side tag has been deleted. I will tag all the builds into a new side tag and create a new update to replace this one.
Installability issues reported in automated tests appear to be only due to changes in feature metapackages; Rust libraries need not provide upgrade paths for these.
The equivalent upgrade in Rawhide worked to build rust-jiter/python-jiter 0.14, which require PyO3 0.28, in local mock testing.
Installability issues reported in automated tests appear to be only due to changes in feature metapackages; Rust libraries need not provide upgrade paths for these.
The equivalent upgrade in Rawhide worked to build rust-jiter/python-jiter 0.14, which require PyO3 0.28, in local mock testing.
This update has been unpushed.
Let’s just let FEDORA-2026-ab227e7dfe land in a week instead.
This update has been unpushed.
Merging this into FEDORA-2026-f4d8c6e22d.
unresolved deps (1):
Good catch, thanks. I missed branching the new package https://src.fedoraproject.org/rpms/rust-reqsign-volcengine-tos/. I’ll fix that.
Unpushing this in favor of FEDORA-2026-f4d8c6e22d, which contains an even newer update.
This update has been unpushed.
This seems correct. Ideally, it would have been combined into a multi-build update with FEDORA-2026-3e9679e3c1, but we can expect they will land together, and there’s no great harm if they don’t.