From: Henri Bragge <henri.bragge@dcombus.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH v2 1/2] recipe for gsnmp-0.3.0
Date: Fri, 06 Aug 2010 13:05:15 +0300 [thread overview]
Message-ID: <4C5BDE5B.3050008@dcombus.com> (raw)
In-Reply-To: <AANLkTincP+hP1RSsA+u5+HQ3xKLFgDkt7x4R-hN3kOsP@mail.gmail.com>
Frans Meulenbroeks wrote:
> 2010/8/5 Frans Meulenbroeks <fransmeulenbroeks@gmail.com>:
>
>> This one also failed building with a similar QA issue:
>>
>> NOTE: Running task 629 of 630 (ID: 10,
>> /home/frans/oe/openembedded/recipes/gsnmp/gsnmp_0.3.0.bb,
>> do_qa_staging)
>> ERROR: QA Issue with staging: libexslt.pc failed sanity test (tmpdir)
>> in path /home/frans/oe/tmp_angstrom/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib/pkgconfig
>> ERROR: QA Issue with staging: libxslt.pc failed sanity test (tmpdir)
>> in path /home/frans/oe/tmp_angstrom/sysroots/armv7a-angstrom-linux-gnueabi/usr/lib/pkgconfig
>> ERROR: QA staging was broken by the package built above
>>
>>
>> see http://tinderbox.openembedded.net/builds/81312
>>
>> No idea how exactly to fix this.
>>
>> Frans
>>
>>
> Please disregard ths comment and the one on the other recipe.
> Apparently some other recipe (libxslt) left a faulty pc file in pkgconfig.
> That is something that needs to be repaired (although I woudl not know
> how), but does not affect your recipe.
>
> Your recipes have been tested, build nicely and have been pushed.
> Thank you for your contribution, and again apologies for any
> inconvenience caused by the above mail)
>
No harm done, I suspected it was someone else's fault this time. Thanks
for testing & comments.
- Henri
next prev parent reply other threads:[~2010-08-06 10:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 10:43 recipes for gsnmp and scli Henri Bragge
2010-08-04 10:43 ` [PATCH 1/2] recipe for gsnmp-0.3.0 Henri Bragge
2010-08-04 10:43 ` [PATCH 2/2] recipe for scli-0.4.0 Henri Bragge
2010-08-04 11:54 ` Frans Meulenbroeks
2010-08-04 12:48 ` [PATCH v2 1/2] recipe for gsnmp-0.3.0 Henri Bragge
2010-08-04 12:48 ` [PATCH v2 2/2] recipe for scli-0.4.0 Henri Bragge
2010-08-04 17:43 ` [PATCH v2 1/2] recipe for gsnmp-0.3.0 Frans Meulenbroeks
2010-08-05 8:53 ` Henri Bragge
2010-08-05 10:05 ` Frans Meulenbroeks
2010-08-05 18:49 ` Frans Meulenbroeks
2010-08-06 9:32 ` Frans Meulenbroeks
2010-08-06 10:05 ` Henri Bragge [this message]
2010-08-06 14:08 ` Frans Meulenbroeks
2010-08-09 11:36 ` [PATCH 1/1] gsnmp-0.3.0: fix quoting in autoconf macros Henri Bragge
2010-08-09 11:52 ` Paul Menzel
2010-08-09 12:05 ` Henri Bragge
2010-08-09 12:36 ` Paul Menzel
2010-08-09 15:31 ` [PATCH v3 " Henri Bragge
2010-08-09 15:43 ` [PATCH " Henri Bragge
2010-08-09 19:16 ` Frans Meulenbroeks
2010-08-09 11:43 ` [PATCH v2 1/2] recipe for gsnmp-0.3.0 Henri Bragge
2010-08-09 12:20 ` [PATCH v2 1/1] gsnmp-0.3.0: fix quoting in autoconf macros Henri Bragge
2010-08-04 12:54 ` [PATCH 2/2] recipe for scli-0.4.0 Henri Bragge
2010-08-05 8:44 ` [PATCH v3 1/2] recipe for gsnmp-0.3.0 Henri Bragge
2010-08-05 8:44 ` [PATCH v3 2/2] recipe for scli-0.4.0 Henri Bragge
2010-08-05 18:47 ` Frans Meulenbroeks
2010-08-04 11:51 ` [PATCH 1/2] recipe for gsnmp-0.3.0 Frans Meulenbroeks
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=4C5BDE5B.3050008@dcombus.com \
--to=henri.bragge@dcombus.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.