Bug 10258 - bitbake package-index does not work with 'rpm'
Summary: bitbake package-index does not work with 'rpm'
Status: VERIFIED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: deployment (show other bugs)
Version: 2.2
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.3 M4
Assignee: Hongxu Jia
QA Contact: David Lopez Barriba
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-09-12 14:08 UTC by Mark Hatle
Modified: 2016-12-01 19:57 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
log.do_package_index (832 bytes, text/plain)
2016-12-01 19:56 UTC, David Lopez Barriba 		no flags Details
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 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