From: Dario Binacchi <dario.binacchi@amarulasolutions.com>
To: buildroot@buildroot.org
Cc: Dario Binacchi <dario.binacchi@amarulasolutions.com>,
Andrea Ricchi <andrea.ricchi@amarulasolutions.com>,
Roy Kollen Svendsen <roykollensvendsen@gmail.com>,
Angelo Compagnucci <angelo.compagnucci@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Jesse Van Gavere <jesseevg@gmail.com>,
richard.genoud@bootlin.com
Subject: [Buildroot] [PATCH v5 3/6] package/qwt: bump to version 6.3.0
Date: Tue, 8 Sep 2026 16:12:50 +0200 [thread overview]
Message-ID: <20260908141253.1556634-4-dario.binacchi@amarulasolutions.com> (raw)
In-Reply-To: <20260908141253.1556634-1-dario.binacchi@amarulasolutions.com>
Release notes:
https://sourceforge.net/p/qwt/git/ci/qwt-6.2/tree/CHANGES-6.2
https://sourceforge.net/p/qwt/git/ci/develop/tree/CHANGES-6.3
Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
---
(no changes since v1)
package/qwt/qwt.hash | 8 ++++----
package/qwt/qwt.mk | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/package/qwt/qwt.hash b/package/qwt/qwt.hash
index d4fd210cbd69..e20c9ebadab9 100644
--- a/package/qwt/qwt.hash
+++ b/package/qwt/qwt.hash
@@ -1,7 +1,7 @@
-# From https://sourceforge.net/projects/qwt/files/qwt/6.1.6
-md5 cc71be5d6c33c2fc19ae8082ccdd3e83 qwt-6.1.6.tar.bz2
-sha1 b1f17a86c9b1b0790a0c0067ef69fb6277efac79 qwt-6.1.6.tar.bz2
+# From https://sourceforge.net/projects/qwt/files/qwt/6.3.0
+md5 06a8f8eb1bc07bedfb1df601804439cb qwt-6.3.0.tar.bz2
+sha1 9180f33f75ff8817f27019c94d10f92de840a5e4 qwt-6.3.0.tar.bz2
# Locally computed
-sha256 99460d31c115ee4117b0175d885f47c2c590d784206f09815dc058fbe5ede1f6 qwt-6.1.6.tar.bz2
+sha256 dcb085896c28aaec5518cbc08c0ee2b4e60ada7ac929d82639f6189851a6129a qwt-6.3.0.tar.bz2
sha256 d8737db330e1eeb439962e11654ab7f1aece3561d9415454a8c538643824ede6 COPYING
diff --git a/package/qwt/qwt.mk b/package/qwt/qwt.mk
index 9f0b78655f6f..67292ee025be 100644
--- a/package/qwt/qwt.mk
+++ b/package/qwt/qwt.mk
@@ -4,7 +4,7 @@
#
################################################################################
-QWT_VERSION = 6.1.6
+QWT_VERSION = 6.3.0
QWT_SOURCE = qwt-$(QWT_VERSION).tar.bz2
QWT_SITE = http://downloads.sourceforge.net/project/qwt/qwt/$(QWT_VERSION)
QWT_INSTALL_STAGING = YES
--
2.43.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-09-08 14:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 14:12 [Buildroot] [PATCH v5 0/6] Support qmake for Qt6 Dario Binacchi
2026-09-08 14:12 ` [Buildroot] [PATCH v5 1/6] package/qt6: Add qmake functionality Dario Binacchi
2026-09-08 14:12 ` [Buildroot] [PATCH v5 2/6] package/qt6: add QT6_QT_CONF_FIXUP hook Dario Binacchi
2026-09-08 14:12 ` Dario Binacchi [this message]
2026-09-08 14:12 ` [Buildroot] [PATCH v5 4/6] package/pkg-qmake: support Qt6 Dario Binacchi
2026-09-08 14:12 ` [Buildroot] [PATCH v5 5/6] package/qwt: enable build with Qt6 Dario Binacchi
2026-09-08 14:12 ` [Buildroot] [PATCH v5 6/6] package/cutekeyboard: " Dario Binacchi
2026-09-10 9:52 ` Andrea Ricchi
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=20260908141253.1556634-4-dario.binacchi@amarulasolutions.com \
--to=dario.binacchi@amarulasolutions.com \
--cc=andrea.ricchi@amarulasolutions.com \
--cc=angelo.compagnucci@gmail.com \
--cc=buildroot@buildroot.org \
--cc=jesseevg@gmail.com \
--cc=richard.genoud@bootlin.com \
--cc=roykollensvendsen@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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