From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: opkg : angstrom fails console-image build
Date: Thu, 22 Jul 2010 11:36:06 +0200 [thread overview]
Message-ID: <20100722093606.GK2189@jama> (raw)
In-Reply-To: <AANLkTil57uQl9XRZmHY7gDTviye2YboZ0G5QyGsEZCj2@mail.gmail.com>
On Thu, Jul 22, 2010 at 04:56:07PM +0930, Graham Gower wrote:
> On 22 July 2010 16:41, Graham Gower <graham.gower@gmail.com> wrote:
> > On 22 July 2010 15:47, Jaap de Jong <jaap.dejong@nedap.com> wrote:
> >> I've made a completely clean build last night and it breaks at the same
> >> problem.
> >>
> >
> > Koen bumped the opkg SRCREV a couple of days ago. One of the recent
> > opkg changes was to return an error in some erroneous cases which were
> > incorrectly ignored previously (check_data_file_clashes errors are one
> > of these cases).
> >
> > Its possible that this problem was there beforehand and its only now
> > being caught because of less dumb error checking. Sorry, I don't know
> > what is causing the issue - you probably need to look at the
> > dependency graph to see why both opkg and opkg-nogpg-nocurl packages
> > are being built and installed.
> >
> > -Graham
> >
>
> PS: pushing my opkg cleanup patch would probably fix this with no
> further need to investigate...
I have your patch in my local branch and it's not enough (one has to
remove already staged opkg-nogpg(-nocurl) first).
Regards,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
prev parent reply other threads:[~2010-07-22 9:35 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
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 [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=20100722093606.GK2189@jama \
--to=martin.jansa@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 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.