-
Notifications
You must be signed in to change notification settings - Fork 23
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
No nvram #617
No nvram #617
Conversation
--removable implies --no-nvram, no need to duplicate it. Signed-off-by: Michal Suchanek <msuchanek@suse.de>
@watologo1 @hramrach I need your help here. Due to bug checker, we add to master workaround for arm at #615 but I worry its logic collide. As now on arm we run with no-nvram --removable and also another grub2-install without it see https://github.com/yast/yast-bootloader/pull/617/files#diff-a2dd9a79782b903e9a1485d4c37037a7R44 So could you evaluate if we should remove this workaround or if logic is still valid? |
Yes, it will conflict. This needs to be rebased. |
Am Dienstag, 22. September 2020, 11:27:51 CEST schrieb Michal Suchánek:
Yes, it will conflict. This needs to be rebased.
Sigh...
I hoped fixing up the minor coding style issue could help...
@michal: Can you rebase this one, please. You know the code much better.
Looks like the Travis checks have been all addressed and calmed down.
I keep thumbs crossed we get this soon...
Thanks everybody,
Thomas
|
well, it does not conflict as git conflict, just result is probably not what we want. I fix all travis issues, so please feel free to create pr against this branch and I will handle rest. |
Updated the original PR. |
@hramrach thanks, I check it and adapt this branch to behave same. |
From code point of view it looks good to me. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@@ -66,6 +66,7 @@ bl_global = | |||
element os_prober { STRING_BOOL }? & | |||
element suse_btrfs { STRING_BOOL }? & | |||
element secure_boot { STRING_BOOL }? & | |||
element update_nvram { STRING_BOOL }? & |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do not forget to update the yast2-schema dependency.
https://github.com/yast/yast-schema/blob/master/package/yast2-schema.spec#L48
✔️ Public Jenkins job #65 successfully finished |
✔️ Internal Jenkins job #32 successfully finished |
replaces #616