Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Marcus Comstedt <marcus.comstedt@requtech.se>
To: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Cc: Steve Sakoman <steve@sakoman.com>
Subject: [scarthgap][backport] Fix packaging of stale externalsrc recipes
Date: Tue, 3 Dec 2024 09:13:53 +0000	[thread overview]
Message-ID: <87mshdgmcv.fsf@requtech.se> (raw)


Hi.

After upgrading from dunfell to scarthgap (due to the EOL of the
former), I discovered that bitbake would occasionally package versions
of externalsrc packages that did not contain the latest changes.

The details are in this bug:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=15646

As Ross Burton noted, this issue has already been identified and fixed
on master, in commit

475759fdab7200488b2a568b2ba1aa31a456d113

I have verified that this commit can be cleanly cherry-picked to
scarthgap and does indeed fix the issue.

Since this is a rather serious issue (at least to me, and probably
anyone else using the same externalsrc recipe in more than one yocto
build), I would like to see this commit backported to the scarthgap
branch.  The only alternative for me would be to fork openembedded-core
in order to do the cherry-pick myself.

I believe the same issue applies to kirkstone, although I have no
personal stake in it getting backported to that branch.  And the same
for non-LTS branch styhead.  All other affected branches are EOL, AFAICT.

Thanks


  // Marcus



             reply	other threads:[~2024-12-03  9:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03  9:13 Marcus Comstedt [this message]
2024-12-03 13:44 ` [scarthgap][backport] Fix packaging of stale externalsrc recipes Steve Sakoman

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=87mshdgmcv.fsf@requtech.se \
    --to=marcus.comstedt@requtech.se \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=steve@sakoman.com \
    /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