See https://ocaml.org/releases/5.2.1 for changes in ocaml 5.2.1. All other packages were rebuilt for OCaml 5.2.1. VCS fields were added for packages lacking them. Other changes are as follows:
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2025-3b699f421bPlease login to add feedback.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
This update has been submitted for testing by bodhi.
So the test failure here is caused by brltty. The previous stable brltty is brltty-6.6-19.fc41. In that build, the brltty binary package does not depend on libespeak or libespeak-ng. In the -21.fc41 build in this update, it does. It also added several other deps:
This is likely caused by https://src.fedoraproject.org/rpms/brltty/c/d38d4c43521ffdf921f3696e6ce10a2cac048543?branch=f41 , so CCing @yselkowitz .
The reason this makes the test fail is that this causes espeak to be pulled into the installer environment. espeak requires libpulse.so.0, which is stripped from the installer environment to save space (the installer environment being presumed not to need sound). CCing @bcl for that angle.
On the face of it, it seems like the espeak-dependent bits of brltty are supposed to be in brltty-espeak , and the espeak-ng-dependent bits are supposed to be in brltty-espeak-ng , and that's what needs fixing. But if anyone thinks that's not what should change, speak up. :D
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
Perhaps we should revert that commit for F41, and then fix whatever needs fixing in Rawhide. That would maintain parity with previous F41 builds.
The original syntax was actually wrong too; see https://src.fedoraproject.org/rpms/brltty/pull-request/14 and https://src.fedoraproject.org/rpms/brltty/pull-request/15.
This update has been pushed to testing.
brltty-6.6-22.fc41 is now waiting in the side tag with the fix.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'failed'.
Thank you. I reran the tests, but they failed again. As usual, I find the test reports to be absolutely incomprehensible. If somebody who knows how to read this stuff could take a look, I would appreciate some help figuring out what is still broken.
You need to regenerate the update. It doesn't happen automatically. The update still contains brltty-6.6-21.fc41 , as you can see over on the right, so the tests failed again for exactly the same reason. If you refresh the update from the side tag (you should have a button to do that), it should pick up the newer brltty and the tests will rerun automatically (and hopefully pass).
yselkowitz edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by yselkowitz.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
Works great! LGTM! =)
CI is passing now.
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
Thank you for the lesson on how to use bodhi, @adamwill, and thank you @yselkowitz for your work.
This update has been submitted for stable by jjames.
This update has been pushed to stable.