From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] data/gentoo-news:master commit in: 2022-12-01-systemd-usrmerge/
Date: Mon, 6 Feb 2023 15:50:47 +0000 (UTC) [thread overview]
Message-ID: <1675698633.af0db5eca18febcc06540d230c960a5e6ed127a3.sam@gentoo> (raw)
commit: af0db5eca18febcc06540d230c960a5e6ed127a3
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Feb 6 15:50:33 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Feb 6 15:50:33 2023 +0000
URL: https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=af0db5ec
2022-12-01-systemd-usrmerge: suggest system be up to date first
This makes life a lot easier with debugging potential issues.
Signed-off-by: Sam James <sam <AT> gentoo.org>
2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt b/2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt
index be1870c..c851d3c 100644
--- a/2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt
+++ b/2022-12-01-systemd-usrmerge/2022-12-01-systemd-usrmerge.en.txt
@@ -18,7 +18,8 @@ script is available to perform the actual migration.
To migrate a system to merged-usr, follow this procedure:
-1. Ensure your system backups are up to date.
+1. Ensure your system backups are up to date. Please also update
+ your system fully and depclean before proceeding.
2. Install sys-apps/merge-usr.
next reply other threads:[~2023-02-06 15:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 15:50 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-08 16:55 [gentoo-commits] data/gentoo-news:master commit in: 2022-12-01-systemd-usrmerge/ Mike Gilbert
2022-12-05 8:42 Sam James
2022-12-01 20:29 Mike Gilbert
2022-12-01 18:09 Mike Gilbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1675698633.af0db5eca18febcc06540d230c960a5e6ed127a3.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox