From: Saul Wold <sgw@linux.intel.com>
To: Paul Barker <paul@paulbarker.me.uk>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/3] opkg: No longer PROVIDES update-alternatives
Date: Wed, 15 Jan 2014 14:37:52 -0800 [thread overview]
Message-ID: <52D70DC0.3060709@linux.intel.com> (raw)
In-Reply-To: <CANyK_8cBWSps_v=eF-ktk6YbUKo76KfGTufa09m2gVsgQk7NRQ@mail.gmail.com>
On 01/15/2014 08:13 AM, Paul Barker wrote:
> On 15 January 2014 15:12, Saul Wold <sgw@linux.intel.com> wrote:
>> On 01/14/2014 06:17 PM, Paul Barker wrote:
>>>
>>> The new provider is the opkg-utils recipe.
>>>
>> This seems to have triggered a failure on the AB:
>>
>> | Computing transaction...error: Can't install
>> nativesdk-shadow-4.1.4.3-r13@i686_nativesdk: no package provides
>> nativesdk-update-alternatives-opkg
>>
>
> I've not really done much with nativesdk, but my guess is I just need to change
>
> BBCLASSEXTEND = "native"
>
> to
>
> BBCLASSEXTEND = "native nativesdk"
>
> in the opkg-utils recipe so that nativesdk-* packages are built for
> that recipe. Does that sound correct? If so, I'll re-spin the patches
> with that change.
>
Yup, that's it, aslo why did you locate opkg-utils in a separate
directory from opkgs itself? Is there a reason they can't co-locate?
Sau!
next prev parent reply other threads:[~2014-01-15 22:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 2:17 [PATCH 0/3] Change update-alternatives provider Paul Barker
2014-01-15 2:17 ` [PATCH 1/3] opkg-utils: Upgrade to latest git HEAD Paul Barker
2014-01-15 10:04 ` Koen Kooi
2014-01-15 16:16 ` Paul Barker
2014-01-15 2:17 ` [PATCH 2/3] default-providers: Change update-alternatives provider to opkg-utils Paul Barker
2014-01-15 2:17 ` [PATCH 3/3] opkg: No longer PROVIDES update-alternatives Paul Barker
2014-01-15 15:12 ` Saul Wold
2014-01-15 16:13 ` Paul Barker
2014-01-15 17:05 ` Otavio Salvador
2014-01-15 22:37 ` Saul Wold [this message]
2014-01-16 13:30 ` Paul Barker
2014-01-15 11:21 ` [PATCH 0/3] Change update-alternatives provider Otavio Salvador
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=52D70DC0.3060709@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul@paulbarker.me.uk \
/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