[gentoo-user] Update of systemd-utils failes (OpenRC)

[Matthias Hanft <mh@hanft.de>]

Hi,

I'm using OpenRC (no systemd).

After "emerge --sync" today, emerge wants to update systemd-utils
from 254.17 to 255.15-r1 and fails with:

>>> Test phase [disabled because of RESTRICT=test]: sys-apps/systemd-utils-255.15-r1
>>> Install sys-apps/systemd-utils-255.15-r1 into /var/tmp/portage/sys-apps/systemd-utils-255.15-r1/image
 * abi_x86_64.amd64: running multilib-minimal_abi_src_install
Error: File --set-rpath does not exist.
 * ERROR: sys-apps/systemd-utils-255.15-r1::gentoo failed (install phase):
 *   patchelf failed

"equery u systemd-utils" shows:

 * Found these USE flags for sys-apps/systemd-utils-255.15-r1:
 U I
 - - abi_x86_32                      : 32-bit (x86) libraries
 + + acl                             : Add support for Access Control Lists
 - - boot                            : Enable systemd-boot (UEFI boot manager)
 - - kernel-install                  : Enable kernel-install
 + - kmod                            : Enable kernel module loading via sys-apps/kmod
 - - python_single_target_python3_10 : Build for Python 3.10 only
 - - python_single_target_python3_11 : Build for Python 3.11 only
 + + python_single_target_python3_12 : Build for Python 3.12 only
 - - python_single_target_python3_13 : Build for Python 3.13 only
 - - secureboot                      : Automatically sign efi executables using user specified key
 - - sysusers                        : Enable systemd-sysusers
 - - test                            : Enable dependencies and/or preparations necessary to run tests (usually
                                       controlled by FEATURES=test but can be toggled independently)
 + - tmpfiles                        : Enable systemd-tmpfiles
 + - udev                            : Enable systemd-udev (userspace device manager)
 - - ukify                           : Enable systemd-ukify

and I wonder why there are so many differences between "U" and "I".

Do I have to change any USE flags to get the update installed?
Or is there another solution? Or is it just a bug which will be
corrected by next week?

Thanks,

-Matt