On 4/3/22 10:27, Alexander Puchmayr wrote:
Am Sonntag, 3. April 2022, 10:23:25 CEST schrieb n952162:
My emerge fails due to a collision with xorg-server and glibc. How can I
find out where the problem is, actually?
Output attached.
Did you have a look at
https://www.gentoo.org/support/news-items/2021-10-18-libxcrypt-migration-stable.html
Alex
Thank you, yes, I forgot to check that.
I put in --ignore-built-slot-operator-deps=y
The conflict is gone but now I have a circular dependency. Recommended
steps:
* unmask and enable the crypt USE flag of sys-libs/glibc
* mask the system USE flag of sys-libs/libxcrypt
* mask >=virtual/libcrypt-2
* unmask virtual/libcrypt:0/1
I'm not really clear on masking.
1. My /etc/portage/package.accept_keywords has no mention of glibc, so
I think there's nothing to unmask.
2. "mask the system USE flag"? USE flags go into
/etc/portage/package.use, correct? Is that "mask" an inexact
expression? Anyway, a "system" USE flag?
$ equery uses sys-libs/libxcrypt
python-exec: Invalid impl in /etc/python-exec/python-exec.conf:
python3.7
[ Legend : U - final flag setting for installation]
[ : I - package is installed with flag ]
[ Colors : set, unset ]
* Found these USE flags for sys-libs/libxcrypt-4.4.27:
U I
+ - abi_x86_32 : 32-bit (x86) libraries
- - static-libs : Build static versions of dynamic libraries as well
- - test : Enable dependencies and/or preparations
necessary to run tests (usually controlled by FEATURES=test but can
be toggled independently)
3.
"mask >=virtual/libcrypt-2"
Like, ">=virtual/libcrypt-2" into /etc/portage/package.accept_keywords, just
like that?
4.
But virtual/libcrypt:0/1 is not masked (to my knowledge).
