-
Notifications
You must be signed in to change notification settings - Fork 192
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
rpm-ostree status –json and –booted do not work as expected together #2829
Comments
I suppose. Right now, when you use |
Yeah, I guess it depends on how you want to “API”-design your CLI. Another idea would be to have a Otherwise, if it’s the same command, you should expect stupid users like me to just combine the flags and expect them to work. If they don’t work together, show an error, at least. (As you do with |
Unfortunately the implement involves some ugly grubbing through GVariant...really need to port this stuff to Rust. Closes: coreos#2829
Unfortunately the implement involves some ugly grubbing through GVariant...really need to port this stuff to Rust. Closes: coreos#2829
Unfortunately the implement involves some ugly grubbing through GVariant...really need to port this stuff to Rust. Closes: coreos#2829
Unfortunately the implement involves some ugly grubbing through GVariant...really need to port this stuff to Rust. Closes: coreos#2829
Unfortunately the implement involves some ugly grubbing through GVariant...really need to port this stuff to Rust. Closes: coreos#2829
Unfortunately the implement involves some ugly grubbing through GVariant...really need to port this stuff to Rust. Closes: coreos#2829
Host system details Fedora CoreOS 34.20210427.2.1
Provide the output of
rpm-ostree status
:Expected vs actual behavior
rpm-ostree status --booted
works as expected:However, when I add
--json
I get a totally different output, i.e. also the not-booted status:Expected:
Only the booted deployment should be shown/included in the
--json
output.This is unexpected, because the help page does not mention the two options are exclusive/”incompatible”:
And there is also no error as when you e.g. try this:
Steps to reproduce it
see above
Would you like to work on the issue?
rather not, unless it's doc-only
The text was updated successfully, but these errors were encountered: