From: Marco Cavallini <koansoftware@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: opkg : angstrom fails console-image build
Date: Wed, 21 Jul 2010 22:38:28 +0200 [thread overview]
Message-ID: <4C475AC4.6010302@gmail.com> (raw)
In-Reply-To: <i275t3$65g$1@dough.gmane.org>
Koen Kooi ha scritto, Il 21/07/2010 18:05:
> On 21-07-10 16:31, Marco Cavallini wrote:
>> Anybody could explain what's happening with opkg in OE recently please?
>> I saw a patch in ML and I wonder if it will be pushed in order to solve
>> this problem.
>
>> http://pastebin.com/NhtAP0Re
>
> It looks like you have a local diff to install 'opkg' as well as
> 'opkg-nogpg-nocurl', which breaks. Solution: remove your local diff.
Thank you for answering.
I'm sorry but I dont' understand what do you mean with "local diff", I'm
using a clean OE org.openembedded.dev branch.
TIA
/marco
next prev parent reply other threads:[~2010-07-21 20:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 14:31 opkg : angstrom fails console-image build Marco Cavallini
2010-07-21 16:05 ` Koen Kooi
2010-07-21 20:38 ` Marco Cavallini [this message]
2010-07-22 0:03 ` Graham Gower
2010-07-22 6:17 ` Jaap de Jong
2010-07-22 7:11 ` Graham Gower
2010-07-22 7:26 ` Graham Gower
2010-07-22 9:36 ` Martin Jansa
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=4C475AC4.6010302@gmail.com \
--to=koansoftware@gmail.com \
--cc=openembedded-devel@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