From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] glib: Version bump. 2.88.3 -> 2.90.0
Date: Mon, 21 Sep 2026 08:38:15 +0200 [thread overview]
Message-ID: <20260921063815.3168188-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20260912195443.2749503-1-christian.melki@t2data.com>
Thanks, applied as c53c5b7b2c1213ca82efeb20736256ee149aba17.
Michael
[sent from post-receive hook]
On Mon, 21 Sep 2026 08:38:15 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> A long list of changes, bug and security fixes for the new stable series.
> https://gitlab.gnome.org/GNOME/glib/-/releases/2.89.0
> https://gitlab.gnome.org/GNOME/glib/-/releases/2.89.1
> https://gitlab.gnome.org/GNOME/glib/-/releases/2.89.2
> https://gitlab.gnome.org/GNOME/glib/-/releases/2.89.3
> https://gitlab.gnome.org/GNOME/glib/-/releases/2.89.4
> https://gitlab.gnome.org/GNOME/glib/-/releases/2.90.0
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20260912195443.2749503-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/glib.make b/rules/glib.make
> index a90344b678aa..347465f82ea5 100644
> --- a/rules/glib.make
> +++ b/rules/glib.make
> @@ -15,8 +15,8 @@ PACKAGES-$(PTXCONF_GLIB) += glib
> #
> # Paths and names
> #
> -GLIB_VERSION := 2.88.3
> -GLIB_SHA256 := ab24d24e698dfa1e408b7bcdb508f4aafc906185a8b8ce72fdf79bbbdc9b383b
> +GLIB_VERSION := 2.90.0
> +GLIB_SHA256 := 17d15cac2af80a33271127408e0abc2748eb297c595c2a26409e81e14e7d1b8f
> GLIB := glib-$(GLIB_VERSION)
> GLIB_SUFFIX := tar.xz
> GLIB_URL := $(call ptx/mirror, GNOME, glib/$(basename $(GLIB_VERSION))/$(GLIB).$(GLIB_SUFFIX))
prev parent reply other threads:[~2026-09-21 6:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 19:54 [ptxdist] [PATCH] " Christian Melki
2026-09-21 6:38 ` Michael Olbrich [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=20260921063815.3168188-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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