Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-devel@lists.openembedded.org,
	openembedded-core@lists.openembedded.org
Subject: Re: State of bitbake world, Failed tasks 2015-08-30
Date: Wed, 2 Sep 2015 14:06:38 +0200	[thread overview]
Message-ID: <20150902120638.GA2470@jama> (raw)
In-Reply-To: <1441192582.24871.52.camel@linuxfoundation.org>

[-- Attachment #1: Type: text/plain, Size: 920 bytes --]

On Wed, Sep 02, 2015 at 12:16:22PM +0100, Richard Purdie wrote:
> On Mon, 2015-08-31 at 14:56 +0200, Martin Jansa wrote:
> > OE @ ~/openembedded-core $ git log --oneline origin/master..contrib/jansa/master 
> > e223862 initramfs-framework: Drop allarch
> > d51627d linux-firmware: Drop allarch
> > ee54e69 ppp-dialin: Drop allarch
> > 2ff92fc usbinit, weston-init, run-postinsts, qt-demo-init: Drop allarch
> > 913639d resolvconf: Drop allarch
> 
> I think that with some recent changes you might be able to drop all of
> the above. We've also added an automated sanity test to ensure this list
> doesn't regress either.

Thanks, I've noticed the SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS additions and
was planning to drop this before next test signatures run on jenkins..
it's just too busy doing normal builds so I didn't get to it yet.

Cheers,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

      reply	other threads:[~2015-09-02 12:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31 12:56 State of bitbake world, Failed tasks 2015-08-30 Martin Jansa
2015-08-31 13:32 ` [oe] " Andreas Müller
2015-08-31 16:03   ` Martin Jansa
2015-09-02 11:16 ` Richard Purdie
2015-09-02 12:06   ` 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=20150902120638.GA2470@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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