From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: opkg : angstrom fails console-image build
Date: Wed, 21 Jul 2010 18:05:54 +0200 [thread overview]
Message-ID: <i275t3$65g$1@dough.gmane.org> (raw)
In-Reply-To: <4C4704CB.2010204@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFMRxriMkyGM64RGpERAhK1AJ9ZUKTULkfpL82eLu2sAdYrzZKVngCfYJLy
vFWj3USeDL0KNk+/xqgdlKk=
=a3yG
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-07-21 16:06 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 [this message]
2010-07-21 20:38 ` Marco Cavallini
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='i275t3$65g$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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 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.