-
Notifications
You must be signed in to change notification settings - Fork 198
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
upgrade --check supported or not? #267
Comments
Sorry, I was unable to type. Second type was a typo. |
FWIW, @cgwalters fixed that ugly Not sure if that would cause the command to return properly like if you just typed
|
cgwalters
added a commit
to cgwalters/rpm-ostree
that referenced
this issue
Apr 27, 2016
If one does `rpm-ostree foo --bar`, one would expect to see `Unknown subcommand foo`, not `Unknown option --bar`. Closes: coreos#267
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
[root@conex puiterwijk]# rpm-ostree upgrade --help
Usage:
rpm-ostree upgrade [OPTION...] - Perform a system upgrade
Help Options:
-h, --help Show help options
Application Options:
--os=OSNAME Operate on provided OSNAME
-r, --reboot Initiate a reboot after an upgrade is prepared
--allow-downgrade Permit deployment of chronologically older trees
--preview Just preview package differences
--check Just check if an upgrade is available
--upgrade-unchanged-exit-77 If no upgrade is available, exit 77
--sysroot=SYSROOT Use system root SYSROOT (default: /)
--peer Force a peer-to-peer connection instead of using the system message bus
--version Print version information and exit
[root@conex puiterwijk]# rpm-ostree uprade --check
Usage:
rpm-ostree [OPTION...] COMMAND
Builtin Commands:
compose
db
deploy
rebase
rollback
status
upgrade
Help Options:
-h, --help Show help options
Application Options:
--version Print version information and exit
error: Unknown option --check
** (rpm-ostree:32710): WARNING **: (src/app/main.c:296):main: runtime check failed: (exit_status != EXIT_SUCCESS)
The text was updated successfully, but these errors were encountered: