Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] podman: update to 3.2.3.
Date: Tue, 10 Aug 2021 20:49:20 +0200	[thread overview]
Message-ID: <20210810184920.HZNRLZV06HmMuu1lBBPhpaCFXL5TiEpjVjSbXcLKORM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32270@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1591 bytes --]

There is an updated pull request by ericonr against master on the void-packages repository

https://github.com/daniel-eys/void-packages podman
https://github.com/void-linux/void-packages/pull/32270

podman: update to 3.2.3.
<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### 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
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
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/32270.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-podman-32270.patch --]
[-- Type: text/x-diff, Size: 2110 bytes --]

From a37c47a24641feac65f541a76d8095dd9b2d4ff0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Daniel=20Ey=C3=9Fer?= <daniel.eysser@gmail.com>
Date: Sat, 31 Jul 2021 15:22:09 +0200
Subject: [PATCH] podman: update to 3.2.3.

By ericonr:
- remove INSTALL.msg, it's been 4 months since the change
- add changelog
---
 srcpkgs/podman/INSTALL.msg | 15 ---------------
 srcpkgs/podman/template    |  5 +++--
 2 files changed, 3 insertions(+), 17 deletions(-)
 delete mode 100644 srcpkgs/podman/INSTALL.msg

diff --git a/srcpkgs/podman/INSTALL.msg b/srcpkgs/podman/INSTALL.msg
deleted file mode 100644
index d9090de158e7..000000000000
--- a/srcpkgs/podman/INSTALL.msg
+++ /dev/null
@@ -1,15 +0,0 @@
-`fuse-overlayfs` has been added as a runtime dependency to podman.
-podman will now prefer this storage driver to the `vfs` fallback driver.
-If you have existing containers that rely on the `vfs` driver, podman
-will display an error and refuse any further operation.
-
-To switch to the new storage driver, podman has to be reset:
-
-    # podman system reset
-
-To instead keep using the `vfs` driver, add
-
-    [storage]
-    driver="vfs"
-
-to `/etc/containers/storage.conf` or `~/.config/containers/storage.conf`.
diff --git a/srcpkgs/podman/template b/srcpkgs/podman/template
index 5808c7122ae7..6db65f96cffa 100644
--- a/srcpkgs/podman/template
+++ b/srcpkgs/podman/template
@@ -1,6 +1,6 @@
 # Template file for 'podman'
 pkgname=podman
-version=3.2.2
+version=3.2.3
 revision=1
 build_style=go
 go_import_path="github.com/containers/podman/v3"
@@ -13,8 +13,9 @@ short_desc="Simple management tool for containers and images"
 maintainer="Cameron Nemo <cnemo@tutanota.com>"
 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=70f70327be96d873c83c741c004806c0014ea41039e716545c789b4393184e79
+checksum=ddb8a83d21d2f496512914820525b4c959ff0902d48caaf93a005854a9069b59
 
 if [ "$CROSS_BUILD" ]; then
 	go_build_tags+=" containers_image_openpgp"

  reply	other threads:[~2021-08-10 18:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-31 13:29 [PR PATCH] " daniel-eys
2021-08-10 18:49 ` ericonr [this message]
2021-08-10 18:55 ` [PR PATCH] [Merged]: " ericonr

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=20210810184920.HZNRLZV06HmMuu1lBBPhpaCFXL5TiEpjVjSbXcLKORM@z \
    --to=ericonr@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).