From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: jaipaul.cheernam@est.tech, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/2] epiphany: upgrade 50.6 -> 51.0
Date: Tue, 15 Sep 2026 10:57:33 +0100 [thread overview]
Message-ID: <e58a04cb8fa7a28860a4e3c82a7c5c11e993ed64.camel@linuxfoundation.org> (raw)
In-Reply-To: <7617622fbf8dc6a97c32605ef2e408d77d1c2599.1789116540.git.jaipaul.cheernam@est.tech>
On Fri, 2026-09-11 at 10:51 +0200, Jaipaul Cheernam via lists.openembedded.org wrote:
> CompareLog: https://github.com/GNOME/epiphany/compare/50.6...51.0
>
> - 51.0 adds a new mandatory dependency on pwquality [1] so add
> libpwquality to DEPENDS.
> libpwquality was imported into OE-Core in the preceding patch.
>
> [1] https://github.com/GNOME/epiphany/commit/683e9a076fa3
>
> Signed-off-by: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
> ---
> .../epiphany/{epiphany_50.6.bb => epiphany_51.0.bb} | 3 ++-
> .../0002-help-meson.build-disable-the-use-of-yelp.patch | 2 +-
> meta/recipes-gnome/epiphany/files/distributor.patch | 4 ++--
> meta/recipes-gnome/epiphany/files/migrator.patch | 6 +++---
> 4 files changed, 8 insertions(+), 7 deletions(-)
> rename meta/recipes-gnome/epiphany/{epiphany_50.6.bb => epiphany_51.0.bb} (92%)
Just for info, upgrading to a new version of gnome will probably need
to wait until after the current release now so we'll need to wait on
this for a bit.
Cheers,
Richard
prev parent reply other threads:[~2026-09-15 9:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 8:51 [PATCH 0/2] epiphany: upgrade to 51.0 and import libpwquality Jaipaul Cheernam
2026-09-11 8:51 ` [PATCH 1/2] libpwquality: import recipe from meta-oe Jaipaul Cheernam
2026-09-11 9:01 ` Patchtest results for " patchtest
2026-09-13 21:25 ` [OE-core] " Marko, Peter
2026-09-14 21:14 ` Jaipaul Cheernam
2026-09-11 8:51 ` [PATCH 2/2] epiphany: upgrade 50.6 -> 51.0 Jaipaul Cheernam
2026-09-15 9:57 ` 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=e58a04cb8fa7a28860a4e3c82a7c5c11e993ed64.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=jaipaul.cheernam@est.tech \
--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