On Sunday, 17 April 2022 14:54:50 -00 Rich Freeman wrote:
> On Sun, Apr 17, 2022 at 9:03 AM Peter Humphrey
wrote:
> > On Sunday, 17 April 2022 12:13:06 -00 Neil Bothwick wrote:
> >
> > --->8
> >
> > > It looks like this is cause my using mixed keywords, amd64 for udev and
> > > ~amd64 for
On Sun, Apr 17, 2022 at 9:03 AM Peter Humphrey wrote:
>
> On Sunday, 17 April 2022 12:13:06 -00 Neil Bothwick wrote:
>
> --->8
> > It looks like this is cause my using mixed keywords, amd64 for udev and
> > ~amd64 for systemd-boot/utils. Does keywording udev-250 resolve the
> > blocks?
>
> Yes,
On Sunday, 17 April 2022 12:13:06 -00 Neil Bothwick wrote:
--->8
> It looks like this is cause my using mixed keywords, amd64 for udev and
> ~amd64 for systemd-boot/utils. Does keywording udev-250 resolve the
> blocks?
Yes, after keywording several others, thus:
~sys-apps/systemd-tmpfiles-249.9
On Sun, 17 Apr 2022 11:41:23 +, Peter Humphrey wrote:
> I've been using bootctl from sys-boot/systemd-boot for several years,
> with some success, but I'm stuck after today's --sync.
>
> First I was told I had to keyword sys-apps/systemd-utils, so I did
> that, but now I get this, which I
Hello list,
I've been using bootctl from sys-boot/systemd-boot for several years, with
some success, but I'm stuck after today's --sync.
First I was told I had to keyword sys-apps/systemd-utils, so I did that, but
now I get this, which I can't decode:
Calculating dependencies ... . .
5 matches
Mail list logo