All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: jaipaul.cheernam@est.tech, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v2 1/2] swig: upgrade 4.4.1 -> 4.5.0
Date: Tue, 11 Aug 2026 11:25:45 +0100	[thread overview]
Message-ID: <61f96793beba861118dc9502be1590176dfef6af.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260811061251.14757-2-jaipaul.cheernam@est.tech>

On Tue, 2026-08-11 at 08:12 +0200, Jaipaul Cheernam via lists.openembedded.org wrote:
> ChangeLog: https://www.swig.org/Release/CHANGES.current
> 
> Release Notes: https://www.swig.org/Release/RELEASENOTES
> 
> CompareLog: https://github.com/swig/swig/compare/v4.4.1...v4.5.0
> 
> - Refresh determinism.patch
> 
> Signed-off-by: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
> ---
>  .../swig/swig/determinism.patch               | 20 +++++++++----------
>  .../swig/{swig_4.4.1.bb => swig_4.5.0.bb}     |  4 ++--
>  2 files changed, 12 insertions(+), 12 deletions(-)
>  rename meta/recipes-devtools/swig/{swig_4.4.1.bb => swig_4.5.0.bb} (92%)

I suspect this breaks u-boot-tools:

https://autobuilder.yoctoproject.org/valkyrie/#/builders/25/builds/4370
https://autobuilder.yoctoproject.org/valkyrie/#/builders/17/builds/4214

and maybe python3-dtc:

https://autobuilder.yoctoproject.org/valkyrie/#/builders/89/builds/4188

Cheers,

Richard


  reply	other threads:[~2026-08-11 10:25 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-10 15:45 [PATCH] swig: upgrade 4.4.1 -> 4.5.0 Jaipaul Cheernam
2026-08-10 21:02 ` [OE-core] " Richard Purdie
2026-08-11  6:12 ` [PATCH v2 0/2] " Jaipaul Cheernam
2026-08-11  6:12   ` [PATCH v2 1/2] " Jaipaul Cheernam
2026-08-11 10:25     ` Richard Purdie [this message]
2026-08-11 11:15       ` [OE-core] " Jaipaul Cheernam
2026-08-11  6:12   ` [PATCH v2 2/2] babeltrace2: fix build with swig 4.5.0 Jaipaul Cheernam
2026-08-11 11:11 ` [PATCH v3 0/4] swig: upgrade 4.4.1 -> 4.5.0 Jaipaul Cheernam
2026-08-11 11:11   ` [PATCH v3 1/4] " Jaipaul Cheernam
2026-08-11 11:11   ` [PATCH v3 2/4] babeltrace2: fix build with swig 4.5.0 Jaipaul Cheernam
2026-08-11 11:11   ` [PATCH v3 3/4] u-boot-tools: fix pylibfdt " Jaipaul Cheernam
2026-08-11 12:58     ` [OE-core] " Mathieu Dubois-Briand
2026-08-11 13:38     ` Quentin Schulz
2026-08-11 11:11   ` [PATCH v3 4/4] python3-dtc: fix " Jaipaul Cheernam
2026-08-11 13:51 ` [PATCH v4 0/4] swig: upgrade 4.4.1 -> 4.5.0 Jaipaul Cheernam
2026-08-11 13:51   ` [PATCH v4 1/4] " Jaipaul Cheernam
2026-08-11 13:51   ` [PATCH v4 2/4] babeltrace2: fix build with swig 4.5.0 Jaipaul Cheernam
2026-08-11 13:51   ` [PATCH v4 3/4] u-boot-tools: fix pylibfdt " Jaipaul Cheernam
2026-08-11 13:52   ` [PATCH v4 4/4] python3-dtc: fix " Jaipaul Cheernam
2026-08-12  9:11     ` [OE-core] " Mathieu Dubois-Briand
2026-08-12 12:05 ` [PATCH v5 0/4] swig: upgrade 4.4.1 -> 4.5.0 Jaipaul Cheernam
2026-08-12 12:05   ` [PATCH v5 1/4] " Jaipaul Cheernam
2026-08-12 12:05   ` [PATCH v5 2/4] babeltrace2: fix build with swig 4.5.0 Jaipaul Cheernam
2026-08-12 12:05   ` [PATCH v5 3/4] u-boot: fix pylibfdt " Jaipaul Cheernam
2026-08-12 12:05   ` [PATCH v5 4/4] python3-dtc: fix " Jaipaul Cheernam

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=61f96793beba861118dc9502be1590176dfef6af.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 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.