feat: update podman to 5.3.2+ds1-1

[deepin-community-bot]

This pull request is requested by @UTsweetyfish.

Basic Information

Old Version: 5.2.5-1deepin1
New Version: 5.3.2+ds1-1
Old version may contain dde / deepin patches. Please review more precisely.

Patch series

--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,9 +1,12 @@
 system-goimports.patch
-0002-Revert-update-to-docker-27.patch
-0003-TestProviders-Skip-test-if-unable-to-list-providers.patch
-0004-Use-gopsutil-v4.patch
-0006-test-system-ignore-some-tests-that-are-broken-on-deb.patch
-0006-test-e2e-skip-some-Containerized-checkpoint-tests.patch
-0007-test-update-timezone-checks.patch
-0008-cirrus-update-CI-images.patch
-0009-test-localsystem-skip-test-podman-network-reload.patch
+Revert-to-docker-26.patch
+pkg-machine-platform.patch
+gopsutil-v4.patch
+tests-unit-skips.patch
+tests-system-skips.patch
+tests-integration-skips.patch
+0008-shell-completion-respect-CONTAINERS_REGISTRIES_CONF.patch
+0009-test-system-remove-system-dial-stdio-test.patch
+0010-test-system-CopyDirectory-do-not-chown-files.patch
+0011-test-system-fix-podman-play-build-private-registry-e.patch
+0012-CI-image-volume-test-robustify.patch

[github-actions]

TAG Bot

TAG: 5.3.2+ds1-1
EXISTED: no
DISTRIBUTION: unstable

[deepin-ci-robot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• https:/raw.githubusercontent.com/deepin-community/template-repository/master/debian/deepin/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[deepin-ci-robot]

The following users are mentioned in OWNERS file(s) but are untrusted for the following reasons. One way to make the user trusted is to add them as members of the deepin-community org. You can then trigger verification by writing /verify-owners in a comment.

• l0rd
  • User is not a member of the org. User is not a collaborator. Satisfy at least one of these conditions to make the user trusted.
  • OWNERS