On Sun, 3 Apr 2022 19:07:30 +0200, Arve Barsnes wrote:
> > > This file is for setting or unsetting USE flags on a package.
> > > To "mask the system USE flag" on libxcrypt you would put this in
> > > /etc/portage/package.use.mask:
> > > sys-libs/libxcrypt system
> >
> > Shouldn't that be
On Sun, 3 Apr 2022 at 15:34, Neil Bothwick wrote:
> On Sun, 3 Apr 2022 15:12:36 +0200, Arve Barsnes wrote:
>
> > This file is for setting or unsetting USE flags on a package.
> > To "mask the system USE flag" on libxcrypt you would put this in
> > /etc/portage/package.use.mask:
> >
On Sun, 3 Apr 2022 15:12:36 +0200, Arve Barsnes wrote:
> This file is for setting or unsetting USE flags on a package.
> To "mask the system USE flag" on libxcrypt you would put this in
> /etc/portage/package.use.mask:
> sys-libs/libxcrypt system
Shouldn't that be
On Sun, 3 Apr 2022 at 11:54, n952162 wrote:
> 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.
This file is for adding or removing keywords from packages (like amd64 or
~amd64).
To "unmask and enable
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
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
6 matches
Mail list logo
