Matthias Hanft wrote: > > After "emerge --sync" today, emerge wants to update systemd-utils > from 254.17 to 255.15-r1 and fails with: [...]
Ok, it was my own fault: I had another (own) "patchelf" (for legacy Kylix programs) in /usr/local/bin which came first in $PATH. Now the update was OK. Just the question remains: > 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 With the update installed, the USE flags kmod, tmpfiles and udev changed from "off" to "on". Is this important, do I have to worry, or can I just ignore it (because there's no impact at all without systemd? -Matt
