When install gcc cross canadian, it will report Downloading http://llu-piketon.sh.intel.com/ipk_sdk/i586-i586-canadian/gcc-cross-canadian_4.5.1-r0_i586-i586-canadian.ipk. Installing libmpfr4 (3.0.0-r0) to root... Downloading http://llu-piketon.sh.intel.com/ipk_sdk/i586-nativesdk/libmpfr4_3.0.0-r0_i586-nativesdk.ipk. Collected errors: * check_data_file_clashes: Package libmpfr4 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 gcc-cross-canadian.
Liping, could you please add reproduce step?
/usr/share/info/dir is a collective file to include the entry points of all info pages i.e., when installing, /usr/share/info/dir should always be updated instead of overridden, such overriding generates errors like above. We should have a postinst in every -doc package to invoke something like install-info to update the dir file.
One interesting thing is that, if I don't use sudo to install the opkg package to the /opt/poky but to some normal folders such as /home/lke/opt/poky, I can install. Seems the problem could be avoided. Yet I am not clear why this happens. If you want to repeat the process, please download the suitable conf file from http://llu-piketon.sh.intel.com, and run below command with your host opkg: opkg-cl -f /home/lke/opkg-sdk-i586.conf -o /home/lke/Downloads/testfolder update opkg-cl -f /home/lke/opkg-sdk-i586.conf -o /home/lke/Downloads/testfolder install gcc-cross-canadian Thanks & Regards, criping
Interestingly, dpkg doesn't use -postinst for this specific requirement, the mechanism is called `trigger', it triggers on every /usr/share/info update, so no postinst is needed. Seems opkg doesn't have this mechanism, not sure about rpm.
*** Bug 546 has been marked as a duplicate of this bug. ***
Liping, Do we still see this problem?
I will re-verify it this week. I guess no one has fixed it. I still use -f now
I did not meet this problem any more. I will close this bug.