Bug 6634 - Bitbake does not give any hint how to resolve conflicting packagegroups
Summary: Bitbake does not give any hint how to resolve conflicting packagegroups
Status: RESOLVED WONTFIX
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.7
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-08-18 15:00 UTC by Laszlo Papp
Modified: 2014-09-23 21:40 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 Laszlo Papp 2014-08-18 15:00:37 UTC
This is all the error I got:

ERROR: Recipe packagegroup-foo is trying to create package packagegroup-foo-dbg which was already written by recipe packagegroup-foo-dbg. This will cause corruption, please resolve this and only provide the package from one recipe or the other or only build one of the recipes.
ERROR: Function failed: read_subpackage_metadata

All, I can see is that the dbg and non-dbg packagegroups for the debug and non-debug images are conflicting. Well, of course, they do, since they use different debug/release configuration for the same software. This is nothing unusual so far.

However, Yocto/bitbake does not really tell me what exactly I could do other than wiping the build folder away. That is what I am currently doing, but it is more than disappointing cause it will take me 1-2 hours to get to the same stage again.

At the very least, it could provide more information what exactly to do:

* clean up these and those packages

or

* Use this force option to override the existing packagegroup build with the currently required one.

This is all happening when trying to generate the SDK.
Comment 1 Richard Purdie 2014-09-23 21:40:16 UTC
This is really not something we can do. We don't know why these two packages exist, or what in any general case the fix might be. There is simply no way to tell the user what to do since it doesn't know, we just know there is a problem and report it as such.