-
Notifications
You must be signed in to change notification settings - Fork 28
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
README.md: Update status to reflect current reality #439
Conversation
Should we mention that bootupd doesn't yet perform updates automatically? Folks may assume otherwise if we don't say anything. |
The FCOS side here is already covered by https://docs.fedoraproject.org/en-US/fedora-coreos/bootloader-updates/ right? |
Sure. But the upstream project status should presumably reflect the upstream portion of this. Disabled auto-merge to avoid this comment creating a race condition. |
I don't quite understand your comment, please feel free to provide suggested replacement text? |
Maybe something like:
? On that topic, ISTM like bootupd could ship the systemd unit in https://docs.fedoraproject.org/en-US/fedora-coreos/bootloader-updates/ itself as e.g. |
I agree that it'd be good to ship the unit upstream, even if disabled by default. How about text like this:
|
Came up re coreos/fedora-coreos-tracker#1441 Co-authored-by: Benjamin Gilbert <[email protected]>
ac2f5a9
to
f0d628f
Compare
LGTM, updated to that text. |
Nightly Rust failure is rust-lang/rust#109199 (comment) And this is a network flake |
@cgwalters: Overrode contexts on behalf of cgwalters: continuous-integration/jenkins/pr-merge In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Came up re coreos/fedora-coreos-tracker#1441