Greetings,
since my last routine Gentoo upgrade on 2021-02-01 "fwupd" is no longer
started in the "default" run level. Reason is that "fwupd" erroneously
thinks its prerequisite "elogind" is not yet running, starts it again,
interprets the error messa
On Thu, 2 Jun 2022 at 17:33, Dr Rainer Woitok
wrote:
> Greetings,
>
> my last successful build of "sys-apps/fwupd" was 1.7.7-r2. Immediately
> before my vacation 1.8.0 failed on 2022-05-10, and today 1.8.1 failed,
> too.
>
> Since the build log says at its
Arve,
On Thursday, 2022-06-02 17:46:14 +0200, you wrote:
> ...
> According to https://bugs.gentoo.org/841767 this could possibly be fixed
> for you by either activating the gusb USE flag, or de-activating the
> modemmanager USE flag.
Bingo! Activating the "gusb" USE flag did the trick! Many
Dr Rainer Woitok wrote:
>
> Yes. To satisfy the requirements of package "sys-apps/fwupd" I long ago
> added the line
>
>>=app-crypt/tpm2-tss-2.2.3-r1 ~amd64
Ah! That explains it.
> But this only means that I accept an unstable package here, not that
Martin,
On Friday, 2020-04-24 17:32:09 -, you wrote:
> ...
> Maybe you run an unstable system, that is ACCEPT_KEYWORDS='~amd64'?
No.
> Or do you have a corresponding entry in package.{accept_,}keywords?
Yes. To satisfy the requirements of package "sys-apps/fwupd&quo
ed by something else, although the only other file
in /etc/init.d that needs it is fwupd, which is not currently running
(and not automatically started).
I suppose if I put elogind in the default runlevel, then open-rc will
hopefully start it before it would otherwise get launched, but I'm
curio
6 matches
Mail list logo
