Bug 12834

Summary: can not install empty package anymore on rootfs with sumo
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Robert Berger <pokylinux>
Component: deploymentAssignee: Robert Berger <pokylinux>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: Medium CC: richard.purdie, ross.burton
Version: 2.5.1   
Target Milestone: 2.5.3   
Hardware: All   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know
Attachments:
Description Flags
sample which shows problem none

Description Robert Berger 2018-06-30 18:16:12 UTC
Created attachment 4337 [details]
sample which shows problem

Looks like with Sumo I can not install an empty package anymore on the rootfs, which makes it hard to install it on the SDK;)

I have a recipe which generates a .a file.

Please check testcase and error in attachment:

autotooled-lib-a
├── files
│   └── libhw-a-1.0.tar.gz
├── libhw-a_1.0.bb
└── readme.txt
Comment 1 Robert Berger 2018-06-30 20:09:56 UTC
Now it's getting spooky;)

If I do this 

IMAGE_INSTALL_append = " libhw-a"
SDKIMAGE_FEATURES_append = " dev-pkgs dbg-pkgs staticdev-pkgs"

I mean I add the line:

SDKIMAGE_FEATURES_append = " dev-pkgs dbg-pkgs staticdev-pkgs"

I can bake

bitbake core-inage-minimal 

without any problem and even see it installed:

bitbake -g core-image-minimal && cat pn-buildlist | grep -v -e '-native' | grep -v digraph | grep -v -e '-image' | awk '{print }' | sort | uniq

contains:

libhw-a
Comment 2 Richard Purdie 2018-12-20 16:14:07 UTC
Hi Robert,

Is this because we disabled static libraries in sumo? That would mean they don't get packaged, the package then becomes empty, empty packages don't get generated and hence you can't install it?
Comment 3 Stephen K Jolley 2018-12-20 16:16:03 UTC
See Richard's question
Comment 4 Robert Berger 2019-01-04 17:40:44 UTC
I did a talk at ELCE Yocto Dev day about this and similar issues (around static libs) and would say this is resolved now.
Comment 5 Robert Berger 2019-01-25 17:44:27 UTC
Yes it's about static (autotooled) libs disabled by default.
Comment 6 Ross Burton 2019-01-31 16:00:05 UTC
From comment #4 it seems as if this is actually fixed now, so I'm closing the bug.  If this is not the case please re-open the bug and explain clearly what the problem is: installing empty packages does work as that's what packagegroups are.