From: Markus Volk <f_l_k@t-online.de>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Cc: openembedded-devel@lists.openembedded.org
Subject: Preview GTK-47.0
Date: Mon, 16 Sep 2024 14:48:23 +0200 [thread overview]
Message-ID: <NWOWJS.9JQ0730OG8B71@t-online.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 782 bytes --]
pre-release version of gnome 47. There were some issues, mainly in
tracker. Besides the obligatory newly included build paths, the
programs were annoyingly renamed from tracker/tracker-miners to
tinysparql/localsearch. This has caused a merry go round of changes all
over the place.
I will wait to send the updates to the mailing list until styhead
release is finalized. At best gtk4, glib-2.0 and libadwaita in oe-core
should be updated first. That would allow to put in all the updates for
meta-openembedded in one go.
This includes all the changes I made to oe-core and meta-openembedded.
I have tested this for x86-64 and aarch64 so far.
<https://codeberg.org/flk/meta-image/src/branch/master/meta>
<https://codeberg.org/flk/meta-image/src/branch/master/meta-gnome>
[-- Attachment #2: Type: text/html, Size: 1062 bytes --]
reply other threads:[~2024-09-16 12:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=NWOWJS.9JQ0730OG8B71@t-online.de \
--to=f_l_k@t-online.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@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