14821 2022-06-01 16:56:39 +0000 recipename function doesn't return recipe name for packages renamed with debian.bbclass 2026-05-07 15:10:33 +0000 1 1 7 Build System, Metadata & Runtime OE-Core configuration unspecified x86 Multiple ACCEPTED Medium normal 6.1 1 pavel randy.macleod pavel randy.macleod --- --- Don't know oldest_to_newest 93361 0 pavel 2022-06-01 16:56:39 +0000 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; " 93366 1 pavel 2022-06-02 12:22:52 +0000 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). 93373 2 pavel 2022-06-02 14:49:14 +0000 license manifet and package manifest are generated from license_image.bbclass 94324 3 pavel 2022-11-01 19:21:41 +0000 Bumping as nobody else is affected it seems 97109 4 randy.macleod 2023-10-30 15:37:25 +0000 Build move to 5.0 -- ../Randy 98824 5 randy.macleod 2024-04-25 01:13:53 +0000 Bulk move of 5.0 medium importance issues to 5.99. Move to 5.1 if you want to actively work on an issue. 98853 6 randy.macleod 2024-04-25 01:23:10 +0000 Move to 5.99 since no one is actively working on this issue. Move to 5.x if you start on a task, please.