docs: cleanup some incorrect info
This commit is contained in:
@@ -26,7 +26,7 @@ If you want to add custom configuration files, you can just add them in the `etc
|
||||
## Installation
|
||||
|
||||
> **Warning**
|
||||
> This is an experimental feature and should not be used in production, try it in a VM for a while! If you are rebasing and not doing a clean install do a `touch ~/.config/ublue/firstboot-done` to keep your flatpak configuration untouched BEFORE you rebase, otherwise we're going to mangle it (for science).
|
||||
> This is an experimental feature and should not be used in production, try it in a VM for a while!
|
||||
|
||||
To rebase an existing Silverblue/Kinoite installation to the latest build:
|
||||
|
||||
@@ -37,10 +37,10 @@ sudo rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/startingpoint
|
||||
This repository builds date tags as well, so if you want to rebase to a particular day's build:
|
||||
|
||||
```
|
||||
sudo rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/startingpoint:20221217
|
||||
sudo rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/startingpoint:20230403
|
||||
```
|
||||
|
||||
The `latest` tag will automatically point to the latest build. Note that when a new version of Fedora is released that the `latest` tag will get updated to that latest release automatically.
|
||||
The `latest` tag will automatically point to the latest build. That build will still always use the Fedora version specified in `release.yml`, so you won't get accidentally updated to the next major version.
|
||||
|
||||
## Just
|
||||
|
||||
|
||||
Reference in New Issue
Block a user