From ba12a9cf88ed079d72d9eedb2aaeeeccbd0b3730 Mon Sep 17 00:00:00 2001 From: ER Date: Mon, 3 Apr 2023 17:32:01 +0300 Subject: [PATCH] docs: cleanup some incorrect info --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 9783f6d..58cf8b8 100644 --- a/README.md +++ b/README.md @@ -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