From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: BAD_RECOMMENDATIONS is broken (opkg issue)
Date: Wed, 24 Feb 2010 15:58:42 -0500 [thread overview]
Message-ID: <20100224205842.GC9601@denix.org> (raw)
In-Reply-To: <6ec4247d0911181455g6399eeeci38db4e9b727886d@mail.gmail.com>
On Thu, Nov 19, 2009 at 09:25:06AM +1030, Graham Gower wrote:
> 2009/11/19 Phil Blundell <philb@gnu.org>:
> >
> > It's meant to be handled by this chunk of code, and I'm fairly sure that
> > this used to work reliably. Has that part of opkg changed recently?
>
> Nope, no changes there. And no particularly invasive changes up to r240.
>
> I have some minor worries that
> http://code.google.com/p/opkg/source/detail?r=328 will have some non
> obvious fallout. (Obviously not the issue here though)
FYI, http://thread.gmane.org/gmane.comp.handhelds.openembedded/30417
--
Denys
prev parent reply other threads:[~2010-02-24 21:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 10:26 BAD_RECOMMENDATIONS is broken Sebastian Spaeth
2009-11-18 10:35 ` BAD_RECOMMENDATIONS is broken (opkg issue) Sebastian Spaeth
2009-11-18 21:20 ` Graham Gower
2009-11-18 22:12 ` Phil Blundell
2009-11-18 22:55 ` Graham Gower
2010-02-24 20:58 ` Denys Dmytriyenko [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=20100224205842.GC9601@denix.org \
--to=denis@denix.org \
--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