Bug 546 - libreadlines clash when installing gdb cross ipk
Summary: libreadlines clash when installing gdb cross ipk
Status: RESOLVED DUPLICATE of bug 547
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: 0.9
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.0 M1
Assignee: Saul Wold
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2010-11-25 00:12 UTC by liping Ke
Modified: 2010-12-21 06:07 UTC (History)
9 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description liping Ke 2010-11-25 00:12:32 UTC
When installing gdb-cross-canadian ipk, it will report:

Installing gdb-cross-canadian (7.2-r0) to root...
Downloading http://llu-piketon.sh.intel.com/ipk_sdk/i586-i586-canadian/gdb-cross-canadian_7.2-r0_i586-i586-canadian.ipk.
Installing libreadline6 (6.1-r0) to root...
Downloading http://llu-piketon.sh.intel.com/ipk_sdk/i586-nativesdk/libreadline6_6.1-r0_i586-nativesdk.ipk.
Collected errors:
 * check_data_file_clashes: Package libreadline6 wants to install file //opt/poky/sysroots/i586-pokysdk-linux/usr/share/info/dir
        But that file is already provided by package  * check_data_file_clashes: <no package>
Please move this file out of the way and try again.
 * opkg_install_cmd: Cannot install package gdb-cross-canadian.
Comment 1 Ke Yu 2010-11-25 01:04:52 UTC
Liping, could you provide the detailed reproduce steps, so that people can try to reproduce?
Comment 2 liping Ke 2010-11-25 01:45:54 UTC
Hi, Ke

We're using opkg command to do the thing. So we need a opkg configuration file. I will paste my opkg configuration file as well as the opkg command a little later.

Thanks & Regards,
criping
Comment 3 Qing He 2010-11-30 17:57:06 UTC
Since we probably need a general mechanism to handle /usr/share/info/dir update, mark the bug as duplicated with Bug 547

*** This bug has been marked as a duplicate of bug 547 ***