On Sun, 17 Apr 2022 11:41:23 +0000, 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 can't decode:
>
> Calculating dependencies ... . ..... done!
> [ebuild N ~] sys-apps/systemd-utils-250.4::gentoo USE="boot
> (split-usr) sysusers tmpfiles udev (-selinux) -test" ABI_X86="(64) -32
> (-x32)" 10,872 KiB [ebuild U ~] sys-boot/systemd-boot-250::gentoo
> [249.9::gentoo] 0 KiB [blocks b ] <sys-boot/systemd-boot-250
> ("<sys-boot/systemd-boot-250" is soft blocking
> sys-apps/systemd-utils-250.4) [blocks B ]
> <sys-apps/systemd-tmpfiles-250 ("<sys-apps/systemd- tmpfiles-250" is
> soft blocking sys-apps/systemd-utils-250.4) [blocks B ]
> <sys-fs/udev-250 ("<sys-fs/udev-250" is soft blocking sys-
> apps/systemd-utils-250.4)
>
> Total: 2 packages (1 upgrade, 1 new), Size of downloads: 10,872 KiB
> Conflict: 3 blocks (2 unsatisfied)
>
> * Error: The above package list contains packages which cannot be
> * installed at the same time on the same system.
>
> (sys-apps/systemd-tmpfiles-249.9-2:0/0::gentoo, installed) pulled in
> by sys-apps/systemd-tmpfiles required by
> (virtual/tmpfiles-0-r1-1:0/0::gentoo, installed) USE="" ABI_X86="(64)"
>
> (sys-apps/systemd-utils-250.4:0/0::gentoo, ebuild scheduled for
> merge) pulled in by
> sys-apps/systemd-utils[udev] required by (sys-boot/systemd-
> boot-250:0/0::gentoo, ebuild scheduled for merge) USE="" ABI_X86="(64)"
>
> (sys-fs/udev-249.6-r2-3:0/0::gentoo, installed) pulled in by
> >=sys-fs/
> udev-232:0/0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_s390_32(-)?,abi_s390_64(-)?]
>
> (>=sys-fs/udev-232:0/0[abi_x86_64(-)]) required by
> (virtual/libudev-232- r5-2:0/1::gentoo, installed) USE="-systemd"
> ABI_X86="(64) -32 (-x32)"
> >=sys-fs/udev-217 required by (virtual/udev-217-r3-1:0/0::gentoo,
> installed) USE="" ABI_X86="(64)"
>
> This is an amd64 openrc system.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? > On another system, ~amd64 openrc, I was > told to set USE=boot on systemd-utils, so I did that and now when I > boot I have no mouse or keyboard. > > Is this the end of the road for systemd-boot on openrc? I think that USE flag just causes the systemd-boot part of systemd-utils to be built. systemd-boot itself is just a virtual now. It doesn't sound like that would cause this problem, did you emerge anything X related at the same time? -- Neil Bothwick without C people would code in Basi, Pasal and Obol
pgpalhNg49Ji2.pgp
Description: OpenPGP digital signature
