[PATCH] update sysutils/podman from 5.1.1 to 5.2.5

[osa]

Summary

Hi,

here's the patch to update sysutils/podman from 5.1.1 to 5.2.5. The upstream has been updated with two patches, so those can be safely removed.

Test Plan

Apply the patch.

% poudriere -j 142amd64 -p default -t sysutils/podman
% pkg install podman-5.2.5.pkg
% sudo podman version
Client:       Podman Engine
Version:      5.2.5
API Version:  5.2.5
Go Version:   go1.21.13
Git Commit:   bd09768e3a85d72f3c5a1a7ea70bef498b0154b8-dirty
Built:        Wed Dec  4 09:42:14 2024
OS/Arch:      freebsd/amd64
% sudo podman run --rm --os=linux alpine cat /etc/os-release | head -1
NAME="Alpine Linux"
% uname -spr
FreeBSD 14.2-RELEASE amd64

[osa]

Here's the update from 5.1.1 to 5.3.1.

[osa]

Update the pkg-plist.

[osa]

Something is broken with v5.3.1 - when I try to pull the alpine image from the docker.io registry it fails:

% podman -v
podman version 5.3.1
% sudo podman pull --os=linux alpine                               
Resolved "alpine" as an alias (/var/cache/containers/short-name-aliases.conf)
Trying to pull docker.io/library/alpine:latest...
Getting image source signatures
Error: copying system image from manifest list: partial pull of blob sha256:da9db072f522755cbeb85be2b3f84059b70571b229512f1571d9217b77e1087f: format not supported on this system

[osa]

Revert back to update to 5.2.5.

[dfr]

Thanks for working on this. In the past, I have usually tried to update all the podman-suite ports as a group, mainly to make sure that manpages shared by podman and buildah (which live in sysutils/containers-common) don't get stale. On the other hand, I don't think there is any harm upgrading podman and buildah separately - I can follow up with containers-common later.

Lets go ahead with v5.2.5 and I will figure out what is going on with v5.3.