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