Bug 14523 - oe-pkgdata-util list-pkg-files doesn't ignore target-sdk-provides-dummy.bb
Summary: oe-pkgdata-util list-pkg-files doesn't ignore target-sdk-provides-dummy.bb
Status: NEW
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: Scripts and Tools (show other bugs)
Version: 4.0
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 6.99
Assignee: Unassigned
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2021-08-23 14:31 UTC by Ross Burton
Modified: 2026-04-30 15:42 UTC (History)
4 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ross Burton 2021-08-23 14:31:45 UTC 
From an empty tmpdir, if I bitbake bash:

$ oe-pkgdata-util list-pkg-files bash
bash:
	/bin/bash.bash

That makes sense.

But if I build a SDK, or more specifically target-sdk-provides-dummy:

$ bitbake target-sdk-provides-dummy
$ oe-pkgdata-util list-pkg-files bash
bash:
bash is in the RPROVIDES of target-sdk-provides-dummy:

That is not useful.  Somehow, it should be ignoring that recipe.
Comment 1 Randy MacLeod 2021-08-26 14:47:18 UTC 
For Kiran in 2 weeks.
Comment 2 Randy MacLeod 2023-07-26 21:22:07 UTC 
Bulk move of 64 bugs to 4.3 M3 after a quick review.
If a bug is actually fixed, please add a commit link and resolve it.
-- Randy for YP bug team.
Comment 3 Trevor Gamblin 2023-09-14 16:44:48 UTC 
Moved to M4.
Comment 4 Randy MacLeod 2023-10-30 15:29:14 UTC 
Bulk move to 5.0 M1. -- Randy
Comment 5 Randy MacLeod 2023-12-21 23:28:31 UTC 
Bulk move of 52 5.0-M1 bugs to M2.
Comment 6 Randy MacLeod 2024-01-25 14:28:52 UTC 
Bulk move of bugs owned by "unassigned" from 5.0-M2 to 5.0-M3.
Comment 7 Randy MacLeod 2024-02-22 19:53:25 UTC 
Bulk move of bugs from 5.0-M3 to 5.99.
The bugs in this list are all unassigned and are ones that I consider to be nice to do some time but not essential track from milestone to milestone in 5.0 or 5.1. We agreed on this bug handling approach in the YP bug review on Feb 22, 2024.

If you disagree, please move back to a 5.[012...]-M* milestone.