From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: ChenQi <Qi.Chen@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH 1/3] systemd: upgrade to 255.1
Date: Mon, 22 Jan 2024 09:18:54 +0100 [thread overview]
Message-ID: <2024012208185452e26e37@mail.local> (raw)
In-Reply-To: <78b1e91b-d681-2031-55a3-b622bccb211d@windriver.com>
On 22/01/2024 16:15:41+0800, ChenQi wrote:
> On 1/22/24 16:04, Alexandre Belloni wrote:
> > On 22/01/2024 12:38:15+0800, ChenQi wrote:
> > > On 1/20/24 02:14, Alexandre Belloni wrote:
> > > > On 19/01/2024 19:13:25+0100, Alexandre Belloni wrote:
> > > > > On 19/01/2024 11:09:20+0800, Chen Qi via lists.openembedded.org wrote:
> > > > > > What's the status of this patch series?
> > > > > > Is there any issue or concern that I missed?
> > > > > I'm glad you asked, I got this today:
> > > > >
> > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/8466/steps/26/logs/warnings
> > > > and I know you sent a patch for this but it didn't make it yet.
> > > I just double checked with the following settings from the "Sysvinit with
> > > systemd" entry in config.json, there's no warning.
> > >
> > > DISTRO_FEATURES:append = ' systemd usrmerge'
> > > ROOT_HOME = '/root'
> > > VIRTUAL-RUNTIME_init_manager = 'sysvinit'
> > >
> > > So I further checked the build's settings.
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/8466
> > >
> > > In the second step, "Fetch yocto-autobuilder-helper", I can see the
> > > following logs:
> > >
> > > HEAD is now at ebb7e65 config.json: Fix syntax errors
> > >
> > > So the build is not using the latest repo. The latest commit is:
> > This is not correct, it was using the latest commit at the time, the
> > patch was applied after my email.
> >
> >
> OK... Do you mean that the warning appeared in autobuilder, and then you
> applied the patch to yocto-autobuilder-helper to make the warning disappear?
> I thought you meant that the warning continued to exist even with the patch.
>
> To clarify, we can now wait for autobuiler's results and I don't need to do
> anything more, right?
I confirm, no action is needed on your side.
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2024-01-22 8:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 4:20 [OE-core][PATCH 1/3] systemd: upgrade to 255.1 Qi.Chen
2023-12-27 4:20 ` [OE-core][PATCH 2/3] systemd-boot: " Qi.Chen
2023-12-27 4:20 ` [OE-core][PATCH 3/3] rootfs-postcommands.bbclass: ignore comment mismatch in systemd_user_check Qi.Chen
2023-12-27 11:59 ` [OE-core][PATCH 1/3] systemd: upgrade to 255.1 Alexandre Belloni
2023-12-28 3:00 ` Chen, Qi
2023-12-28 3:19 ` Khem Raj
2023-12-28 3:32 ` Chen, Qi
2023-12-28 21:14 ` Alexandre Belloni
2023-12-29 2:38 ` ChenQi
2023-12-29 8:03 ` Alexander Kanavin
2023-12-29 10:48 ` Chen, Qi
2024-01-05 16:01 ` Alexandre Belloni
2024-01-07 14:05 ` Chen, Qi
2024-01-09 7:47 ` Alexandre Belloni
2024-01-09 8:14 ` Chen, Qi
2024-01-19 3:09 ` ChenQi
2024-01-19 18:13 ` Alexandre Belloni
2024-01-19 18:14 ` Alexandre Belloni
2024-01-22 4:38 ` ChenQi
2024-01-22 8:04 ` Alexandre Belloni
2024-01-22 8:15 ` ChenQi
2024-01-22 8:18 ` Alexandre Belloni [this message]
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=2024012208185452e26e37@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=Qi.Chen@windriver.com \
--cc=openembedded-core@lists.openembedded.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