file clashes
I started with my sato-like image which includes gnome-keyring.
Then I added another application which wanted to use libgnome-keyring.
This caused this clash at install time (I'm still using opkg):
* check_data_file_clashes: Package libgnome-keyring0 wants to install file /usr/lib/libgnome-keyring.so.0.1.1 But that file is already provided by package * gnome-keyring
* check_data_file_clashes: Package libgnome-keyring0 wants to install file /usr/lib/libgnome-keyring.so.0 But that file is already provided by package * gnome-keyring
Does this happen because of the recipe/versions?
meta/recipes-gnome/gnome/libgnome-keyring_2.32.0.bb meta/recipes-gnome/gnome/gnome-keyring_2.32.1.bb
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 11 lines · Gary Thomas
I started with my sato-like image which includes gnome-keyring.
Then I added another application which wanted to use libgnome-keyring.
This caused this clash at install time (I'm still using opkg):
*check_data_file_clashes: Package libgnome-keyring0 wants to install file/usr/lib/libgnome-keyring.so.0.1.1But that file is already provided by package * gnome-keyring
*check_data_file_clashes: Package libgnome-keyring0 wants to install file/usr/lib/libgnome-keyring.so.0But that file is already provided by package * gnome-keyringDoes this happen because of the recipe/versions? meta/recipes-gnome/gnome/libgnome-keyring_2.32.0.bb meta/recipes-gnome/gnome/gnome-keyring_2.32.1.bb
This turned out to be my problem - I had pinned gnome-keyring to 2.28.0 which caused the clash. Removing that pin and all is well.
Perhaps old recipes like that should be removed, certainly if they cause problems?
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------