From: AnInternetTroll <AnInternetTroll@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] podman: update to 5.0.2.
Date: Wed, 24 Apr 2024 18:28:19 +0200 [thread overview]
Message-ID: <20240424162819.F349D216A9@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49936@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 670 bytes --]
There is an updated pull request by AnInternetTroll against master on the void-packages repository
https://github.com/AnInternetTroll/void-packages user/luca/podman
https://github.com/void-linux/void-packages/pull/49936
podman: update to 5.0.2.
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86\_64-glibc)
Tested locally with an nginx image (plus netavark and passt).
The tests failed locally for me when compiling for i686, but passed for
x86\_64-glibc and x86\_64-musl
A patch file from https://github.com/void-linux/void-packages/pull/49936.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-user/luca/podman-49936.patch --]
[-- Type: text/x-diff, Size: 1963 bytes --]
From 397ac71e66b6465576ee2fbcdfaaaf7fe492d5f8 Mon Sep 17 00:00:00 2001
From: Luca Matei Pintilie <luca@lucamatei.com>
Date: Sat, 20 Apr 2024 18:38:43 +0200
Subject: [PATCH] podman: update to 5.0.2.
---
srcpkgs/podman/template | 18 ++++++++++++++----
1 file changed, 14 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/podman/template b/srcpkgs/podman/template
index 2d96648e291fb2..e11f13ea583d15 100644
--- a/srcpkgs/podman/template
+++ b/srcpkgs/podman/template
@@ -1,12 +1,12 @@
# Template file for 'podman'
pkgname=podman
-version=4.9.3
+version=5.0.2
revision=1
build_style=go
-go_import_path="github.com/containers/podman/v4"
+go_import_path="github.com/containers/podman/v5"
go_package="${go_import_path}/cmd/podman ${go_import_path}/cmd/rootlessport"
go_build_tags="seccomp apparmor containers_image_ostree_stub"
-hostmakedepends="pkg-config go-md2man python3"
+hostmakedepends="pkg-config go-md2man python3 mdocml"
makedepends="gpgme-devel libseccomp-devel device-mapper-devel libbtrfs-devel"
depends="runc conmon cni-plugins slirp4netns fuse-overlayfs
containers-common containers.image containers.storage"
@@ -16,16 +16,26 @@ 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=37afc5bba2738c68dc24400893b99226c658cc9a2b22309f4d7abe7225d8c437
+checksum=85c3f70a1c293ccf48907d8e9fe13c6c9aac67242525a539296beeef31ba11a8
if [ "$CROSS_BUILD" ]; then
go_build_tags+=" containers_image_openpgp"
fi
+case $XBPS_TARGET_MACHINE in
+ aarch64* | x86_64*) ;;
+ *) make_check="no" ;; # Upstream only supports tests on aarch64 and x86_64
+esac
+
post_build() {
make docs
}
+do_check() {
+ make .install.ginkgo
+ make localunit
+}
+
post_install() {
vmkdir usr/libexec/podman
mv "${DESTDIR}/usr/bin/rootlessport" "${DESTDIR}/usr/libexec/podman/rootlessport"
prev parent reply other threads:[~2024-04-24 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-20 16:41 [PR PATCH] " AnInternetTroll
2024-04-24 16:28 ` AnInternetTroll [this message]
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=20240424162819.F349D216A9@inbox.vuxu.org \
--to=aninternettroll@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).