Comments
music
It seems like https://bugzilla.redhat.com/show_bug.cgi?id=2327553 should be associated with this update, too.
The upstream release notes for the packaged version claim it fixes the mentioned CVE’s, and the command-line tool passed a quick “smoke test” in a mock chroot.
The upstream release notes for the packaged version claim it fixes the mentioned CVE’s, and the command-line tool passed a quick “smoke test” in a mock chroot.
The upstream release notes for the packaged version claim it fixes the mentioned CVE’s, and the command-line tool passed a quick “smoke test” in a mock chroot.
The upstream release notes for the packaged version claim it fixes the mentioned CVE’s, and the command-line tool passed a quick “smoke test” in a mock chroot.
This update has been unpushed.
Unpushing this update in order to tag the build into a Pydantic 3.10 update similar to FEDORA-2024-064d418de8.
All the nu crate library packages appear to be installable (mock -r fedora-41-x86_64 --enablerepo=updates-testing -i 'rust-nu*' succeeds).
The nu shell appears to work.
The uv-0.4.30-2.fc40 package in this update was built with rust-jiff-0.1.14-1.fc40, from FEDORA-2024-a8a682f03e, and rust-goblin-0.9.2-1.fc40, from FEDORA-2024-d995ad4e76.
The uv-0.4.30-2.fc41 package in this update was built with rust-jiff-0.1.14-1.fc41, from FEDORA-2024-cad1407d4e, and rust-goblin-0.9.2-1.fc41, from FEDORA-2024-dc111cf987.
Replaced by FEDORA-2024-5256f2495c.
This update has been unpushed.
Replaced by FEDORA-2024-87b18b6707.
This update has been unpushed.
We can’t add a build to a non-side-tag update, but we can unpush the update, tag the build into a side tag, and re-use it for a new update based on the side tag, without having to rebuild python-nibabel again.
I’m still doing local rebuilds to verify that everything else is OK. The things that depend on this have some seriously heavy tests.
It turns out that this breaks python-nifti-mrs. That’s fixed in python-nifti-mrs-1.3.1, so one possibility is that this update could be unpushed and the build could be tagged into a side tag with python-nifti-mrs-1.3.1, and that side tag could be used to create a new update.
However, I wonder if anything else is affected. I’ll spend a little time doing test builds and follow up.
It turns out that this breaks python-nifti-mrs. That’s fixed in python-nifti-mrs-1.3.1, so one possibility is that this update could be unpushed and the build could be tagged into a side tag with python-nifti-mrs-1.3.1, and that side tag could be used to create a new update.
However, I wonder if anything else is affected. I’ll spend a little time doing test builds and follow up.
While rpminspect claims “New package python3-tox-uv-1.15.0-1.fc41.noarch.rpm is empty (no payloads),” manual inspection of python3-tox-uv-1.15.0-1.fc41.noarch.rpm indicates that this diagnostic is (weirdly) spurious.
The update looks reasonable, installs correctly, and appears to resolve https://bugzilla.redhat.com/show_bug.cgi?id=2319202.
The upstream release notes for the packaged version claim it fixes the mentioned CVE’s, and the command-line tool passed a quick “smoke test” in a mock chroot.