Bug 12962

Summary: [meta-mingw] update-alternative warnings
Product: [Build System, Metadata & Runtime] Other YP Layers Reporter: Ross Burton <ross.burton>
Component: meta-mingwAssignee: Joshua Watt <JPEWhacker>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium CC: poky.bs.watcher, poky.watcher, randy.macleod
Version: unspecified   
Target Milestone: 2.8 M1   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Ross Burton 2018-10-16 13:39:09 UTC
WARNING: nativesdk-libiconv-1.14-r1 do_patch: 
WARNING: nativesdk-bzip2-1.0.6-r5 do_package: bzip2: alternative target (/opt/poky/2.5+snapshot/sysroots/i686-pokysdk-mingw32/usr/bin/bunzip2 or /opt/poky/2.5+snapshot/sysroots/i686-pokysdk-mingw32/usr/bin/bunzip2.bzip2) does not exist, skipping...
WARNING: nativesdk-bzip2-1.0.6-r5 do_package: bzip2: alternative target (/opt/poky/2.5+snapshot/sysroots/i686-pokysdk-mingw32/usr/bin/bzcat or /opt/poky/2.5+snapshot/sysroots/i686-pokysdk-mingw32/usr/bin/bzcat.bzip2) does not exist, skipping...
WARNING: nativesdk-bzip2-1.0.6-r5 do_package: bzip2: NOT adding alternative provide /opt/poky/2.5+snapshot/sysroots/i686-pokysdk-mingw32/usr/bin/bunzip2: /opt/poky/2.5+snapshot/sysroots/i686-pokysdk-mingw32/usr/bin/bunzip2.bzip2 does not exist
WARNING: nativesdk-bzip2-1.0.6-r5 do_package: bzip2: NOT adding alternative provide /opt/poky/2.5+snapshot/sysroots/i686-pokysdk-mingw32/usr/bin/bzcat: /opt/poky/2.5+snapshot/sysroots/i686-pokysdk-mingw32/usr/bin/bzcat.bzip2 does not exist
WARNING: nativesdk-bzip2-1.0.6-r5 do_package: bzip2: alt_link == alt_target: /opt/poky/2.5+snapshot/sysroots/i686-pokysdk-mingw32/usr/bin/bunzip2 == /opt/poky/2.5+snapshot/sysroots/i686-pokysdk-mingw32/usr/bin/bunzip2
WARNING: nativesdk-bzip2-1.0.6-r5 do_package: bzip2: alt_link == alt_target: /opt/poky/2.5+snapshot/sysroots/i686-pokysdk-mingw32/usr/bin/bzcat == /opt/poky/2.5+snapshot/sysroots/i686-pokysdk-mingw32/usr/bin/bzcat
WARNING: nativesdk-diffutils-3.6-r0 do_package: diffutils: alternative target (/opt/poky/2.5+snapshot/sysroots/i686-pokysdk-mingw32/usr/bin/diff or /opt/poky/2.5+snapshot/sysroots/i686-pokysdk-mingw32/usr/bin/diff.diffutils) does not exist, skipping...
WARNING: nativesdk-diffutils-3.6-r0 do_package: diffutils: alternative target (/opt/poky/2.5+snapshot/sysroots/i686-pokysdk-mingw32/usr/bin/cmp or /opt/poky/2.5+snapshot/sysroots/i686-pokysdk-mingw32/usr/bin/cmp.diffutils) does not exist, skipping...
WARNING: nativesdk-diffutils-3.6-r0 do_package: diffutils: NOT adding alternative provide /opt/poky/2.5+snapshot/sysroots/i686-pokysdk-mingw32/usr/bin/diff: /opt/poky/2.5+snapshot/sysroots/i686-pokysdk-mingw32/usr/bin/diff.diffutils does not exist
WARNING: nativesdk-diffutils-3.6-r0 do_package: diffutils: NOT adding alternative provide /opt/poky/2.5+snapshot/sysroots/i686-pokysdk-mingw32/usr/bin/cmp: /opt/poky/2.5+snapshot/sysroots/i686-pokysdk-mingw32/usr/bin/cmp.diffutils does not exist
WARNING: nativesdk-diffutils-3.6-r0 do_package: diffutils: alt_link == alt_target: /opt/poky/2.5+snapshot/sysroots/i686-pokysdk-mingw32/usr/bin/diff == /opt/poky/2.5+snapshot/sysroots/i686-pokysdk-mingw32/usr/bin/diff
WARNING: nativesdk-diffutils-3.6-r0 do_package: diffutils: alt_link == alt_target: /opt/poky/2.5+snapshot/sysroots/i686-pokysdk-mingw32/usr/bin/cmp == /opt/poky/2.5+snapshot/sysroots/i686-pokysdk-mingw32/usr/bin/cmp
WARNING: core-image-minimal-1.0-r0 do_populate_sdk: The postinstall intercept hook 'update_gio_module_cache-nativesdk' failed, details in /home/pokybuild/yocto-worker/nightly-qa-extras/build/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/temp/log.do_populate_sdk
Comment 1 Joshua Watt 2019-05-10 23:03:08 UTC
There are actually 2 different warnings. The first is the alternatives warning. There were several of these showing up in multiple recipes, and have been since fixed. The second warning is related to the postinstall intercept hook for update_gio_module_cache-nativesdk. This one is more involved to fix since it is trying to run the hook in qemu, but also far less annoying, since it only appears once per build.
Comment 2 Joshua Watt 2019-07-18 14:54:27 UTC
These appear to have been fixed since they are no longer appearing in the autobuilder warning output.