Bug 14821 - recipename function doesn't return recipe name for packages renamed with debian.bbclass
Summary: recipename function doesn't return recipe name for packages renamed with debi...
Status: ACCEPTED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: configuration (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 6.1
Assignee: Randy MacLeod
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2022-06-01 16:56 UTC by Pavel Zhukov
Modified: 2026-05-07 15:10 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pavel Zhukov 2022-06-01 16:56:39 UTC
if the package has been renamed to comply with debian naming rules (debian.bbclass has been inherited and package contains .so-files) then oe.packagedata.recipename function doesn't work properly and returns None for such packages.

Disabling debian.bbclass solves the problem and can be used as a workaround.

Simple reproducer would be:

# repro.bblass


python my_report () {

    from oe.rootfs import image_list_installed_packages
    from oe.packagedata import recipename, pkgmap

    pkgs = image_list_installed_packages(d)
    for pkg in pkgs:
        recipe = recipename(pkg, d)
        if recipe is None: bb.error("Whoops recipe of {} is None".format(pkg))
}

ROOTFS_POSTPROCESS_COMMAND += " my_report; "
Comment 1 Pavel Zhukov 2022-06-02 12:22:52 UTC
Another problem related to this bug is the fact that package name in package.manifest and package name in license.manifest are different.
package manifest has "debian" name in it (dbus-1 for example) while license manifest contains the original name (dbus).
Comment 2 Pavel Zhukov 2022-06-02 14:49:14 UTC
license manifet and package manifest are generated from license_image.bbclass
Comment 3 Pavel Zhukov 2022-11-01 19:21:41 UTC
Bumping as nobody else is affected it seems
Comment 4 Randy MacLeod 2023-10-30 15:37:25 UTC
Build move to 5.0 -- ../Randy
Comment 5 Randy MacLeod 2024-04-25 01:13:53 UTC
Bulk move of 5.0 medium importance issues to 5.99.
Move to 5.1 if you want to actively work on an issue.
Comment 6 Randy MacLeod 2024-04-25 01:23:10 UTC
Move to 5.99 since no one is actively working on this issue.
Move to 5.x if you start on a task, please.