| Summary: | python3-build depends on python3-ensurepip but recipe doesn't exist | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | kwalsh1 |
| Component: | devtools / tool chain | Assignee: | Unassigned <unassigned> |
| Status: | RESOLVED NOTABUG | QA Contact: | |
| Severity: | normal | ||
| Priority: | Undecided | CC: | meta.mr.watcher, meta.watcher, ross.burton, tgamblin |
| Version: | unspecified | ||
| Target Milestone: | 0.0.0 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| URL: | https://git.yoctoproject.org/poky/tree/meta/recipes-devtools/python/python3-build_0.10.0.bb | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
kwalsh1
2023-06-20 15:50:38 UTC
python3-ensurepip is a split of the python3 standard library. If you add it to IMAGE_INSTALL:append or a recipe's RDEPENDS list, it should be installed in an image. It looks like it's already in the RDEPENDS list for python3-build and has been since April (see commit ff633ce7a7ffc0d39b86043caeb63a9ffcef99b8). Is your poky repo up to date? The python3-build recipe _RDEPENDS_ on python3-ensurepip, not DEPENDS. This means it wants a package called python3-ensurepip, not a recipe. As can be seen in the python3-manifest.json file, and verified with oe-pkgdata-util, python3-ensurepip is (as Trevor says) part of the python3 recipe: $ oe-pkgdata-util lookup-recipe python3-ensurepip python3 |