[skip-ci] test containers-common rpm via packit

[Luap99]

/packit test containers/container-libs#795

[lsm5]

Hmm, the fedora-42 testing-farm job doesn't seem to have installed the rpm from the container-libs PR containers-common-0.68.0~dev-1.20260428163917133560.main.718.ge3b0c9aa78.fc42.noarch . Looking ..

[lsm5]

I suspect it's because containers-common has the ridiculously high Epoch for podman-next builds that overwrites one from the container-libs PR. Suggest retrying with this change:

diff --git a/contrib/packit-tmt/update-deps.sh b/contrib/packit-tmt/update-deps.sh
index dc2d14dc95..d094cb871c 100644
--- a/contrib/packit-tmt/update-deps.sh
+++ b/contrib/packit-tmt/update-deps.sh
@@ -4,4 +4,4 @@ set -exo pipefail

 # This should work even when podman-next isn't installed. It'll fetch the
 # highest versions available across all repos.
-dnf -y upgrade --allowerasing --disable-repo=testing-farm-tag-repository --exclude=podman*
+dnf -y upgrade --allowerasing --disable-repo=testing-farm-tag-repository --exclude=podman* --exclude=containers-common*

That shouldn't upgrade containers-common after setting up podman-next.

[Luap99]

AFAIK last time I did this it worked fine, I think it may have not liked the comment in the PR description, i.e. I see no packit eyes which it normally does

let me try again

[Luap99]

/packit test containers/container-libs#795

[packit-as-a-service]

Cockpit tests failed for commit a191d81. @martinpitt, @jelly, @mvollmer please check.

[Luap99]

looks like this did the trick https://artifacts.dev.testing-farm.io/4cb39ae3-f4d7-4e8e-8dcd-244a1ac06abc/

containers-common-0.68.0~dev-1.20260428143457469173.pr795.718.g676611e43e.fc45.noarch

[Luap99]

/packit test containers/container-libs#795

[packit-as-a-service]

[NON-BLOCKING] Packit jobs failed. @containers/packit-build please check. Everyone else, feel free to ignore.