From: "Jörg Krause" <jkrause@posteo.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/shairport-sync: fix static builds
Date: Sun, 30 Nov 2014 13:09:11 +0100 [thread overview]
Message-ID: <1417349351.882.7.camel@posteo.de> (raw)
In-Reply-To: <20141130113557.GB4124@free.fr>
Yann,
On So, 2014-11-30 at 12:35 +0100, Yann E. MORIN wrote:
>
> All three patches applied upstream:
> https://github.com/mikebrady/shairport-sync/commit/2a430ec434674ed8c1959698c061662bb7abc1a1
> https://github.com/mikebrady/shairport-sync/commit/e5a74a3ff08134a2b11f07bd850659d7816fb03d
> https://github.com/mikebrady/shairport-sync/commit/1f759e57e8c0682613eaaf89a46fdf6db4c6b5cd
>
> There is now a new release with those three patches, but that would make
> us bump pass a few releases, from 2.1.8 to 2.1.13, with some new
> features along the lines.
>
> So, for the release, I suggest we just apply those three patches, and
> I'll send a version bump after the release has been cut.
>
> Is that OK?
First, many thanks for your work! I had a look at the autobuild errors,
but it was beyond my knowledge.
Version 2.1.9 to 2.1.13 include several bugfixes, so I would suggest to
update the package. I can make a run-time test tomorrow.
next prev parent reply other threads:[~2014-11-30 12:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-29 13:34 [Buildroot] [PATCH] package/shairport-sync: fix static builds Yann E. MORIN
2014-11-29 18:10 ` Baruch Siach
2014-11-29 18:15 ` Yann E. MORIN
2014-11-30 11:35 ` Yann E. MORIN
2014-11-30 12:09 ` Jörg Krause [this message]
2014-11-30 13:48 ` Yann E. MORIN
-- strict thread matches above, loose matches on Subject: below --
2014-11-30 11:42 Yann E. MORIN
2014-11-30 23:11 ` Peter Korsgaard
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=1417349351.882.7.camel@posteo.de \
--to=jkrause@posteo.de \
--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