From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <chris.laplante@agilent.com>, <bitbake-devel@lists.openembedded.org>
Cc: <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH 1/4] lib: rename fetch2 as fetch; invert compat shim to make bb.fetch2 = bb.fetch
Date: Fri, 28 Aug 2026 07:51:43 +0200 [thread overview]
Message-ID: <DL0CCF115T08.227YUHOXXHLP3@bootlin.com> (raw)
In-Reply-To: <20260827142958.547182-1-chris.laplante@agilent.com>
On Thu Aug 27, 2026 at 4:29 PM CEST, Chris Laplante via lists.yoctoproject.org wrote:
> From: Chris Laplante <chris.laplante@agilent.com>
>
> bb.fetch2 replaced bb.fetch back in 2012, and the compatibility shim of
> bb.fetch = bb.fetch2 has been in place ever since. There's no longer a
> good reason to keep the '2' suffix, so lets drop it.
>
> We also invert the bb.fetch = bb.fetch2 compatibility shim to now make
> bb.fetch2 = bb.fetch. We do this by creating a new lib/bb/fetch2.py,
> which lets us get rid of the ugly-ish shim in lib/bb/__init__.py.
> Finally, we add a deprecation warning for good measure.
>
> Signed-off-by: Chris Laplante <chris.laplante@agilent.com>
> ---
Hi Chris,
I suspect some renaming is missing on the oecore side. We have this
error on all builds:
Running '. ./init-build-env; bitbake world -k' with output to /srv/pokybuild/yocto-worker/qemux86-world-alt/build/build/command-1-build-targets.log in /srv/pokybuild/yocto-worker/qemux86-world-alt/build/build
ERROR: Execution of event handler 'check_sanity_eventhandler' failed
Traceback (most recent call last):
File "/srv/pokybuild/yocto-worker/qemux86-world-alt/build/layers/openembedded-core/meta/classes-global/sanity.bbclass", line 169, in check_sanity_eventhandler
oe.sanity.check_sanity(sanity_data)
~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^
File "/srv/pokybuild/yocto-worker/qemux86-world-alt/build/layers/openembedded-core/meta/lib/oe/sanity.py", line 1007, in check_sanity
check_sanity_everybuild(status, sanity_data)
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
File "/srv/pokybuild/yocto-worker/qemux86-world-alt/build/layers/openembedded-core/meta/lib/oe/sanity.py", line 890, in check_sanity_everybuild
decoded = bb.fetch2.decodeurl(pattern)
^^^^^^^^^
AttributeError: module 'bb' has no attribute 'fetch2'. Did you mean: 'fetch'?
https://autobuilder.yoctoproject.org/valkyrie/#/builders/17/builds/4359
Can you have a look at the issue?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-08-28 5:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 14:29 [PATCH 1/4] lib: rename fetch2 as fetch; invert compat shim to make bb.fetch2 = bb.fetch chris.laplante
2026-08-27 14:29 ` [PATCH 2/4] bin, lib, conf: use bb.fetch instead of bb.fetch2 chris.laplante
2026-08-27 14:29 ` [PATCH 3/4] tests: add fetch_import tests to test bb.fetch2 => bb.fetch migration chris.laplante
2026-08-27 14:29 ` [PATCH 4/4] doc: update manual to reflect " chris.laplante
2026-08-28 5:51 ` Mathieu Dubois-Briand [this message]
2026-08-28 12:00 ` [bitbake-devel] [docs] [PATCH 1/4] lib: rename fetch2 as fetch; invert compat shim to make bb.fetch2 = bb.fetch Peter Kjellerstedt
2026-08-28 14:37 ` chris.laplante
2026-08-28 14:45 ` chris.laplante
2026-08-28 14:59 ` chris.laplante
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=DL0CCF115T08.227YUHOXXHLP3@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=chris.laplante@agilent.com \
--cc=docs@lists.yoctoproject.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