From: "Gaël PORTAY" <gael.portay@savoirfairelinux.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] qt5: bump latest version to 5.11.0
Date: Mon, 18 Jun 2018 19:04:52 -0400 [thread overview]
Message-ID: <20180618230452.clpzxg5no3gio57w@archlinux> (raw)
In-Reply-To: <20180617234604.0a7d1225@windsurf>
Hi Thomas,
On Sun, Jun 17, 2018 at 11:46:04PM +0200, Thomas Petazzoni wrote:
> (...)
>
> I've applied. But there was something weird, see below.
>
>
> > diff --git a/package/qt5/qt5charts/qt5charts.hash b/package/qt5/qt5charts/qt5charts.hash
> > index ce1189d0e1..6bd9a9d51b 100644
> > --- a/package/qt5/qt5charts/qt5charts.hash
> > +++ b/package/qt5/qt5charts/qt5charts.hash
> > @@ -1,8 +1,8 @@
> > # Hash from: https://download.qt.io/official_releases/qt/5.6/5.6.3/submodules/qtcharts-opensource-src-2.1.3.tar.xz.mirrorlist
> > sha256 f636a9b1c255f678f11b36cd73abc807d16dae0c31ecbc75c09524703aae7d2f qtcharts-opensource-src-2.1.3.tar.xz
>
> This didn't apply, because there was no such hash in upstream
> Buildroot, since qtcharts only appeared in Qt 5.7.
>
> Could you make sure your patches apply on top of the latest master ?
>
Facepalm... I forgot to send this patch[1] with the bump; qt5charts is
available with 5.6 since 5.6.3 under the version 2.1.3.
Even worse... the hash bump of 5.11.0 for this module is now missing :(
Could you consider this patch as well[2]. Thanks and sorry about mess
up.
> Thanks!
>
> Thomas
> --
> Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
> Embedded Linux and Kernel engineering
> https://bootlin.com
Regards,
Ga?l
[1]: https://patchwork.ozlabs.org/patch/931215/
[2]: https://patchwork.ozlabs.org/patch/931214/
prev parent reply other threads:[~2018-06-18 23:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 23:44 [Buildroot] [PATCH] qt5: bump latest version to 5.11.0 Gaël PORTAY
2018-06-17 21:46 ` Thomas Petazzoni
2018-06-18 23:04 ` Gaël PORTAY [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=20180618230452.clpzxg5no3gio57w@archlinux \
--to=gael.portay@savoirfairelinux.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