From: Robert Yang <liezhi.yang@windriver.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>, Zhenfeng.Zhao@windriver.com
Subject: Re: [PATCH 1/1] opkg 0.1.8: respect to the arch when choose the alternatives
Date: Fri, 1 Jun 2012 08:23:21 +0800 [thread overview]
Message-ID: <4FC80B79.6070101@windriver.com> (raw)
In-Reply-To: <D16CA58F-8D7A-4910-ACCA-84E01CEE6510@dominion.thruhere.net>
On 05/31/2012 11:01 PM, Koen Kooi wrote:
>
> Op 31 mei 2012, om 16:13 heeft Robert Yang het volgende geschreven:
>
>> There is a bug if we:
>> 1) bitbake core-image-sato-sdk MACHINE=qemux86
>> 2) bitbake core-image-sato with MACHINE=crownbay
>>
>> Then several pkgs in deploy/ipk/i586 would be installed to crownbay's
>> image even if there is one in deploy/ipk/core2 and we have set the
>> core2's priority higher than i586, when the version in deploy/ipk/i586 is
>> higher. This doesn't work for us, for example, what the crownbay need is
>> xserver-xorg-1.9.3, but it installs xserver-xorg-1.11.2.
>
> And this is working exactly as intended. Don't break opkg because your hardware driver situation sucks.
>
Hi Koen,
Thanks for your great patient on this patch:-), I'm afraid that this is
not working exactly as intended, since the rpm or dpkg doesn't have this
issue. (I have fixed other issue for rpm, but not the same as this one,
the xserver-xorg-1.9.3.rpm had installed correctly before the fix for rpm).
and dpkg works well without any fix.
I'm also glad that if we won't fix it.
// Robert
> So: NAK on this patch.
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
next prev parent reply other threads:[~2012-06-01 0:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 14:13 [PATCH 0/1] V2 opkg 0.1.8: respect to the arch when choose the alternatives Robert Yang
2012-05-31 14:13 ` [PATCH 1/1] " Robert Yang
2012-05-31 15:01 ` Koen Kooi
2012-06-01 0:23 ` Robert Yang [this message]
2012-06-01 8:17 ` Richard Purdie
2012-06-01 9:04 ` Koen Kooi
2012-06-01 10:02 ` Richard Purdie
2012-06-01 10:35 ` Koen Kooi
2012-06-04 9:31 ` Robert Yang
2012-06-04 10:39 ` Martin Jansa
2012-06-04 14:38 ` Koen Kooi
-- strict thread matches above, loose matches on Subject: below --
2012-05-25 10:02 [PATCH 0/1] " Robert Yang
2012-05-25 10:02 ` [PATCH 1/1] " Robert Yang
2012-05-25 11:19 ` Koen Kooi
2012-05-25 11:30 ` Martin Jansa
2012-05-25 14:09 ` Richard Purdie
2012-05-26 2:47 ` Robert Yang
2012-05-26 2:54 ` Robert Yang
2012-05-26 6:28 ` Martin Jansa
2012-05-26 8:07 ` Koen Kooi
2012-05-26 8:47 ` Robert Yang
2012-05-26 8:15 ` Robert Yang
2012-05-26 8:19 ` Martin Jansa
2012-05-26 8:35 ` Robert Yang
2012-05-26 8:42 ` Martin Jansa
2012-05-26 2:25 ` Robert Yang
2012-05-26 5:24 ` Robert Yang
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=4FC80B79.6070101@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=Zhenfeng.Zhao@windriver.com \
--cc=koen@dominion.thruhere.net \
--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