Bug 10258

Summary: bitbake package-index does not work with 'rpm'
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Mark Hatle <mark.hatle>
Component: deploymentAssignee: Hongxu Jia <hongxu.jia>
Status: VERIFIED FIXED QA Contact: David Lopez Barriba <davidx.lopez.barriba>
Severity: normal    
Priority: Medium+ CC: bluelightning, hongxu.jia, jose.perez.carranza, stephano
Version: 2.2   
Target Milestone: 2.3 M4   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
log.do_package_index none

Description Mark Hatle 2016-09-12 14:08:57 UTC 
If you configure a system using the default package_rpm format.  There is currently no way to generate an index for remote deployments (updates).

The 'bitbake package-index' command 'succeeds' but if you look at the logs:
DEBUG: Executing python function do_package_index
NOTE: There are no packages in /.../tmp-glibc/deploy/rpm
DEBUG: Python function do_package_index finished

The package-index does not appear to be processing the 'arch' list (ALL_MULTILIB_PACKAGE_ARCHS).  This may be related to recent changes of only constructing the index in the WORKDIR, while the 'package-index' should be constructing it in the deploy directory.
Comment 2 David Lopez Barriba 2016-12-01 19:56:33 UTC 
Created attachment 3553 [details]
log.do_package_index

log.do_package_index
Comment 3 David Lopez Barriba 2016-12-01 19:57:32 UTC 
Verified in commit 6c9f6b5f70ab3ee194b2c2c6f3bd462c994848fa
works OK