From: Martin Jansa <martin.jansa@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH V3 0/2] BlueZ 5.3 new package
Date: Mon, 25 Mar 2013 18:03:46 +0100 [thread overview]
Message-ID: <20130325170346.GD7539@jama> (raw)
In-Reply-To: <CAJTo0Lb9e4j-O2R5_wvkH=2APWYMZDnFw0pxj_YheeHZfUBdig@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 661 bytes --]
On Mon, Mar 25, 2013 at 04:23:26PM +0000, Burton, Ross wrote:
> On 25 March 2013 16:09, Koen Kooi <koen@dominion.thruhere.net> wrote:
> > So you say it's not an upgrade path, but...
> >
> >> - bluez5 conflicts with/replaces bluez4.
> >
> > ... here you add RREPLACES. Why is that?
>
> The logic was that if a *distro* does the upgrade from bluez4 to
> bluez5, the package manager needs to be able to remove bluez4 when
> installing bluez5, as otherwise they'd just conflict and the package
> manager would error out.
But opkg will still error out because of missing RPROVIDES, no?
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-03-25 17:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 13:07 [PATCH V3 0/2] BlueZ 5.3 new package Cristian Iorga
2013-03-25 13:07 ` [PATCH V3 1/2] bluez5: new package for v5.3 Cristian Iorga
2013-03-25 13:07 ` [PATCH V3 2/2] bluez4: conflicts with/replaces bluez5 Cristian Iorga
2013-03-26 16:42 ` [PATCH V3 2/2] bluez4: conflicts with/replaces bluez5 - upgrade real-life tests Iorga, Cristian
2013-03-26 17:50 ` Martin Jansa
2013-03-26 18:00 ` Iorga, Cristian
2013-03-25 16:09 ` [PATCH V3 0/2] BlueZ 5.3 new package Koen Kooi
2013-03-25 16:23 ` Burton, Ross
2013-03-25 17:03 ` Martin Jansa [this message]
2013-03-25 17:14 ` Burton, Ross
2013-03-26 10:20 ` Iorga, Cristian
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=20130325170346.GD7539@jama \
--to=martin.jansa@gmail.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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.