Bug 13491 - perllocal.pod clash from multiple different packages
Summary: perllocal.pod clash from multiple different packages
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: configuration (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.8 M4
Assignee: Tim Orling
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2019-08-23 01:44 UTC by jonathan.yong
Modified: 2019-10-17 14:53 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jonathan.yong 2019-08-23 01:44:22 UTC
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"
Comment 1 Ross Burton 2019-10-03 15:13:32 UTC
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.
Comment 2 Ross Burton 2019-10-04 00:22:29 UTC
Patch for the QA test on the list now.
Comment 3 Tim Orling 2019-10-17 14:35:34 UTC
QA sanity test was merged in Zeus: a5a5708dbbb534f6624fafe9e78f96de25c10dea
Comment 4 Tim Orling 2019-10-17 14:53:29 UTC
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.