From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: QA Logs now on tinderbox
Date: Tue, 23 Sep 2008 17:54:14 +0200 [thread overview]
Message-ID: <gbb3f6$nfr$1@ger.gmane.org> (raw)
In-Reply-To: <d1b08f940809230842j78a43e64r6f2e43fcecd1f656@mail.gmail.com>
Andrea Adami wrote:
>> These two are the most common:
>
> Well, it is clear to me these are 'cruft' in staging. Two wrong
> packages are tainting the whole staging area.
> (This phenomenon has been already seen with libmudflap, libc, ... in
> angstrom-stable [1])
>
> But...why not fix these two immediately?
The .pc.in files need to get fixed, since fixing them when they are
already in staging means that you are shipping from .pc files in -dev
packages.
regards,
Koen
>
> Andrea
>
>
> [1]
> ERROR: QA Issue: libmudflap.la failed sanity test (installed) in path
> /OE/angstrom-tmp//staging/arm-angstrom-linux-gnueabi/lib
> NOTE: a QA error occured but will not be logged because QA_LOG is not set
> ERROR: QA Issue: libsupc++.la failed sanity test (installed) in path
> /OE/angstrom-tmp//staging/arm-angstrom-linux-gnueabi/lib
> NOTE: a QA error occured but will not be logged because QA_LOG is not set
> ERROR: QA Issue: libmudflapth.la failed sanity test (installed) in path
> /OE/angstrom-tmp//staging/arm-angstrom-linux-gnueabi/lib
> NOTE: a QA error occured but will not be logged because QA_LOG is not set
> ERROR: QA Issue: libstdc++.la failed sanity test (installed) in path
> /OE/angstrom-tmp//staging/arm-angstrom-linux-gnueabi/lib
> NOTE: a QA error occured but will not be logged because QA_LOG is not set
next prev parent reply other threads:[~2008-09-23 15:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 8:58 QA Logs now on tinderbox Andrea Adami
2008-09-23 9:34 ` Robert Schuster
2008-09-23 11:14 ` Koen Kooi
2008-09-23 15:42 ` Andrea Adami
2008-09-23 15:54 ` Koen Kooi [this message]
2008-09-23 17:18 ` Jeremy Lainé
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='gbb3f6$nfr$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.