From: baal-zebub <baal-zebub@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] bash: update to 5.1.016.
Date: Sat, 08 Jan 2022 13:20:45 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34942@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 568 bytes --]
There is a new pull request by baal-zebub against master on the void-packages repository
https://github.com/baal-zebub/void-packages bash
https://github.com/void-linux/void-packages/pull/34942
bash: update to 5.1.016.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
A patch file from https://github.com/void-linux/void-packages/pull/34942.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-bash-34942.patch --]
[-- Type: text/x-diff, Size: 1658 bytes --]
From 22b3d84b4c100f0739469fa3a005d01afebf5059 Mon Sep 17 00:00:00 2001
From: Kamil Smardzewski <roderyk197@gmail.com>
Date: Sat, 8 Jan 2022 13:16:04 +0100
Subject: [PATCH] bash: update to 5.1.016.
---
srcpkgs/bash/template | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/bash/template b/srcpkgs/bash/template
index c13fef6e2bd2..9751a08f34ee 100644
--- a/srcpkgs/bash/template
+++ b/srcpkgs/bash/template
@@ -1,6 +1,6 @@
# Template file for 'bash'
pkgname=bash
-version=5.1.008
+version=5.1.016
revision=1
_bash_distver=${version%.*}
_bash_patchlevel=${version##*.}
@@ -34,7 +34,15 @@ checksum="cc012bc860406dcf42f64431bcd3d2fa7560c02915a601aba9cd597a39329baa
cccbb5e9e6763915d232d29c713007a62b06e65126e3dd2d1128a0dc5ef46da5
75e17d937de862615c6375def40a7574462210dce88cf741f660e2cc29473d14
acfcb8c7e9f73457c0fb12324afb613785e0c9cef3315c9bbab4be702f40393a
- f22cf3c51a28f084a25aef28950e8777489072628f972b12643b4534a17ed2d1"
+ f22cf3c51a28f084a25aef28950e8777489072628f972b12643b4534a17ed2d1
+ e45cda953ab4b4b4bde6dc34d0d8ca40d1cc502046eb28070c9ebcd47e33c3ee
+ a2c8d7b2704eeceff7b1503b7ad9500ea1cb6e9393faebdb3acd2afdd7aeae2a
+ 58191f164934200746f48459a05bca34d1aec1180b08ca2deeee3bb29622027b
+ 10f189c8367c4a15c7392e7bf70d0ff6953f78c9b312ed7622303a779273ab98
+ c7acb66df435d284304c16ca83a5265f9edd9368612095b01a733d45c77ed5ad
+ 6a4ee0c81b437b96279a792c1efcec4ba56f009195a318083db6b53b096f83d0
+ 1b37692ef1f6cc3dcec246773443276066e6b1379868f8c14e01f4dfd4df80f0
+ 8899144f76a5db1fb41a89ed881c9f19add95728dd71db324f772ef225c5384f"
make_dirs="/etc/bash/bashrc.d 755 root root"
conflicts="chroot-bash>=0"
next reply other threads:[~2022-01-08 12:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 12:20 baal-zebub [this message]
2022-01-08 16:46 ` [PR PATCH] [Merged]: " leahneukirchen
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34942@inbox.vuxu.org \
--to=baal-zebub@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).