From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] data/gentoo-news:master commit in: 2021-06-30-libxcrypt-migration/
Date: Thu, 1 Jul 2021 06:51:18 +0000 (UTC) [thread overview]
Message-ID: <1625122253.48149ddf9fcd870bb6ac09a5cd8ded10718f9024.sam@gentoo> (raw)
commit: 48149ddf9fcd870bb6ac09a5cd8ded10718f9024
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Jul 1 06:50:53 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Jul 1 06:50:53 2021 +0000
URL: https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=48149ddf
2021-06-30-libxcrypt-migration: change unmask instruction to use ~ operator
We changed the mask to use ~ for future flexibility.
Signed-off-by: Sam James <sam <AT> gentoo.org>
2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.en.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.en.txt b/2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.en.txt
index 87cfd67..16b5596 100644
--- a/2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.en.txt
+++ b/2021-06-30-libxcrypt-migration/2021-06-30-libxcrypt-migration.en.txt
@@ -40,7 +40,7 @@ of steps described on the wiki (see below), but the outline is:
* unforce the crypt USE flag of sys-libs/glibc and disable it
* unmask the system and split-usr (if applicable) USE flag of sys-libs/libxcrypt
and enable it
-* unmask >=virtual/libcrypt-2
+* unmask ~virtual/libcrypt-2
For more information, please see:
* https://wiki.gentoo.org/wiki/Project:Toolchain/libcrypt_implementation
next reply other threads:[~2021-07-01 6:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 6:51 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-22 23:41 [gentoo-commits] data/gentoo-news:master commit in: 2021-06-30-libxcrypt-migration/ Sam James
2021-07-22 23:41 Sam James
2021-07-05 23:46 Sam James
2021-06-30 21:18 Sam James
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=1625122253.48149ddf9fcd870bb6ac09a5cd8ded10718f9024.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