From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/icu: bump version to 60.1
Date: Sun, 3 Dec 2017 21:00:12 +0100 [thread overview]
Message-ID: <20171203210012.0cb2bc4c@windsurf.home> (raw)
In-Reply-To: <20171203194140.8138-1-bernd.kuhls@t-online.de>
Hello,
On Sun, 3 Dec 2017 20:41:40 +0100, Bernd Kuhls wrote:
> Removed 0006-i18n-Drop-include-xlocale.h.patch, problem was fixed
> upstream with a different solution:
> http://bugs.icu-project.org/trac/changeset/40603
>
> Added upstream sha512 hash and license hash.
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
Curious: how many packages that depend on ICU did you build? From past
experience, each major ICU bump very often causes a number of build
failures in other packages.
What are the changes between 59.1 and 60.1 ? Anything significant that
has a chance of breaking packages that depend on ICU ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-12-03 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-03 19:41 [Buildroot] [PATCH 1/1] package/icu: bump version to 60.1 Bernd Kuhls
2017-12-03 20:00 ` Thomas Petazzoni [this message]
2017-12-03 22:01 ` Mario Lang
2017-12-04 7:20 ` Bernd Kuhls
2017-12-04 10:33 ` Thomas Petazzoni
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=20171203210012.0cb2bc4c@windsurf.home \
--to=thomas.petazzoni@free-electrons.com \
--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