| 1 |
Replied to the list. |
| 2 |
|
| 3 |
On Thu, 2 Sep 2021 15:50:37 -0400, Alan Grimes wrote: |
| 4 |
|
| 5 |
> Neil Bothwick wrote: |
| 6 |
> |
| 7 |
> If you wish to manually migrate now, there are a series |
| 8 |
> of steps described on the wiki (see below), but the outline is: |
| 9 |
> * unforce the crypt USE flag of sys-libs/glibc and disable it |
| 10 |
> * unmask the system and split-usr (if applicable) USE flag of |
| 11 |
> sys-libs/libxcrypt and enable it |
| 12 |
> * unmask ~virtual/libcrypt-2 |
| 13 |
> |
| 14 |
> ### |
| 15 |
> |
| 16 |
> Glibc simply DOES NOT HAVE a "crypt" useflag... so FALSE!!!! |
| 17 |
|
| 18 |
Yes it does, but only on the testing version. If you are running stable, |
| 19 |
you won't have it. But if you are running stable, why are you trying to |
| 20 |
emerge libxcrypt-4.4.25? |
| 21 |
|
| 22 |
It appears that your problem may be caused by trying to mix stable and |
| 23 |
testing packages with inter-dependencies. |
| 24 |
|
| 25 |
|
| 26 |
-- |
| 27 |
Neil Bothwick |
| 28 |
|
| 29 |
All generalizations are false, including this one. |
Archives