Bug 8837

Summary: Cannot load just-installed kernel module during opkg configure because depmod call is intercepted and deferred
Product: [Yocto Project Subprojects] opkg Reporter: Will Page <will.page>
Component: opkgAssignee: Haris Okanovic <haris.okanovic>
Status: RESOLVED FIXED QA Contact:
Severity: major    
Priority: Undecided    
Version: 0.3.2   
Target Milestone: ---   
Hardware: All   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Yes (doc changes required)

Description Will Page 2015-12-17 22:03:51 UTC 
An opkg installs a kernel module, then postinst calls "depmod -a".  The opkg intercept causes the depmod invocation to be deferred until later.  Meanwhile, whether in this postinst or in a later one, attempts to load/use that kernel module fail because depmod hasn't run yet.

Hypothetically, the same issue could occur with the ldconfig intercept.  For example, if a package installs a library, then a later package wants to start a service that depends on that library.  The service start request will occur immediately, meanwhile the ldconfig call won't happen until much later.
Comment 1 Alejandro del Castillo 2015-12-18 16:37:03 UTC 
opkg should have a config option to disable intercepts, for cases like this one.
Comment 2 Haris Okanovic 2016-01-29 19:30:50 UTC 
Added intercepts_dir option to opkg.conf (commit 0991c27b), which can be used to disable postinst intercepts by setting to /dev/null.