From: Alejandro del Castillo <alejandro.delcastillo@ni.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] opkg: upgrade to v0.3.0
Date: Wed, 02 Sep 2015 14:39:57 -0500 [thread overview]
Message-ID: <55E7508D.3050101@ni.com> (raw)
In-Reply-To: <1441176900.24871.25.camel@linuxfoundation.org>
On 09/02/2015 01:55 AM, Richard Purdie wrote:
> On Tue, 2015-09-01 at 09:17 -0500, Alejandro del Castillo wrote:
>> Changes required:
>> - Rename opkg-cl to opkg
>> - Add libarchive dependency
>> - Drop backport patches
>> - Drop obsolete directory options
>> - Add patch to handle empty index files
>>
>> Based on initial work by Paul Barker.
>>
>> Signed-off-by: Alejandro del Castillo <alejandro.delcastillo@ni.com>
>> CC: Paul Barker <paul@paulbarker.me.uk>
>
> The autobuilder shows these errors for a build containing this patch:
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-ipk/builds/468/steps/BuildImages/logs/stdio
>
> Not sure why...
running populate-volatile seems to cause the permission problem. If I remove the
commit below (master-next), I can build fine:
0e59378 image.bbclass: Always try to run populate-volatile.sh at rootfs time
Regarding the opkg upgrade patch, I sent to the same thread a follow up patch
that fixes the adt-installer. Both changes are related to the opkg upgrade, so
they can be squashed. Let me know if you want me to send you a v2 patch with the
adt-installer changes included.
--
Cheers,
Alejandro
prev parent reply other threads:[~2015-09-02 19:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 14:17 [PATCH] opkg: upgrade to v0.3.0 Alejandro del Castillo
2015-09-01 23:28 ` [PATCH] adt-installer: upgrade to opkg 0.3.0 Alejandro del Castillo
2015-09-02 6:55 ` [PATCH] opkg: upgrade to v0.3.0 Richard Purdie
2015-09-02 19:39 ` Alejandro del Castillo [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=55E7508D.3050101@ni.com \
--to=alejandro.delcastillo@ni.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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