From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: James Hilliard <james.hilliard1@gmail.com>,
buildroot@buildroot.org, Norbert Lange <nolange79@gmail.com>,
Romain Naour <romain.naour@smile.fr>,
Sen Hastings <sen@phobosdpl.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/systemd: bump to version 254
Date: Mon, 31 Jul 2023 22:39:40 +0200 [thread overview]
Message-ID: <20230731203940.GD421096@scaer> (raw)
In-Reply-To: <20230731212049.10b538fd@windsurf>
James, All,
On 2023-07-31 21:20 +0200, Thomas Petazzoni via buildroot spake thusly:
> On Sat, 29 Jul 2023 00:56:16 -0600
> James Hilliard <james.hilliard1@gmail.com> wrote:
> > package/systemd/systemd.hash | 4 ++--
> > package/systemd/systemd.mk | 29 ++++++++++++-----------------
> > 2 files changed, 14 insertions(+), 19 deletions(-)
> I am getting back to you regarding this version bump. Did you run the
> systemd test cases in supporting/testing after doing this version bump?
>
> Indeed, it seems like the systemd test cases are no broken. See
> https://gitlab.com/buildroot.org/buildroot/-/pipelines/950175077/failures
> for the full list of failed cases (a number are not systemd related,
> and not relevant here, but many are systemd related).
>
> I looked at only one, and the failure happens at runtime and goes like
> this:
>
> # systemctl --no-pager --failed --no-legend
> ● systemd-vconsole-setup.service loaded failed failed Virtual Console Setup
# journalctl -u systemd-vconsole-setup.service
Jul 31 20:21:04 buildroot systemd-vconsole-setup[129]: /usr/bin/loadkeys failed with exit status 1.
So it looks like it needs kbd (for loadkeys). v252 already did, so it
would be interesting to also understand why it did not fail then, while
it fails now.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-07-31 20:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-29 6:56 [Buildroot] [PATCH 1/1] package/systemd: bump to version 254 James Hilliard
2023-07-29 8:59 ` Thomas Petazzoni via buildroot
2023-07-31 19:20 ` Thomas Petazzoni via buildroot
2023-07-31 20:39 ` Yann E. MORIN [this message]
2023-08-02 22:12 ` Romain Naour
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=20230731203940.GD421096@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=nolange79@gmail.com \
--cc=romain.naour@smile.fr \
--cc=sen@phobosdpl.com \
--cc=thomas.petazzoni@bootlin.com \
/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