Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Jamin Lin <jamin_lin@aspeedtech.com>
To: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Cc: Troy Lee <troy_lee@aspeedtech.com>,
	Jamin Lin <jamin_lin@aspeedtech.com>,
	Vince Chang <vince_chang@aspeedtech.com>
Subject: [PATCH v1 0/2] oe: Fix build failures with multiple git SRC_URI entries
Date: Fri, 15 May 2026 09:36:17 +0000	[thread overview]
Message-ID: <20260515093615.126849-1-jamin_lin@aspeedtech.com> (raw)

Some recipes (e.g. Zephyr-based) use multiple git SRC_URI entries with
different destsuffix values, causing each source to be unpacked into a
separate subdirectory of EXTERNALSRC that retains its own .git directory.

These nested git repositories trigger two independent failures:

1. externalsrc.bbclass: 'git add -A .' exits with code 128 during
   srctree_hash_files(), halting the bitbake parse phase.

2. oe/reproducible.py: 'git log -1' exits with code 128 inside a nested
   repo found by find_git_repositories(), aborting do_unpack.

Jamin Lin (2):
  externalsrc: Handle nested git repos from multiple SRC_URI entries
  reproducible: Handle nested git repos in find_git_repositories

 meta/classes/externalsrc.bbclass | 37 +++++++++++++++++++++++++++++++-
 meta/lib/oe/reproducible.py      |  6 +++++-
 2 files changed, 41 insertions(+), 2 deletions(-)

-- 
2.43.0


             reply	other threads:[~2026-05-15  9:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-15  9:36 Jamin Lin [this message]
2026-05-15  9:36 ` [PATCH v1 1/2] externalsrc: Handle nested git repos from multiple SRC_URI entries Jamin Lin
2026-05-18 19:16   ` Paul Barker
2026-05-19  6:28     ` Jamin Lin
2026-05-19 10:04       ` [OE-core] " Paul Barker
2026-05-20  3:25         ` Jamin Lin
2026-05-20  5:24           ` Jamin Lin
2026-05-19  7:07     ` Jamin Lin
2026-05-19  9:09       ` Jamin Lin
2026-05-15  9:36 ` [PATCH v1 2/2] reproducible: Handle nested git repos in find_git_repositories Jamin Lin
2026-05-18 19:22   ` Paul Barker

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=20260515093615.126849-1-jamin_lin@aspeedtech.com \
    --to=jamin_lin@aspeedtech.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=troy_lee@aspeedtech.com \
    --cc=vince_chang@aspeedtech.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