-
Notifications
You must be signed in to change notification settings - Fork 356
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cherry-pick PR 5297 content from Fedora-39 branch #5324
Conversation
Hello @KKoukiou! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:
Comment last updated at 2024-02-06 15:45:13 UTC |
This needs to be tested with the Web UI |
This PR is stale because it has been open 60 days with no activity. |
What's the testing that it needs? Is it something that's now available? |
we dont have automation for live images, so that needs to be tested manually. |
Oh :( |
Live images are already installed with grub2 and cannot be changed on the fly to systemd-boot (well at least without a lot of extra work). In case the user passed one of the systemd-boot options to anaconda, we should be a bit more graceful than failing to run the updateloader entries script as currently happens. This change, when run on non webUI installs results in a popup notifying the user there is an error in the bootloader configuration and asking if they would like to ignore it. Resolves: rhbz#2234638 Signed-off-by: Jeremy Linton <[email protected]>
The installer is not able to verify requirements of the selected bootloader with other types of payload, like live images and rpmostree installations. Let's allow systemd-boot only for package installations for now and deal with other use cases later. Related: rhbz#2234638
58b686b
to
a10b1fa
Compare
Something wrong with RPM builds here. Closing and reopening for COPR from packit to be recreated. |
No description provided.