All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Volk <f_l_k@t-online.de>
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org,
	Ross Burton <ross.burton@arm.com>
Subject: Re: [oe-core][PATCH 3/3] adwaita-icon-theme: upgrade 50.0 -> 51.0
Date: Wed, 16 Sep 2026 11:05:36 +0200	[thread overview]
Message-ID: <C99GLT.GR8BI2T2HG851@t-online.de> (raw)
In-Reply-To: <321582c9e3e2e99229b5a74bd3d244bdc1e0b270.camel@linuxfoundation.org>

[-- Attachment #1: Type: text/plain, Size: 532 bytes --]

Hi Richard,

I created the GNOME-51 recipes to verify the basic functionality and 
test it in a runtime environment.
The only really annoying issue I've noticed so far is a segfault in 
gnome-keyring-51, which I've already
been able to fix locally. I don’t want to cause any confusion, and if 
the general consensus is that the
GNOME update should only be added after the release, I’m fine with 
that. However, if glib-2.0, gtk4
and libadwaita do make it into the release, I would personally consider 
that a benefit.


[-- Attachment #2: Type: text/html, Size: 642 bytes --]

  reply	other threads:[~2026-09-16  9:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-16  5:53 [oe-core][PATCH 1/3] gtk4: upgrade 4.22.5 -> 4.24.0 Markus Volk
2026-09-16  5:53 ` [oe-core][PATCH 2/3] libadwaita: upgrade 1.9.3 -> 1.10.0 Markus Volk
2026-09-16  5:53 ` [oe-core][PATCH 3/3] adwaita-icon-theme: upgrade 50.0 -> 51.0 Markus Volk
2026-09-16  8:41   ` Richard Purdie
2026-09-16  9:05     ` Markus Volk [this message]
2026-09-16  9:12     ` Ross Burton
2026-09-16 11:43 ` [oe-core][PATCH 1/3] gtk4: upgrade 4.22.5 -> 4.24.0 Antonin Godard
2026-09-16 14:18   ` Markus Volk
2026-09-18 11:19   ` Ross Burton
2026-09-18 12:18     ` Markus Volk
2026-09-18 16:17       ` Ross Burton
2026-09-21 13:00         ` Ross Burton

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=C99GLT.GR8BI2T2HG851@t-online.de \
    --to=f_l_k@t-online.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=ross.burton@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.