13491 2019-08-23 01:44:22 +0000 perllocal.pod clash from multiple different packages 2019-10-17 14:53:29 +0000 1 1 7 Build System, Metadata & Runtime OE-Core configuration unspecified x86 Multiple RESOLVED FIXED Medium+ normal 2.8 M4 1 jonathan.yong tim.orling randy.macleod ross.burton --- --- Yes (doc changes required) oldest_to_newest 84738 0 jonathan.yong 2019-08-23 01:44:22 +0000 Background: perl modules when installed can produce a perllocal.pod file for documenting a list of locally installed perl modules. This can conflict if multiple packages generate the file. When building lmsensors, it fails with: mc:x86:lmsensors-3.4.0-r0 do_prepare_recipe_sysroot: The file /usr/lib64/perl5/5.28.1/x86_64-linux/perllocal.pod is installed by both apparmor and rrdtool, aborting Should this file be removed automatically? I am using this bbclass as a workaround: remove_perllocal(){ if [ -d "${D}/${libdir}/perl5" ]; then find "${D}/${libdir}/perl5" -type f -name perllocal.pod -delete fi } do_install[postfuncs] += "remove_perllocal" 85193 1 ross.burton 2019-10-03 15:13:32 +0000 If something is using cpan.bbclass it won't install the fiel, so any recipe that ships it is doing so explicitly for some reason. I believe we should add a QA test for this, but not wipe it out globally. 85205 2 ross.burton 2019-10-04 00:22:29 +0000 Patch for the QA test on the list now. 85357 3 tim.orling 2019-10-17 14:35:34 +0000 QA sanity test was merged in Zeus: a5a5708dbbb534f6624fafe9e78f96de25c10dea 85367 4 tim.orling 2019-10-17 14:53:29 +0000 Individual recipes (from layers that are not triaged by the YP Bug Triage team) may still need to be corrected to not install perllocal.pod. If so, either send a patch to the proper mailing list to fix the recipe in question or send an email to the proper list highlighting the need to fix perllocal.pod QA test.