From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Broken BAD_RECOMMENDATIONS support
Date: Mon, 07 Nov 2011 13:52:31 +0000 [thread overview]
Message-ID: <1320673961.22985.653.camel@phil-desktop> (raw)
In-Reply-To: <CAP9ODKp-5oZ3Fr=5EWbm7F1vR3ZFGXw9ezkPj-Ciui12SczM6A@mail.gmail.com>
On Mon, 2011-11-07 at 11:45 -0200, Otavio Salvador wrote:
> Hello,
>
> It seems BAD_RECOMMENDATIONS support, in ipk, is broken.
>
> I checked and the rootfs_ipk is writting the contents into the opkg's
> status file however it seems opkg when starts to install the packages
> it overwrites or ignores it. People at IRC confirmated that this also
> happens to them and thus this is indeed broken.
>
> Do someone know how I can debug opkg to see what's going on?
You can add -V4 to ${ipkg_args} in package_install_internal_ipk() to get
more verbosity, though the output is not always especially illuminating.
It might be easiest to just hack the scripting so that it bails out at
that point and then run opkg-cl by hand under the debugger.
p.
next prev parent reply other threads:[~2011-11-07 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 13:45 Broken BAD_RECOMMENDATIONS support Otavio Salvador
2011-11-07 13:52 ` Phil Blundell [this message]
2011-11-07 14:20 ` 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=1320673961.22985.653.camel@phil-desktop \
--to=philb@gnu.org \
--cc=openembedded-core@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