From: Khem Raj <raj.khem@gmail.com>
To: Marek Vasut <marex@denx.de>
Cc: Alexander Kanavin <alex.kanavin@gmail.com>,
OE-core <openembedded-core@lists.openembedded.org>,
Alexander Kanavin <alex@linutronix.de>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Subject: Re: [OE-core] [PATCH] ffmpeg: Update from 4.4.1 to 5.0
Date: Thu, 20 Jan 2022 12:33:08 -0800 [thread overview]
Message-ID: <CAMKF1soPeRuNjAtjFEONmS_i5oHPcBhWd0FeHh9VcVFO4D8jpA@mail.gmail.com> (raw)
In-Reply-To: <7e645982-b148-680c-c6aa-89724716f659@denx.de>
On Thu, Jan 20, 2022 at 12:28 PM Marek Vasut <marex@denx.de> wrote:
>
> On 1/20/22 21:15, Khem Raj wrote:
> > there are bunch of failures in meta-openembedded as well see
> >
> > https://errors.yoctoproject.org/Errors/Build/138784/
>
> So, how shall we proceed here ?
>
> I suspect Alex will send a patch for the problem detected in oe-core and
> then oe-core with ffmpeg 5.0 won't be broken anymore.
>
> As for the rest of the recipes in meta-openembedded, they will likely be
> catching up to ffmpeg 5.0 over time, so we can either upgrade them, or
> patch them. I suspect the former is more favorable approach.
Someone needs to fix them.
as seen this is not a trivial amount of recipes to fix. Generally its cordial to
keep meta-openembedded working for extended testing and CI.
>
> However, what is not clear to me is whether this breakage in
> meta-openembedded is a blocker for this patch to be applied to oe-core
> (with the fix from Alex), or not ?
next prev parent reply other threads:[~2022-01-20 20:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 18:50 [PATCH] ffmpeg: Update from 4.4.1 to 5.0 Marek Vasut
2022-01-18 20:48 ` [OE-core] " Alexander Kanavin
2022-01-20 20:15 ` Khem Raj
2022-01-20 20:28 ` Marek Vasut
2022-01-20 20:33 ` Khem Raj [this message]
2022-01-20 20:47 ` Alexander Kanavin
2022-01-21 19:35 ` Alexander Kanavin
[not found] ` <16CC6034E1AC2CBC.18829@lists.openembedded.org>
2022-01-21 21:41 ` Alexander Kanavin
[not found] ` <16CC67149B14BEF3.29636@lists.openembedded.org>
2022-01-22 21:47 ` Alexander Kanavin
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=CAMKF1soPeRuNjAtjFEONmS_i5oHPcBhWd0FeHh9VcVFO4D8jpA@mail.gmail.com \
--to=raj.khem@gmail.com \
--cc=alex.kanavin@gmail.com \
--cc=alex@linutronix.de \
--cc=marex@denx.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).