From: kwshi <kwshi@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] buildah: update to 1.22.3
Date: Wed, 08 Sep 2021 01:40:08 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32871@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1335 bytes --]
There is a new pull request by kwshi against master on the void-packages repository
https://github.com/kwshi/void-packages buildah-1.22.3
https://github.com/void-linux/void-packages/pull/32871
buildah: update to 1.22.3
<!-- Mark items with [x] where applicable -->
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/32871.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-buildah-1.22.3-32871.patch --]
[-- Type: text/x-diff, Size: 1031 bytes --]
From 1e7adc3b4303970757f06a74dcb28ac3fe7e0435 Mon Sep 17 00:00:00 2001
From: Kye Shi <shi.kye@gmail.com>
Date: Tue, 7 Sep 2021 14:01:22 -0700
Subject: [PATCH] buildah: update to 1.22.3
---
srcpkgs/buildah/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/buildah/template b/srcpkgs/buildah/template
index 91ddeba3d41c..e79cbca14f89 100644
--- a/srcpkgs/buildah/template
+++ b/srcpkgs/buildah/template
@@ -1,6 +1,6 @@
# Template file for 'buildah'
pkgname=buildah
-version=1.20.1
+version=1.22.3
revision=1
build_style=go
go_import_path=github.com/containers/buildah
@@ -16,7 +16,7 @@ license="Apache-2.0"
homepage="https://github.com/containers/buildah"
changelog="https://github.com/containers/buildah/blob/master/CHANGELOG.md"
distfiles="${homepage}/archive/v${version}.tar.gz"
-checksum=970c326594acf85665640b721d11839fb9701daef3471cd8dd1823ff33b11db2
+checksum=977c7d845c4a767afee8c7004f26654fa970730495e2d3526032615f93e04af4
post_build() {
make -C docs GOMD2MAN=go-md2man
next reply other threads:[~2021-09-07 23:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 23:40 kwshi [this message]
2021-09-10 22:23 ` [PR REVIEW] " paper42
2021-09-15 3:55 ` [PR PATCH] [Updated] " kwshi
2021-09-15 17:54 ` paper42
2021-09-15 21:22 ` CameronNemo
2021-09-16 1:21 ` ericonr
2021-09-23 6:36 ` [PR PATCH] [Updated] " kwshi
2021-09-23 6:56 ` kwshi
2021-09-24 3:48 ` CameronNemo
2021-09-24 8:20 ` [PR PATCH] [Merged]: " paper42
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-32871@inbox.vuxu.org \
--to=kwshi@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).