From: Titouan Christophe <titouanchristophe@gmail.com>
To: buildroot@buildroot.org
Cc: Titouan Christophe <titouanchristophe@gmail.com>
Subject: [Buildroot] [PATCH 1/1] package/waf: bump to v2.1.1
Date: Mon, 17 Jun 2024 09:55:03 +0200 [thread overview]
Message-ID: <20240617075503.938411-1-titouanchristophe@gmail.com> (raw)
Signed-off-by: Titouan Christophe <titouanchristophe@gmail.com>
---
package/waf/waf.hash | 6 +++---
package/waf/waf.mk | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/package/waf/waf.hash b/package/waf/waf.hash
index 1ad535febb..543bea5d7b 100644
--- a/package/waf/waf.hash
+++ b/package/waf/waf.hash
@@ -1,7 +1,7 @@
# Locally computed
-sha1 e310e29a44f23f80591f2aa6c2d4c30e5f1a26a8 waf-2.0.26
-sha256 dcec3e179f9c33a66544f1b3d7d91f20f6373530510fa6a858cddb6bfdcde14b waf-2.0.26
+sha1 9ee587d802ffd15a2e7cae579560d00754db4fad waf-2.1.1
+sha256 2e66e01fd564f09106419389119c78143327c89a35f26ee3ed376f0ee410a14d waf-2.1.1
# The waf script also contains its license, but is renamed `waf` in the extract
# step, so this is a synonym for the above, to check WAF_LICENSE
-sha256 dcec3e179f9c33a66544f1b3d7d91f20f6373530510fa6a858cddb6bfdcde14b waf
+sha256 2e66e01fd564f09106419389119c78143327c89a35f26ee3ed376f0ee410a14d waf
diff --git a/package/waf/waf.mk b/package/waf/waf.mk
index bffa27a926..a12d15a228 100644
--- a/package/waf/waf.mk
+++ b/package/waf/waf.mk
@@ -4,7 +4,7 @@
#
################################################################################
-WAF_VERSION = 2.0.26
+WAF_VERSION = 2.1.1
WAF_SOURCE = waf-$(WAF_VERSION)
WAF_SITE = https://waf.io
WAF_LICENSE = BSD-3-Clause
--
2.45.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2024-06-17 7:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 7:55 Titouan Christophe [this message]
2024-06-22 17:41 ` [Buildroot] [PATCH 1/1] package/waf: bump to v2.1.1 Thomas Petazzoni via buildroot
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=20240617075503.938411-1-titouanchristophe@gmail.com \
--to=titouanchristophe@gmail.com \
--cc=buildroot@buildroot.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.