All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: daniel.turull@ericsson.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/2] devtool: upgrade: ignore changelogs from 3rd party
Date: Mon, 03 Aug 2026 14:12:48 +0100	[thread overview]
Message-ID: <358db0c094083c05a67c0d989bc6390e33659949.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260803100231.3752129-1-daniel.turull@ericsson.com>

On Mon, 2026-08-03 at 12:02 +0200, Daniel Turull via lists.openembedded.org wrote:
> From: Daniel Turull <daniel.turull@ericsson.com>
> 
> Some upstream projects bundle vendored dependencies in their source
> tree (e.g. nghttp2 ships third-party/mruby, which has its own
> NEWS.md). The changelog extractor could mistake one of these
> vendored changelogs for the recipe's own, misattributing unrelated
> upstream changes to the package being upgraded.
> 
> Exclude paths under common vendoring directory names (third-party,
> vendor, external, deps, etc.) from changelog candidates.
> 
> AI-Generated: Kiro with Claude Sonnet 5
> Signed-off-by: Daniel Turull <daniel.turull@ericsson.com>
> ---
>  scripts/lib/devtool/upgrade.py | 10 ++++++++++
>  1 file changed, 10 insertions(+)

Thanks for these. Unfortunately something in here caused the devtool tests to fail:

https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/4274

Cheers,

Richard


  parent reply	other threads:[~2026-08-03 13:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03 10:02 [PATCH 1/2] devtool: upgrade: ignore changelogs from 3rd party daniel.turull
2026-08-03 10:02 ` [PATCH 2/2] devtool: upgrade: diff git-log-style changelogs by commit hash daniel.turull
2026-08-03 13:12 ` Richard Purdie [this message]
2026-08-03 13:16   ` [OE-core] [PATCH 1/2] devtool: upgrade: ignore changelogs from 3rd party Daniel Turull

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=358db0c094083c05a67c0d989bc6390e33659949.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=daniel.turull@ericsson.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 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.