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; "
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).
license manifet and package manifest are generated from license_image.bbclass
Bumping as nobody else is affected it seems
Build move to 5.0 -- ../Randy
Bulk move of 5.0 medium importance issues to 5.99. Move to 5.1 if you want to actively work on an issue.
Move to 5.99 since no one is actively working on this issue. Move to 5.x if you start on a task, please.