Bug 16323 - AB-INT: git: error while loading shared libraries: libpython3.14.so.1.0
Summary: AB-INT: git: error while loading shared libraries: libpython3.14.so.1.0
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: Scripts and Tools (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 6.1
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard: AB-INT
Depends on:
Blocks:
 
Reported: 2026-06-18 10:34 UTC by Mathieu Dubois-Briand
Modified: 2026-07-23 15:58 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mathieu Dubois-Briand 2026-06-18 10:34:32 UTC
We got this failure, only once so far. Richard does not remember having any related change in his branch.

ERROR: babeltrace2-2.1.2-r0 do_unpack: Bitbake Fetcher Error: FetchError("Fetch command ['git', '-c', 'gc.autoDetach=false', '-c', 'core.pager=cat', '-c', 'safe.bareRepository=all', '-c', 'clone.defaultRemoteName=origin', 'rev-list', '-n', '1', 'd0e946a71faf5f0c2d7f1fb5b92a369983e9cf10'] failed with exit code 127, output:\npython3: error while loading shared libraries: libpython3.14.so.1.0: cannot open shared object file: No such file or directory\n", None)
Comment 1 Mathieu Dubois-Briand 2026-06-18 10:35:51 UTC
pkgman-non-rpm debian13-vk-2 master-next completed at 2026-06-18 04:55:20+00:00
https://autobuilder.yoctoproject.org/valkyrie/#/builders/67/builds/3977/steps/26/logs/stdio
Comment 2 Richard Purdie 2026-06-18 14:01:11 UTC
Some extra data. This build has the vardepsexclude patches in which means it rebuilds every time PACKAGE_CLASSES is changed.

That meant for this build, lots of sstate tasks were invalid and being replaced.

There were two tasks running at the time:

pokybuild@debian13-vk-2:~/yocto-worker/pkgman-non-rpm/build/build/tmp/work/cortexa57-poky-linux/babeltrace2/2.1.2/temp$ tail -n 4 log.task_order 
20260618-033948.185268 do_create_package_spdx (4020795): log.do_create_package_spdx.4020795
20260618-043242.937024 do_fetch (596760): log.do_fetch.596760
20260618-043243.278254 do_unpack (597065): log.do_unpack.597065
20260618-043243.294757 do_prepare_recipe_sysroot (597069): log.do_prepare_recipe_sysroot.597069

NOTE: python3 exists in sysroot, but is stale (python3.5aa073fd57c8f749a841396c1b5da03cbea6c1bfd33cf281366a6f32e5e2a26d vs. python3.caef672044878ee492a67390c83f8818dc20aa04f7143a53476e37e55f6469c3), removing.
NOTE: python3-native exists in sysroot, but is stale (python3-native.6363ac386d19013c4360e4df54382c1c8785b21476db12fc033716ae0466cf69 vs. python3-native.e99ddcbf0526f810136cf7cacc1d31009b37e69b803767e3e12a8858cade5556), removing

There is no mention or trace of git-replacement-native having been involved.

I'd therefore guess git from the host was finding libpython from the native sysroot and got upset when it was removed. Why it would do that...
Comment 3 Richard Purdie 2026-06-18 14:03:03 UTC
Although python on the host ($ python --version) is Python 3.13.5 so perhaps git used python from the sysroot while it was being removed?
Comment 4 Richard Purdie 2026-06-18 14:53:59 UTC
Bug triage noted we have an intercept script for git written in python3 which is why we would have triggered a python failure here.