[packit] Propose downstream failed for release v1.30.5

[packit-as-a-service]

Packit failed on creating pull-requests in dist-git (https://src.fedoraproject.org/rpms/cri-o.git):

dist-git branch	error
f40	See https://dashboard.packit.dev/results/propose-downstream/10565

You can retrigger the update by adding a comment (/packit propose-downstream) into this issue.

[packit-as-a-service]

Packit failed on creating pull-requests in dist-git (https://src.fedoraproject.org/rpms/cri-o.git):

dist-git branch	error
f39	See https://dashboard.packit.dev/results/propose-downstream/10566

You can retrigger the update by adding a comment (/packit propose-downstream) into this issue.

[saschagrunert]

@cri-o/cri-o-maintainers @lsm5 is there anything we can do to fix that issue?

[lsm5]

@LorbusChris @saschagrunert i guess something is up with fedora-40 package in the packit config. Looks like rawhide pull request was created just fine https://src.fedoraproject.org/rpms/cri-o/pull-request/23 . I'd suggest checking in https://matrix.to/#/#packit:fedora.im .

Also, do you want to ship different versions to each active Fedora release or are you ok with shipping only the latest crio to all Fedora? For the latter case, your packit config can be a lot simpler.

[saschagrunert]

are you ok with shipping only the latest crio to all Fedora

I'd say we can only ship the latest one since various streams are available using the k8s packaging. (cc @cri-o/cri-o-maintainers)

[lsm5]

I'd say we can only ship the latest one since various streams are available using the k8s packaging. (cc @cri-o/cri-o-maintainers)

In that case crio's packit config can be kinda like conmon's packit config.

[github-actions]

A friendly reminder that this issue had no activity for 30 days.