From: Matthias Hanft <mh@hanft.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Update of systemd-utils failes (OpenRC)
Date: Sat, 8 Feb 2025 09:56:20 +0100 [thread overview]
Message-ID: <40682dd1-b0bb-5bc7-4526-fa3e8a3c4066@hanft.de> (raw)
In-Reply-To: <29a0377a-1a44-b6a2-1c61-1d1562252455@hanft.de>
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
next prev parent reply other threads:[~2025-02-08 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-08 8:45 [gentoo-user] Update of systemd-utils failes (OpenRC) Matthias Hanft
2025-02-08 8:56 ` Matthias Hanft [this message]
2025-02-08 10:55 ` Michael
2025-02-09 6:00 ` Eli Schwartz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40682dd1-b0bb-5bc7-4526-fa3e8a3c4066@hanft.de \
--to=mh@hanft.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox