Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH V3 1/1] gconf: fix multilib conflict - org.gnome.GConf.service
Date: Wed, 22 Oct 2014 18:58:41 +0800	[thread overview]
Message-ID: <54478DE1.9080202@windriver.com> (raw)
In-Reply-To: <CAJTo0LZKKpiceby03E=fD6yqpxY4RTBXYKiCfqLgRj6CU4deiw@mail.gmail.com>

On 10/22/14, 6:07 PM, Burton, Ross wrote:
> On 22 October 2014 08:09, Chong Lu <Chong.Lu@windriver.com> wrote:
>> The gconfd-2 will be called in org.gnome.GConf.service file and the path of
>> gconfd-2 is ${libexecdir}, this will get following error when multilib exported
>> in the sdk:
>> error: file /usr/share/dbus-1/services/org.gnome.GConf.service from install
>> of gconf-3.2.6-r0.0.lib32_x86 conflicts with file from package
>> gconf-3.2.6-r0.0.x86_64
>
> I'm clearly not understanding how our multilib implementation works,
> but you don't need many copies of the main gconf package, just one in
> the preferred configuration. What is causing multiple copies of gconf
> to be installed?

Installing both the lib32 and "regular" version of gconf attempts to install the 
file "/usr/share/dbus-1/services/org.gnome.GConf.service" twice.  (This is 
normally acceptable, as long as the -contents- of the file are identical.)  For 
whatever reason the contents are different, and the usual way to fix this is to 
provide a unique file that both versions can include.

This way only one version will be installed, but yet the other service elements 
will be properly duplicated.

I'd like a bit more information in the commit message indicating what the 
conflict actually was between both files (since I believe the service file is 
textual so a diff is easy to include).

--Mark

> Ross
>



  reply	other threads:[~2014-10-22 10:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22  7:09 [PATCH V3 0/1] gconf: fix multilib conflict - org.gnome.GConf.service Chong Lu
2014-10-22  7:09 ` [PATCH V3 1/1] " Chong Lu
2014-10-22 10:07   ` Burton, Ross
2014-10-22 10:58     ` Mark Hatle [this message]
2014-10-22 11:04       ` Burton, Ross
2014-10-24  2:26     ` Chong Lu
2014-10-26 20:58       ` Burton, Ross
2014-10-24  6:10   ` Koen Kooi
2014-10-24  6:16     ` Chong Lu
2014-10-24  7:01       ` Anders Darander

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=54478DE1.9080202@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox