From: "Maupin, Chase" <chase.maupin@ti.com>
To: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: bitbake does not fail when QA issues encountered
Date: Wed, 9 Feb 2011 14:02:01 -0600 [thread overview]
Message-ID: <131E5DFBE7373E4C8D813795A6AA7F08032A3023DE@dlee06.ent.ti.com> (raw)
In-Reply-To: <AANLkTikXULU=UyfomMr_GVx5o1GieZrRxDZET3QF30px@mail.gmail.com>
> -----Original Message-----
> From: openembedded-devel-bounces@lists.openembedded.org
> [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of
> Frans Meulenbroeks
> Sent: Saturday, February 05, 2011 7:35 AM
> To: openembedded-devel@lists.openembedded.org
> Subject: Re: [oe] bitbake does not fail when QA issues encountered
>
> 2011/2/4 Otavio Salvador <otavio@ossystems.com.br>:
> > On Fri, Feb 4, 2011 at 15:26, Frans Meulenbroeks
> > <fransmeulenbroeks@gmail.com> wrote:
> >> The recipes at hand are:
> > ...
> >> cups: there is someone bitching about that this is 1.2, but he
> >> apparently prefers bitching upon resolving the issue. Probably the
> >> best solution is to drop the DP = -1 from the 1.4.4 recipe
> > ...
> >
> > I can work on cups next week (I am on VAC right now).
>
> Actually the cups thing is the one I would feel fairly comfortable with.
> The question here is mainly when/how to drop the DP = -1.
> A pinning of 1.4.4 is already in my local.conf for quite a while.
Frans,
Have you already got a patch for version 1.2.12 to fix the desktop file QA errors? If not I was going to work on this because this is breaking my build scripts which check the return status of the build.
Chase
>
> Frans
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2011-02-09 20:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 19:37 bitbake does not fail when QA issues encountered Maupin, Chase
2011-01-25 20:58 ` Frans Meulenbroeks
2011-01-25 21:36 ` Khem Raj
2011-01-26 10:32 ` Martyn Welch
2011-01-26 15:03 ` Maupin, Chase
2011-01-26 15:27 ` Tom Rini
2011-01-27 9:38 ` Thomas Zimmermann
2011-01-27 11:27 ` Frans Meulenbroeks
2011-01-27 15:02 ` Tom Rini
2011-02-03 7:09 ` Denys Dmytriyenko
2011-02-03 17:43 ` Tom Rini
2011-02-03 22:20 ` Denys Dmytriyenko
2011-02-03 23:09 ` Tom Rini
2011-02-04 7:54 ` Frans Meulenbroeks
2011-02-04 8:16 ` Stefan Schmidt
2011-02-04 8:37 ` Frans Meulenbroeks
2011-02-04 9:03 ` Stefan Schmidt
2011-02-04 9:57 ` Frans Meulenbroeks
2011-02-04 12:42 ` Otavio Salvador
2011-02-04 13:10 ` Frans Meulenbroeks
2011-02-04 13:58 ` Andreas Mueller
2011-02-04 14:59 ` Tom Rini
2011-02-04 15:26 ` Frans Meulenbroeks
2011-02-04 15:52 ` Otavio Salvador
2011-02-05 13:35 ` Frans Meulenbroeks
2011-02-06 1:21 ` Otavio Salvador
2011-02-06 12:02 ` Frans Meulenbroeks
2011-02-09 20:02 ` Maupin, Chase [this message]
2011-02-09 20:13 ` Maupin, Chase
2011-02-10 6:32 ` Frans Meulenbroeks
2011-02-04 17:37 ` Tom Rini
2011-02-04 14:44 ` Tom Rini
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=131E5DFBE7373E4C8D813795A6AA7F08032A3023DE@dlee06.ent.ti.com \
--to=chase.maupin@ti.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.