Since I am using Silverblue, I’ve always typed rpm-ostree update. I also think that’s how all old docs etc. called it.
You cannot image then, how shocked I was when I saw rpm-ostree upgrade!
It’s easy to check that one is an alias of the other and they both seem to do the same.
The big question is: Which is the correct one?
You can e.g. check the autocompletion with tab:
$ rpm-ostree u uninstall upgrade usroverlay
Additionally, the man page only mentions the
upgrade Download the latest version of the current tree, and deploy it, setting it up as the default for the next boot. By design, this has no effect on your running filesystem tree. You must reboot for any changes to take effect.
And also the official docs only mention
upgrade is the “real”/“recommend” command and now I have to change years (is rpm-ostree even that old?) of (by heard) learned typing behaviour…
$ rpm-ostree --version rpm-ostree: Version: '2020.2' Git: f6cdd9765f1c0d1d88210e448756fc22a9a18c57 Features: - compose - rust
That said, I still think most of the community/people in this forum, do use
rpm-ostree update? I am really surprised to see the
upgrade command being used…
But hey, let’s actually ask the community:
What command do you use for refreshing your Fedora Silverblue system?
(or CoreOS too, for that matter…)
- rpm-ostree update
- rpm-ostree upgrade
Despite all that, I would be glad if someone could explain me the history of how that change happened (and when?? I did not notice it…)
I.e.: How could that happen?
(And what’s the reasoning behind that?)