Fixes on the posttrans code, where now 'spec: move all pending EFI logic from common to EFI package'
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-020161eb80Please log in to add feedback.
This update has been submitted for testing by lsandova.
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 contains a scriptlet that fails when installing the package in a chroot (or similar) as part of building an image, e.g. from Kiwi:
remember, package scriptlets are required by policy never to exit non-zero: "All scriptlets MUST exit with the zero exit status."
This update has been pushed to testing.
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.
0 due scriptlet error
As in rawhide, this is the f44 https://src.fedoraproject.org/rpms/grub2/pull-request/234 proposal
wainting for the new build
Works great! LGTM! =)
Works.
Works
This fails as part of a install in a podman container
lsandova edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by lsandova.
This update's test gating status has been changed to 'waiting'.
@luap99 yes and in theory the new build (2.12-63) fixes it .
This update's test gating status has been changed to 'passed'.
This update has been pushed to testing.
seems to pass now, though the error is still shows in the output but I guess that does not matter much
@luap99 which error? it should not print any error (in theory)
The same I posted above, the only difference it exits 0 so rpm works
@luap99 which environment are you installing/upgrading grub? I should be able to replicate and see if something can be done and avoid that error even on zero-exit status.
It is a podman container, see my original comment
Yes we do not need grub in a container so this does not matter much to me, I just noticed as some script put it into a container build and suddenly failed.
@luap99 oh you are right, I did not look carefully your original comment. Yeah, grub is not needed on a container env.
no issues on my laptop
This update can be pushed to stable now if the maintainer wishes
Working fine for me.