From: Alexander Egorenkov <egorenar@linux.ibm.com>
To: buildroot@buildroot.org
Subject: [Buildroot] [PATCH 1/1] package/s390-tools: bump to version 2.26.0
Date: Sat, 18 Feb 2023 14:40:59 +0100 [thread overview]
Message-ID: <20230218134059.53863-1-egorenar@linux.ibm.com> (raw)
Signed-off-by: Alexander Egorenkov <egorenar@linux.ibm.com>
---
package/s390-tools/s390-tools.hash | 2 +-
package/s390-tools/s390-tools.mk | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/s390-tools/s390-tools.hash b/package/s390-tools/s390-tools.hash
index a0dde477c324..37b67c5cb180 100644
--- a/package/s390-tools/s390-tools.hash
+++ b/package/s390-tools/s390-tools.hash
@@ -1,3 +1,3 @@
# Locally computed:
-sha256 ccb20954e748309a50fd56edd9abd94c6f897081e9a1a33e9d965a56f650990d s390-tools-2.25.0.tar.gz
+sha256 da81c55fb11d84923c0ebaed703f557052eb1a273495f60ebe3d20a74627303e s390-tools-2.26.0.tar.gz
sha256 cca17a9a944ebec769adee4aebd805c912c357785ff2705a99ffe68563021f75 LICENSE
diff --git a/package/s390-tools/s390-tools.mk b/package/s390-tools/s390-tools.mk
index cb6278dfb837..8cd549140547 100644
--- a/package/s390-tools/s390-tools.mk
+++ b/package/s390-tools/s390-tools.mk
@@ -4,7 +4,7 @@
#
################################################################################
-S390_TOOLS_VERSION = 2.25.0
+S390_TOOLS_VERSION = 2.26.0
S390_TOOLS_SITE = $(call github,ibm-s390-linux,s390-tools,v$(S390_TOOLS_VERSION))
S390_TOOLS_LICENSE = MIT
S390_TOOLS_LICENSE_FILES = LICENSE
--
2.39.2
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2023-02-18 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-18 13:40 Alexander Egorenkov [this message]
2023-02-19 21:09 ` [Buildroot] [PATCH 1/1] package/s390-tools: bump to version 2.26.0 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=20230218134059.53863-1-egorenar@linux.ibm.com \
--to=egorenar@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox