| 1 |
On Sun, 10 Apr 2022 at 04:35, Walter Dnes <waltdnes@××××××××.org> wrote: |
| 2 |
|
| 3 |
> To quote Rowan and Martin "Later... that very same evening" (7 hours |
| 4 |
> and 265 packages) it finished. Now to tackle libcrypt. How do I handle |
| 5 |
> the following? As near as I can tell from the news item, glibc's |
| 6 |
> internal libcrypt is being replaced by an external libxcrypt but the |
| 7 |
> details are vague.. |
| 8 |
> |
| 9 |
|
| 10 |
|
| 11 |
Hard to tell from your output what the status of any conflicts are on your |
| 12 |
system. As the message correctly indicates, it cannot upgrade glibc because |
| 13 |
virtual/libcrypt-1 requires the older version. |
| 14 |
|
| 15 |
What would portage complain about before you excluded it? What is the |
| 16 |
output from: |
| 17 |
emerge -1va =virtual/libcrypt-2 |
| 18 |
|
| 19 |
As mentioned in the news item, most upgrades should have just happened on |
| 20 |
its own without user interference, so it might also be as simple as |
| 21 |
re-running the @world command with --backtrack=1000 |
| 22 |
|
| 23 |
Regards, |
| 24 |
Arve |
Archives