Bug 5666 - opkg doesn't use run-postinsts
Summary: opkg doesn't use run-postinsts
Status: VERIFIED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: deployment (show other bugs)
Version: 1.5
Hardware: All Multiple
: Medium+ enhancement
Target Milestone: 1.6
Assignee: Laurentiu Palcu
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-12-13 17:40 UTC by Ross Burton
Modified: 2014-04-07 13:52 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ross Burton 2013-12-13 17:40:30 UTC
run-postinsts isn't used in the case where opkg is the package manager and the package manager is to be installed on the host.

Given that this is introducing a different codepath when dpkg/rpm/opkg-without-package-manager all use run-postinsts, we should evaluate removing the first-boot-postinstall code from opkg.
Comment 2 Alexandru Palalau 2014-03-18 13:41:31 UTC
It seems that package-management is not present in IMAGE_FEATURES when building postinstalls.

Also this is related to https://bugzilla.yoctoproject.org/show_bug.cgi?id=5972
Comment 3 Laurentiu Palcu 2014-03-18 16:06:59 UTC
I was testing IMAGE_FEATURES in run-postinsts recipe which is not quite right... All my tests were done with core-image-minimal which was hiding the problem because I was adding package-management to IMAGE_FEATURES in local.conf and was available to run-postinsts during compilation.

I have a fix already in tests.
Comment 4 Laurentiu Palcu 2014-03-31 07:12:48 UTC
Fixed the old solution and created a more generic run-postinsts script:
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=cbefaa3e3160aed390722b301e909f72b22dbbb8
Comment 5 Alexandru Palalau 2014-04-07 13:52:23 UTC
Verified on master branch.
Commit ID:bb66113bde5361b869dce2bdaece5b938f077ea8