From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: mr.name@web.de, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] sysvinit: upgrade 3.04 -> 3.10
Date: Fri, 30 Aug 2024 07:09:02 +0100 [thread overview]
Message-ID: <64c0811f16f7b9af17c4f493af3080befc1bb1b7.camel@linuxfoundation.org> (raw)
In-Reply-To: <18822.1724963809858109674@lists.openembedded.org>
On Thu, 2024-08-29 at 13:36 -0700, Sven Reschke via
lists.openembedded.org wrote:
> > On Thu, Aug 29, 2024 at 1:52 AM Richard Purdie via
> > lists.openembedded.org
> > <richard.purdie=linuxfoundation.org@...> wrote:
> > > On Mon, 2024-08-26 at 12:01 -0700, Sven Reschke via
> > > lists.openembedded.org wrote:
> > > > Hi Alex and Alexandre,
> > > >
> > > > sorry for the delay.
> > > > I've created a PR on Github on top of your latest changes:
> > > > https://github.com/Nanowires/oe-core-clone/pull/1
> > > I did try this on our automated testing and there were some
> > > issues:
> > >
> > > musl build failures:
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/9440/steps/11/logs/stdio
> > > https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/9456/steps/11/logs/stdio
> > This can be fixed by using realpath(path, NULL) API instead of
> > canonicalize_file_name(path), we have done such changes
> > in few packages e.g. elfutils
> >
> > https://sourceware.org/git/?p=elfutils.git;a=commitdiff;h=06263dda990be6778a4beb33481cfd39ce60c623;hp=fd0cee63fb02455a5021ca298da8dadb4df63a9a
> >
> > there is a meta-oe patch for ssiapi
> > https://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-support/ssiapi/ssiapi/0003-replace-canonicalize_file_name-with-realpath.patch
> >
> first of all: Thanks for the automated testing :-)
> Yes, I broke the realpath.patch with my update. I've pushed a fix,
> which should solve this issue.
>
>
> > systemd+sysvinit build failure:
> >
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/9431/steps/25/logs/stdio
> >
> > Cheers,
> >
> > Richard
> For this I fixed the install.patch (which I removed in the first
> place). Could you re-run the tests with my latest commits? ;-)
I can't just test one persons changes so there are multiple patches
causing multiple issues in this build but there still seem to be
sysvinit issues:
https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/5903/steps/12/logs/stdio
There are probably other issues in there too.
As Alex says, pulling patches from github subverts our review process
so whilst I did it as a one off, I can't do this on a regular basis.
Cheers,
Richard
prev parent reply other threads:[~2024-08-30 6:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-18 9:39 [PATCH] sysvinit: upgrade 3.04 -> 3.10 Sven Reschke
2024-08-18 9:45 ` Sven Reschke
2024-08-18 9:52 ` Sven Reschke
2024-08-22 11:02 ` [OE-core] " Alexandre Belloni
2024-08-22 11:05 ` Alexander Kanavin
2024-08-22 18:12 ` Sven Reschke
2024-08-22 19:34 ` [OE-core] " Alexander Kanavin
2024-08-26 19:01 ` Sven Reschke
2024-08-29 8:51 ` [OE-core] " Richard Purdie
2024-08-29 9:56 ` Alexander Kanavin
2024-08-29 17:15 ` Khem Raj
2024-08-29 20:36 ` Sven Reschke
2024-08-29 21:13 ` [OE-core] " Alexander Kanavin
2024-08-30 6:09 ` Richard Purdie [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=64c0811f16f7b9af17c4f493af3080befc1bb1b7.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=mr.name@web.de \
--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