Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
	 openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 05/15] mesa/mesa-tools-native: Upgrade 26.1.2 -> 26.1.4
Date: Sun, 05 Jul 2026 10:45:31 +0100	[thread overview]
Message-ID: <d81936f4d8a3bed25ad0bd34e6f2503798906044.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj9mveU24cR_VQky=rTAFze_2gffU22a9WJ_jetLsaxLTA@mail.gmail.com>

On Sun, 2026-07-05 at 10:43 +0200, Alexander Kanavin wrote:
> On Sun, 5 Jul 2026 at 10:32, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> 
> > > Just to confirm, we indeed have this error:
> > > https://autobuilder.yoctoproject.org/valkyrie/#/builders/59/builds/4097
> > 
> > I've queued my .4 with Alex's patch, thanks.
> 
> This patch is coming from a big rollup of everything that was
> released in June:
> https://git.openembedded.org/openembedded-core-contrib/log/?h=akanavin/package-version-updates
> 
> This set is now ready, but it has been cooking long enough that
> meanwhile upstreams have released even newer versions, and patches
> were sent for them, so to avoid clutter and duplicates, let's merge
> the newer versions first, then I'll rebase and send. E.g. mesa is
> updated to .3 in my set, but latest is already .4.

I've had this happen to me a couple of times as well, where upstream
release a new point release, obsoleting the thing I was testing.

It is important to get the newer point releases that happen 'fast' as
they often do that for important bug fixes.

We'll work things out but I am keen to try and get us then keep us up
to date.

Cheers,

Richard


  reply	other threads:[~2026-07-05  9:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-03  8:29 [PATCH 01/15] hwdata: upgrade 0.408 -> 0.409 Richard Purdie
2026-07-03  8:29 ` [PATCH 02/15] libadwaita: upgrade 1.9.1 -> 1.9.2 Richard Purdie
2026-07-03  8:29 ` [PATCH 03/15] python3-typing-extensions: upgrade 4.15.0 -> 4.16.0 Richard Purdie
2026-07-03  8:29 ` [PATCH 04/15] jansson: upgrade 2.15.0 -> 2.15.1 Richard Purdie
2026-07-03  8:29 ` [PATCH 05/15] mesa/mesa-tools-native: Upgrade 26.1.2 -> 26.1.4 Richard Purdie
2026-07-03 21:36   ` [OE-core] " Alexander Kanavin
2026-07-05  8:23     ` Mathieu Dubois-Briand
2026-07-05  8:32       ` Richard Purdie
2026-07-05  8:43         ` Alexander Kanavin
2026-07-05  9:45           ` Richard Purdie [this message]
2026-07-03  8:29 ` [PATCH 06/15] diffoscope: upgrade 319 -> 323 Richard Purdie
2026-07-03  8:29 ` [PATCH 07/15] enchant2: upgrade 2.8.16 -> 2.8.17 Richard Purdie
2026-07-03  8:29 ` [PATCH 08/15] igt-gpu-tools: upgrade 2.4 -> 2.5 Richard Purdie
2026-07-03  8:29 ` [PATCH 09/15] libxmlb: upgrade 0.3.27 -> 0.3.28 Richard Purdie
2026-07-03  8:29 ` [PATCH 10/15] python3-cython: upgrade 3.2.5 -> 3.2.8 Richard Purdie
2026-07-03  8:29 ` [PATCH 11/15] python3-rpds-py: upgrade 2026.5.1 -> 2026.6.3 Richard Purdie
2026-07-03  8:29 ` [PATCH 12/15] python3-uv-build: upgrade 0.11.21 -> 0.11.26 Richard Purdie
2026-07-03  8:29 ` [PATCH 13/15] erofs-utils: upgrade 1.9.1 -> 1.9.2 Richard Purdie
2026-07-03  8:29 ` [PATCH 14/15] libjpeg-turbo: upgrade 3.1.4.1 -> 3.2.0 Richard Purdie
2026-07-03  8:29 ` [PATCH 15/15] gpgme: upgrade 2.1.0 -> 2.1.2 Richard Purdie

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=d81936f4d8a3bed25ad0bd34e6f2503798906044.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alex.kanavin@gmail.com \
    --cc=mathieu.dubois-briand@bootlin.com \
    --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