From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/libupnpp: bump to version 0.15.0
Date: Mon, 12 Sep 2016 15:46:49 +0200 [thread overview]
Message-ID: <1473688009.1525.10.camel@embedded.rocks> (raw)
In-Reply-To: <20160911230718.364d0611@free-electrons.com>
On Sun, 2016-09-11 at 23:07 +0200, Thomas Petazzoni wrote:
> Hello,
>
> On Sun, 11 Sep 2016 09:12:40 +0200, J?rg Krause wrote:
> >
> > Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
> > ---
> > ?package/libupnpp/libupnpp.hash | 4 ++--
> > ?package/libupnpp/libupnpp.mk???| 2 +-
> > ?2 files changed, 3 insertions(+), 3 deletions(-)
>
> This update is causing a number of build failures:
>
> ? http://autobuild.buildroot.net/?reason=libupnpp-0.15.0
>
> Could you have a look?
Yes, I am already working with upstream to fix the issue.
J?rg
prev parent reply other threads:[~2016-09-12 13:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 7:12 [Buildroot] [PATCH] package/libupnpp: bump to version 0.15.0 Jörg Krause
2016-09-11 13:35 ` Thomas Petazzoni
2016-09-11 21:07 ` Thomas Petazzoni
2016-09-12 13:46 ` Jörg Krause [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=1473688009.1525.10.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--cc=buildroot@busybox.net \
/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