Debian Patches

Status for podman/5.3.2+ds1-1

Patch Description Author Forwarded Bugs Origin Last update
system-goimports.patch system-goimports
===================================================================
Debian Go Packaging Team <pkg-go-maintainers@lists.alioth.debian.org> no 2024-07-12
Revert-to-docker-26.patch Revert "update to docker 27"
This reverts commit e24367aa14b7669d116a2a27ba12c69cbf51612b.
Reinhard Tartler <siretart@tauware.de> no 2024-08-07
pkg-machine-platform.patch TestProviders: Skip test if unable to list providers
this is to fix autopkgtest in Debian when running in qemu
Reinhard Tartler <siretart@tauware.de> no 2024-08-09
gopsutil-v4.patch Do not hardcode gopsutil v4

We can use v4 when no version suffix is used. Remove it so that we can
upgrade the gopsutil modules from v3 to v4 in Debian.
Guillem Jover <gjover@sipwise.com> not-needed 2024-10-01
tests-unit-skips.patch TestUnitDirs: Skip when CLONE_NEWUSER fails Reinhard Tartler <siretart@tauware.de> no 2024-11-13
tests-system-skips.patch test/system: Skip some system tests that fail in Debian Reinhard Tartler <siretart@tauware.de> no 2024-10-03
tests-integration-skips.patch e2e-test: Skip tests that don't currently work
These failures need to be investigated more closely
Reinhard Tartler <siretart@tauware.de> no 2024-11-28
0008-shell-completion-respect-CONTAINERS_REGISTRIES_CONF.patch shell completion: respect CONTAINERS_REGISTRIES_CONF

Found in debian testing where by default there are no unqualified search
registries installed. As such the test failed as the FIXME said. Now
there is no need for the test to assume anything.

Instead set our own config via CONTAINERS_REGISTRIES_CONF then we can
do exact matches, except that env was not read in the shell completion
code so move some code around to make it read the var in the same way as
podman login/logout.
Paul Holzinger <git@holzinger.dev> yes 2024-12-17
0009-test-system-remove-system-dial-stdio-test.patch test/system: remove system dial-stdio test

This test a pretty much useless, it checks that a connection attempt on
the default socket fails. But this is incorrect as the socket is outside
of the test control as such it might be ready to accept connections as
thus the test can fail locally or as reported here in the debian tests.

Given that a simple connection fails does not add any value I opted to
remove it.

Fixes #24803
Paul Holzinger <git@holzinger.dev> yes 2024-12-17
0010-test-system-CopyDirectory-do-not-chown-files.patch test/system: CopyDirectory() do not chown files

If the source dir is owned by another user then the test the chown will
fail assuming we run the tests rootless. This function is only used by
the quadlet tests and for the purpose all we need is to read the files
so the simple fix is remove the chown as this should make the tests pass
on the special debian gating env.

Fixes #24802
Paul Holzinger <git@holzinger.dev> yes 2024-12-17
0011-test-system-fix-podman-play-build-private-registry-e.patch test/system: fix "podman play --build private registry" error

When running this test on a system without unqualifiedsearch registries
it will fail with a different error causing the test to fail. to avoid
that case define our own registries.conf that defines quay.io as
registry. This should make the test pass in the debian env.
Paul Holzinger <git@holzinger.dev> yes 2024-12-17
0012-CI-image-volume-test-robustify.patch CI: --image-volume test: robustify

Test is failing on 1mt because of differences between 'stat'
command output and /proc/mounts. Solution: compare stat %t
(hex filesystem type), not %T (human-readable). This should
match no matter what kernel version or version of stat on
host/container.
Ed Santiago <santiago@redhat.com> yes 2024-11-19

All known versions for source package 'podman'

Links