From: Alexander Kanavin <alex.kanavin@gmail.com>
To: bitbake-devel@lists.openembedded.org
Cc: Alexander Kanavin <alex@linutronix.de>
Subject: [PATCH] bin/bitbake-setup: print a note about fetcher log if something fails there
Date: Mon, 7 Sep 2026 19:32:07 +0200 [thread overview]
Message-ID: <20260907173208.3672064-1-alex.kanavin@gmail.com> (raw)
From: Alexander Kanavin <alex@linutronix.de>
Fetcher errors can sometimes be not particularly helpful, e.g.
ERROR: Fetcher failure for URL: '<url>'. Unable to fetch URL from any source.
In such situations, fetcher log can contain the actual information about what
went wrong, but bitbake-setup would not say where it is (unlike bitbake proper
which does).
So if a log exists, and isn't empty, print a note to try to help users:
ERROR: Check /home/alex/bitbake-builds/poky-master-poky-distro_poky-machine_qemux86-64/layers/logs/fetch_log.20260907192613 for additional information to diagnoze the issue.
ERROR: Fetcher failure for URL: '<url>'. Unable to fetch URL from any source.
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
---
bin/bitbake-setup | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/bin/bitbake-setup b/bin/bitbake-setup
index 427a2d835..d18d32ba0 100755
--- a/bin/bitbake-setup
+++ b/bin/bitbake-setup
@@ -985,6 +985,10 @@ def do_fetch(fetcher, dir):
try:
fetcher.download()
fetcher.unpack_update(dir)
+ except:
+ if os.path.exists(fetchlog) and os.path.getsize(fetchlog) > 0:
+ logger.error("Check {} for additional information that may help diagnoze the issue.".format(fetchlog))
+ raise
finally:
sys.stdout = oldstdout
--
2.47.3
reply other threads:[~2026-09-07 17:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260907173208.3672064-1-alex.kanavin@gmail.com \
--to=alex.kanavin@gmail.com \
--cc=alex@linutronix.de \
--cc=bitbake-devel@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