From: Alexander Egorenkov <egorenar@linux.ibm.com>
To: buildroot@buildroot.org
Subject: [Buildroot] [PATCH 1/1] package/s390-tools: bump to version 2.19.0
Date: Mon, 22 Nov 2021 09:48:09 +0100 [thread overview]
Message-ID: <20211122084809.475864-1-egorenar@linux.ibm.com> (raw)
Fixes:
- https://release-monitoring.org/project/10714/
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 eafe7f4d7acf..13c68fbf52f4 100644
--- a/package/s390-tools/s390-tools.hash
+++ b/package/s390-tools/s390-tools.hash
@@ -1,3 +1,3 @@
# Locally computed:
-sha256 a1e2118152a85201984d2045033d49f7fd92e8cd0ea80ae0a5ebeb0d258cdedb s390-tools-2.18.0.tar.gz
+sha256 17dc163e6a1e940f895c64955c130058600e1df834e1ab134410be7266ef724a s390-tools-2.19.0.tar.gz
sha256 cca17a9a944ebec769adee4aebd805c912c357785ff2705a99ffe68563021f75 LICENSE
diff --git a/package/s390-tools/s390-tools.mk b/package/s390-tools/s390-tools.mk
index 6b4351ce83ed..328986bcb37c 100644
--- a/package/s390-tools/s390-tools.mk
+++ b/package/s390-tools/s390-tools.mk
@@ -4,7 +4,7 @@
#
################################################################################
-S390_TOOLS_VERSION = 2.18.0
+S390_TOOLS_VERSION = 2.19.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.31.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2021-11-22 8:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 8:48 Alexander Egorenkov [this message]
2021-12-11 20:43 ` [Buildroot] [PATCH 1/1] package/s390-tools: bump to version 2.19.0 Arnout Vandecappelle
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=20211122084809.475864-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 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.