| 1 |
On Sun, 17 Apr 2022 11:41:23 +0000, Peter Humphrey wrote: |
| 2 |
|
| 3 |
> I've been using bootctl from sys-boot/systemd-boot for several years, |
| 4 |
> with some success, but I'm stuck after today's --sync. |
| 5 |
> |
| 6 |
> First I was told I had to keyword sys-apps/systemd-utils, so I did |
| 7 |
> that, but now I get this, which I can't decode: |
| 8 |
> |
| 9 |
> Calculating dependencies ... . ..... done! |
| 10 |
> [ebuild N ~] sys-apps/systemd-utils-250.4::gentoo USE="boot |
| 11 |
> (split-usr) sysusers tmpfiles udev (-selinux) -test" ABI_X86="(64) -32 |
| 12 |
> (-x32)" 10,872 KiB [ebuild U ~] sys-boot/systemd-boot-250::gentoo |
| 13 |
> [249.9::gentoo] 0 KiB [blocks b ] <sys-boot/systemd-boot-250 |
| 14 |
> ("<sys-boot/systemd-boot-250" is soft blocking |
| 15 |
> sys-apps/systemd-utils-250.4) [blocks B ] |
| 16 |
> <sys-apps/systemd-tmpfiles-250 ("<sys-apps/systemd- tmpfiles-250" is |
| 17 |
> soft blocking sys-apps/systemd-utils-250.4) [blocks B ] |
| 18 |
> <sys-fs/udev-250 ("<sys-fs/udev-250" is soft blocking sys- |
| 19 |
> apps/systemd-utils-250.4) |
| 20 |
> |
| 21 |
> Total: 2 packages (1 upgrade, 1 new), Size of downloads: 10,872 KiB |
| 22 |
> Conflict: 3 blocks (2 unsatisfied) |
| 23 |
> |
| 24 |
> * Error: The above package list contains packages which cannot be |
| 25 |
> * installed at the same time on the same system. |
| 26 |
> |
| 27 |
> (sys-apps/systemd-tmpfiles-249.9-2:0/0::gentoo, installed) pulled in |
| 28 |
> by sys-apps/systemd-tmpfiles required by |
| 29 |
> (virtual/tmpfiles-0-r1-1:0/0::gentoo, installed) USE="" ABI_X86="(64)" |
| 30 |
> |
| 31 |
> (sys-apps/systemd-utils-250.4:0/0::gentoo, ebuild scheduled for |
| 32 |
> merge) pulled in by |
| 33 |
> sys-apps/systemd-utils[udev] required by (sys-boot/systemd- |
| 34 |
> boot-250:0/0::gentoo, ebuild scheduled for merge) USE="" ABI_X86="(64)" |
| 35 |
> |
| 36 |
> (sys-fs/udev-249.6-r2-3:0/0::gentoo, installed) pulled in by |
| 37 |
> >=sys-fs/ |
| 38 |
> 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(-)?] |
| 39 |
> (>=sys-fs/udev-232:0/0[abi_x86_64(-)]) required by |
| 40 |
> (virtual/libudev-232- r5-2:0/1::gentoo, installed) USE="-systemd" |
| 41 |
> ABI_X86="(64) -32 (-x32)" |
| 42 |
> >=sys-fs/udev-217 required by (virtual/udev-217-r3-1:0/0::gentoo, |
| 43 |
> installed) USE="" ABI_X86="(64)" |
| 44 |
> |
| 45 |
> This is an amd64 openrc system. |
| 46 |
|
| 47 |
It looks like this is cause my using mixed keywords, amd64 for udev and |
| 48 |
~amd64 for systemd-boot/utils. Does keywording udev-250 resolve the |
| 49 |
blocks? |
| 50 |
|
| 51 |
> On another system, ~amd64 openrc, I was |
| 52 |
> told to set USE=boot on systemd-utils, so I did that and now when I |
| 53 |
> boot I have no mouse or keyboard. |
| 54 |
> |
| 55 |
> Is this the end of the road for systemd-boot on openrc? |
| 56 |
|
| 57 |
I think that USE flag just causes the systemd-boot part of systemd-utils |
| 58 |
to be built. systemd-boot itself is just a virtual now. It doesn't sound |
| 59 |
like that would cause this problem, did you emerge anything X related at |
| 60 |
the same time? |
| 61 |
|
| 62 |
|
| 63 |
-- |
| 64 |
Neil Bothwick |
| 65 |
|
| 66 |
without C people would code in Basi, Pasal and Obol |
Archives