Bug 12279

Summary: enhance manifest not found warning
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Robert Yang <liezhi.yang>
Component: coreAssignee: New Comer Bugs <newcomer>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: Medium+ CC: liezhi.yang, meta.mr.watcher, meta.watcher, mikejongen12, randy.macleod, tgamblin
Version: 2.5   
Target Milestone: 5.99   
Hardware: x86   
OS: Multiple   
Whiteboard: NEWCOMER
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Robert Yang 2017-10-26 06:39:08 UTC
The warning when manifest not found:
WARNING: lib32-wrlinux-image-glibc-small-1.0-r1 do_prepare_recipe_sysroot: Manifest /path/to/tmp/sstate-control/manifest-allarch-lib32-qemuwrapper-cross.populate_sysroot not found?
    
The message wasn't clear enough, it searched a few manifests, but only reported the last one, which confused user.

We can enhance it to:

WARNING: lib32-wrlinux-image-glibc-small-1.0-r1 do_rootfs: Manifest not found, searched manifests:
/path/to/tmp/sstate-control/manifest-qemux86_64-lib32-qemuwrapper-cross.populate_sysroot
/path/to/tmp/sstate-control/manifest-core2-64-lib32-qemuwrapper-cross.populate_sysroot
/path/to/tmp/sstate-control/manifest-x86_64-lib32-qemuwrapper-cross.populate_sysroot
/path/to/tmp/sstate-control/manifest-allarch-lib32-qemuwrapper-cross.populate_sysroot
Comment 1 Randy MacLeod 2022-06-16 15:22:38 UTC
From sysroot staging code.
Comment 2 Randy MacLeod 2023-07-26 21:29:36 UTC
Bulk move to 4.3 M3.
Comment 3 Trevor Gamblin 2023-09-14 16:55:19 UTC
Moved to M4.
Comment 4 Randy MacLeod 2024-01-25 14:32:32 UTC
Robert had this bug in in progress-review. I wonder if it actually was fixed...
Move from 5.0 M2 to M4
Comment 5 Randy MacLeod 2024-04-25 01:08:00 UTC
Move to 5.99 since no one is actively working on this issue.
Comment 6 Mike Jongen 2026-01-23 15:43:19 UTC
hello,
I checked if I could reproduce the error, and it seems like the issue is already fixed.
This is the error I got:

ERROR: qemuwrapper-cross-1.0-r0 do_prepare_recipe_sysroot: The sstate manifest for task 'qemu-native:populate_sysroot' (multilib variant '') could not be found.
The pkgarchs considered were: x86_64, x86_64_ubuntu-24.04.
But none of these manifests exists:
    /path/to/tmp/sstate-control/manifest-x86_64-qemu-native.populate_sysroot
    /path/to/tmp/sstate-control/manifest-x86_64_ubuntu-24.04-qemu-native.populate_sysroot
ERROR: Logfile of failure stored in: /path/to/tmp/work/cortexa72-poky-linux/qemuwrapper-cross/1.0/temp/log.do_prepare_recipe_sysroot.91564
ERROR: Task (/path/to/poky/meta/recipes-devtools/qemu/qemuwrapper-cross_1.0.bb:do_prepare_recipe_sysroot) failed with exit code '1'

Is this enough to close this bug?

Steps to reproduce
1. select a package with a do_prepare_recipe_sysroot task, which depends on a do_populate_sysroot task (I choose qemuwrapper-cross.do_prepare_recipre_sysroot and qemu-native.do_populate_sysroot)
2. clean sstate of both packages:
`bitbake -c cleansstate qemuwrapper-cross`
`bitbake -c cleansstate qemu-native`
3. run do populate_sysroot task:
`bitbake -c do_populate_sysroot qemu-native`
4. remove manifest*.populate_sysroot file of the package you just made
5. run do prepare_recipe_sysroot task
`bitbake -c do_prepare_recipe_sysroot qemuwrapper-cross`
You should now get the error
Comment 7 Robert Yang 2026-01-26 07:12:28 UTC
@Mike, yes, that's enough to close it, thanks for the update.