From: daniel-eys <daniel-eys@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] podman: update to 4.4.3.
Date: Tue, 28 Mar 2023 00:40:33 +0200 [thread overview]
Message-ID: <20230327224033.vz1HcJmXiXvownjQPtPGmLM2Ue0FDazSsT0VzLHvHJw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43030@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]
There is an updated pull request by daniel-eys against master on the void-packages repository
https://github.com/daniel-eys/void-packages podman
https://github.com/void-linux/void-packages/pull/43030
podman: update to 4.4.3.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- 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/43030.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-podman-43030.patch --]
[-- Type: text/x-diff, Size: 1097 bytes --]
From c87c625b406d1cbf62e1ef6540d7d32e5f56ffbc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Daniel=20Ey=C3=9Fer?= <daniel.eysser@gmail.com>
Date: Fri, 24 Mar 2023 00:59:25 +0100
Subject: [PATCH] podman: update to 4.4.4.
---
srcpkgs/podman/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/podman/template b/srcpkgs/podman/template
index 0c7265f3dfb0..fe7785423fb8 100644
--- a/srcpkgs/podman/template
+++ b/srcpkgs/podman/template
@@ -1,6 +1,6 @@
# Template file for 'podman'
pkgname=podman
-version=4.4.0
+version=4.4.4
revision=1
build_style=go
go_import_path="github.com/containers/podman/v4"
@@ -16,7 +16,7 @@ license="Apache-2.0"
homepage="https://podman.io/"
changelog="https://raw.githubusercontent.com/containers/podman/main/RELEASE_NOTES.md"
distfiles="https://github.com/containers/podman/archive/v${version}.tar.gz"
-checksum=4bb966fd960b0aae05181e30672a6b20be365225758110eb251b81214414cb25
+checksum=2dacfe7041b83e2cb05fda58bd1fbdae61348a427f5b9073b96b36154de894a1
if [ "$CROSS_BUILD" ]; then
go_build_tags+=" containers_image_openpgp"
next prev parent reply other threads:[~2023-03-27 22:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 16:38 [PR PATCH] " daniel-eys
2023-03-27 22:40 ` daniel-eys [this message]
2023-03-28 3:41 ` podman: update to 4.4.4 CameronNemo
2023-03-28 7:45 ` daniel-eys
2023-03-28 18:56 ` CameronNemo
2023-03-29 7:51 ` [PR PATCH] [Updated] " daniel-eys
2023-03-29 7:53 ` daniel-eys
2023-03-30 16:38 ` [PR PATCH] [Merged]: podman: update to 4.4.4, including dependency stack update 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=20230327224033.vz1HcJmXiXvownjQPtPGmLM2Ue0FDazSsT0VzLHvHJw@z \
--to=daniel-eys@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).