All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: poky@yoctoproject.org
Subject: Re: file clashes
Date: Fri, 11 Mar 2011 16:13:52 -0700	[thread overview]
Message-ID: <4D7AACB0.3020005@mlbassoc.com> (raw)
In-Reply-To: <4D7A5D7C.6040608@mlbassoc.com>

On 03/11/2011 10:35 AM, Gary Thomas wrote:
> 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

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?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


      reply	other threads:[~2011-03-11 23:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-11 17:35 file clashes Gary Thomas
2011-03-11 23:13 ` Gary Thomas [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D7AACB0.3020005@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=poky@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.