From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Norbert Lange <nolange79@gmail.com>,
Sen Hastings <sen@phobosdpl.com>,
"Yann E . MORIN" <yann.morin.1998@free.fr>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/systemd: select kdb
Date: Mon, 31 Jul 2023 23:57:37 +0200 [thread overview]
Message-ID: <20230731235737.3a0eb6a5@windsurf> (raw)
In-Reply-To: <20230731214559.99648-1-james.hilliard1@gmail.com>
Hello James,
On Mon, 31 Jul 2023 15:45:59 -0600
James Hilliard <james.hilliard1@gmail.com> wrote:
> We need to select BR2_PACKAGE_KBD when building systemd with vconsole.
>
> Fixes:
> systemd-vconsole-setup[129]: /usr/bin/loadkeys failed with exit status 1.
>
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
Same question as always: since when is this needed? I suppose since
commit 36d275f695936b7a54738c0354572944c1f08d87 ("package/systemd: bump
to version 254"), but I don't know, and Peter will have an even harder
time figuring this out when he will try to figure out which commits in
master need to be backported to the stable branch.
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-07-31 21:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 21:45 [Buildroot] [PATCH 1/1] package/systemd: select kdb James Hilliard
2023-07-31 21:57 ` Thomas Petazzoni via buildroot [this message]
2023-07-31 22:07 ` James Hilliard
2023-07-31 22:18 ` Thomas Petazzoni via buildroot
2023-08-01 20:01 ` Yann E. MORIN
2023-08-01 21:09 ` James Hilliard
2023-08-02 14:11 ` Yann E. MORIN
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=20230731235737.3a0eb6a5@windsurf \
--to=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=nolange79@gmail.com \
--cc=sen@phobosdpl.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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