-
Notifications
You must be signed in to change notification settings - Fork 127
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RPM: Remove crio #524
RPM: Remove crio #524
Conversation
cri-o dirs will be owned by the cri-o package Fixes: containers#517 Signed-off-by: Lokesh Mandvekar <[email protected]>
All of our official downstream envs that build from this spec file support autochangelog so we don't need these conditionals. CentOS Stream 9 builds with this spec file are only on the podman-next COPR, so removing these conditionals is no big deal. Signed-off-by: Lokesh Mandvekar <[email protected]>
@saschagrunert @haircommander do we need the |
@lsm5 I don't think so. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IIUC this meets the packaging requirements, namely not to touch %{_libexecdir}/crio
, which is owned by crio. If the podman tests still pass, which from the discussion we seem confident they will, this looks good to me.
Could you please point to the exact |
PTAL. |
Sorry, this was just my hand-wavy assumption that they must exist somewhere and will be executed here. I believe the primary concern about this change is that it could break podman (but we don't believe it will because podman is using a different conmon binary). I did notice that there appear to be some podman tests in the Fedora repo here: https://src.fedoraproject.org/rpms/conmon/blob/rawhide/f/tests. I don't know what they do, though. |
Ack. I guess we can leave TMT enablement and cirrus removal for another PR. This PR should be good to go. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@haircommander PTAL
Awesome, thanks! @lsm5 Any idea which version of Fedora this is likely to land in? |
@saschagrunert @haircommander is it worth cutting a new conmon for this? If not, I can add it manually. |
To reiterate my use case: I cannot switch to the k8s cri-o packages until I update my base OS (Fedora CoreOS) to a release including this change. |
@mdbooth updates created https://bodhi.fedoraproject.org/updates/?search=conmon . |
yeah we could cut a new version, I also see you've patched the RPM which I'm fine with |
No description provided.