Bug 12545

Summary: [2.5 M2 RC1] SDK runqemu failed with python import logging
Product: [Build System, Metadata & Runtime] OE-Core Reporter: yeoh ee peng <ee.peng.yeoh>
Component: devtools / tool chainAssignee: Alexander Kanavin <alex.kanavin>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Undecided CC: meta.mr.watcher, meta.watcher, randy.macleod, richard.purdie, ross.burton, stephano
Version: 2.5   
Target Milestone: 2.1.4   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description yeoh ee peng 2018-02-13 03:01:57 UTC
Download toolchain:
https://autobuilder.yocto.io/pub/releases/yocto-2.5_M2.rc1/toolchain/x86_64/poky-glibc-x86_64-core-image-sato-i586-toolchain-2.4%2Bsnapshot.sh

Install toolchain and execute runqemu on core-image-sato-sdk-qemux86.qemuboot.conf.

Error:
yeoh@eyeoh-desktop:~/yp_images/qa_2.5_m2_rc1/qemux86$ runqemu core-image-sato-sdk-qemux86.qemuboot.conf
Traceback (most recent call last):
  File "/opt/poky/new_2.5_m2_rc1/sysroots/x86_64-pokysdk-linux/usr/bin/runqemu", line 23, in <module>
    import logging
ImportError: No module named 'logging'
Comment 1 Ross Burton 2018-02-15 15:54:02 UTC
Two theories:

1) This is running a Python binary that we ship in the SDK, and the recent manifest changes have broken what packages get installed.

2) The host is Debian/Ubuntu and only has python3-minimal installed.  On my Debian box libpython3.5-minimal ships logging, but maybe other releases didn't.
Comment 2 Alexander Kanavin 2018-02-15 16:23:22 UTC
I can confirm that 1) is correct:

ak@kanavin-desktop:/opt/poky/2.4+snapshot$ /opt/poky/2.4+snapshot/sysroots/x86_64-pokysdk-linux/usr/bin/python3
Python 3.5.3 (default, Jan 30 2018, 15:37:04) 
[GCC 7.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import logging
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: No module named 'logging'