From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gdk-pixbuf: Avoid rebuild failures
Date: Thu, 24 Sep 2015 22:40:18 +0100 [thread overview]
Message-ID: <1443130818.19044.104.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAP9ODKrBa6oiFm2Fj1XxtH5m2gx=6nSg4OhEs+s_KjgvAgFaFg@mail.gmail.com>
On Thu, 2015-09-24 at 08:27 -0300, Otavio Salvador wrote:
> Hello Richard,
>
> Thanks for hunting this bug, this was very annoying and hard to
> figure. It does seem to address the issue in our builder.
Sadly, whilst I merged it and it does fix that problem, I suspect this
causes:
https://autobuilder.yoctoproject.org/main/builders/nightly-x32/builds/497/steps/BuildImages/logs/stdio
:(
Cheers,
Richard
next prev parent reply other threads:[~2015-09-24 21:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 22:32 [PATCH] gdk-pixbuf: Avoid rebuild failures Richard Purdie
2015-09-23 22:54 ` Gary Thomas
2015-09-24 6:35 ` Richard Purdie
2015-09-24 11:27 ` Otavio Salvador
2015-09-24 21:40 ` Richard Purdie [this message]
2015-09-25 18:12 ` Otavio Salvador
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=1443130818.19044.104.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
/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.