Upstream tag: v4.6.2
Upstream commit: 5db42e86
If you need to do any change in this pull request, you need to locally fetch the source branch of it and push it (with a fix) to your fork (as it is not possible to push to the branch created in the Packit’s fork):
```
git fetch https://src.fedoraproject.org/forks/packit/rpms/podman.git refs/heads/*:refs/remotes/packit/*
git checkout packit/4.6.2-rawhide-update-propose_downstream
```
Upstream tag: v4.6.1
Upstream commit: f3069b3f
If you need to do any change in this pull request, you need to locally fetch the source branch of it and push it (with a fix) to your fork (as it is not possible to push to the branch created in the Packit’s fork):
```
git fetch https://src.fedoraproject.org/forks/packit/rpms/podman.git refs/heads/*:refs/remotes/packit/*
git checkout packit/4.6.1-rawhide-update-propose_downstream
```
Upstream tag: v4.6.0
Upstream commit: 38e6fab9
If you need to do any change in this pull request, you need to locally fetch the source branch of it and push it (with a fix) to your fork (as it is not possible to push to the branch created in the Packit’s fork):
```
git fetch https://src.fedoraproject.org/forks/packit/rpms/podman.git refs/heads/*:refs/remotes/packit/*
git checkout packit/4.6.0-rawhide-update-propose_downstream
```
Fixes flake: 'dial tcp: lookup cdn03.quay.io: no such host'
Okay, doesn't actually fix as in _fix_, just fix as in "sweep it
under the rug". The actual bug is in systemd-resolved, or in the
quay.io/cloudflare.net DNS nameservers, or in the weird specific
setup for cdn03 (it's a CNAME, compared to cdn01/02 which are A).
Maybe a combination of all of the above. I don't care; I just
want the flakes gone. I realize that this makes our testing
environment different from default Fedora, and am okay with
that because I suspect many Fedora users disable systemd-resolved
as SOP.
Signed-off-by: Ed Santiago <santiago@redhat.com>
Testing Farm 2023-03.1 has updated to a new Ansible
version.
Unfortunately, playbooks using the deprecated `warn:`
parameter for the shell/command modules will fail
because this had been deprecated
This should fix the problem.
Signed-off-by: Miroslav Vadkerti <mvadkert@redhat.com>
A new change soon to be merged upstream will leave the buildroot macro
in /usr/bin/docker in the rpmbuild process.
This commit will sanitize the buildroot macro from /usr/bin/docker.
Signed-off-by: Lokesh Mandvekar <lsm5@fedoraproject.org>
