[OE-core] Package Manager Conflicts

[Randy MacLeod]

On 2017-06-26 06:03 PM, Andrew Sampson wrote:
> I'm attempting to setup a package feed for a board which I don't have 
> the ability to flash nor do I have access to the original image that is 
> on it.

Do you know the image was built?
Do you have access to the build scripts that were used to build the 
image? Without such information, it could be hard to produce
identically configured/tuned builds...

> 
> The image on the board comes with Smart installed.
> 
> I build an image using the information in this guide: 
> https://www.openembedded.org/wiki/OE-Core_Standalone_Setup
> 
> 
> and add my dependencies before doing: bitbake core-image-minimal and 
> bitbake package-feed
> 
> However when I attempt to install a package via smart I get this error
> 
> Committing transaction...
> error: update-alternatives-opkg-0.3.4+git0+1a708fd73d-r0 conflicts with 
> update-alternatives-cworth
> 
> I can't find any information referencing this issue, is there a way I 
> can completely strip opkg from the oe-core layer or a solution to this 
> problem?
> 
> 

In your conf/local.conf file you should have lines like:
#
# Package Management configuration
#
# This variable lists which packaging formats to enable. Multiple 
package back-ends
# can be enabled at once and the first item listed in the variable will 
be used
# to generate the root filesystems.
# Options are:
#  - 'package_deb' for debian style deb files
#  - 'package_ipk' for ipk files are used by opkg (a debian style 
embedded package manager)
#  - 'package_rpm' for rpm style packages
# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"
# We default to ipk:
PACKAGE_CLASSES ?= "package_ipk"


Hopefully swapping "package_ipk" for "package_rpm" will work for you.
'deb' is not well supported in the OE world.

Is there an rpm binary on your target?



-- 
# Randy MacLeod. SMTS, Linux, Wind River
Direct: 613.963.1350 | 350 Terry Fox Drive, Suite 200, Ottawa, ON, 
Canada, K2K 2W5