From: Neil Bothwick <neil@digimed.co.uk>
To: Alan Grimes <alonzotg@verizon.net>, gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] SNAFU
Date: Thu, 2 Sep 2021 21:12:51 +0100 [thread overview]
Message-ID: <20210902211251.76bdfe46@digimed.co.uk> (raw)
In-Reply-To: <5435f4a8-1b44-c668-f539-36c287e0ed09@verizon.net>
[-- Attachment #1: Type: text/plain, Size: 882 bytes --]
Replied to the list.
On Thu, 2 Sep 2021 15:50:37 -0400, Alan Grimes wrote:
> Neil Bothwick wrote:
>
> If you wish to manually migrate now, there are a series
> 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
>
> ###
>
> Glibc simply DOES NOT HAVE a "crypt" useflag... so FALSE!!!!
Yes it does, but only on the testing version. If you are running stable,
you won't have it. But if you are running stable, why are you trying to
emerge libxcrypt-4.4.25?
It appears that your problem may be caused by trying to mix stable and
testing packages with inter-dependencies.
--
Neil Bothwick
All generalizations are false, including this one.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-09-02 20:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1b60ceef-6ec6-afeb-c519-d21f3fc42cc0.ref@verizon.net>
2021-09-02 14:35 ` [gentoo-user] SNAFU Alan Grimes
2021-09-02 15:38 ` Neil Bothwick
[not found] ` <5435f4a8-1b44-c668-f539-36c287e0ed09@verizon.net>
2021-09-02 20:12 ` Neil Bothwick [this message]
2021-09-02 21:49 ` David Haller
2021-09-02 21:58 ` David Haller
2021-09-02 22:11 ` Neil Bothwick
2021-09-02 22:54 ` antlists
2021-09-03 8:44 ` [gentoo-user] Richard Blackburn
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=20210902211251.76bdfe46@digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=alonzotg@verizon.net \
--cc=gentoo-user@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