Bug 12933

Summary: python-sqlite3 is packaged incorrectly
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Jeroen Hofstee <jhofstee>
Component: devtools / tool chainAssignee: Ross Burton <ross.burton>
Status: RESOLVED FIXED QA Contact:
Severity: major    
Priority: Medium+ CC: meta.mr.watcher, meta.watcher, ross.burton
Version: 2.6   
Target Milestone: 2.6 M4   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Jeroen Hofstee 2018-09-25 19:42:42 UTC
On current master e3f5ceec690379 "build-appliance-image: Update to master head revision" /usr/lib/python2.7/sqlite3 ends up in the python-misc package and not
in python-sqlite3. Hence when only installing python-sqlite3, import sqlite3 throws an "ImportError: No module named sqlite3" exception. Importing _sqlite (with an underscore) does work.

get_module_deps2.py does see that python2.7/sqlite3/__init__.pyc is needed and replaces it with ${libdir}/python2.7/sqlite3, but it doesn't get written to the manifest file (also not after regenerating it) and hence ends up in misc.

Simply adding "${libdir}/python2.7/sqlite3" seems to manifest file seems to work, also after regeneration, but that includes then sqlite3/test as well, which doesn't seem to be the intend.

Setting severity to major, since I assume you want this fixed in a release. Feel free to lower it. There is a easy workaround, just install python-misc as well.
Comment 1 Ross Burton 2018-09-26 11:55:44 UTC
Patch on the list. The test thing is already resolved.
Comment 2 Ross Burton 2018-10-01 15:15:41 UTC
Fixed as of oe-core 9c2b1a0bfc8783052b5dda344cc334b9c13736f5.