Skip to content
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

[CI:BUILD] Packit: remove pre-sync action #4926

Merged
merged 1 commit into from Jul 17, 2023

Conversation

lsm5
Copy link
Member

@lsm5 lsm5 commented Jul 14, 2023

The pre-sync action constantly breaks and is currently not possible to reliably test until the subsequent upstream release due to limitations in packit.

The lines being added by the action script to the downstream Fedora spec were only meant to keep Fedora happy. But given that they provide no tangible benefit as github notifies us of security issues in libraries mentioned in go.mod and go.sum, along with redhat prodsec's own magic for creating security alerts, there's absolutely no point to having the pre-sync action run and add a layer of uncertainty.

This commit removes the pre-sync action and
rpm/update-spec-provides.sh.

Ref: containers/podman#19232

[NO NEW TESTS NEEDED]

What type of PR is this?

/kind other

What this PR does / why we need it:

simplifies downstream Fedora packaging task

How to verify it

doesn't affect upstream. will be verified once we publish the next upstream buildah release.

Which issue(s) this PR fixes:

None

Special notes for your reviewer:

None

Does this PR introduce a user-facing change?

None

The pre-sync action constantly breaks and is currently not possible to
reliably test until the subsequent upstream release due to limitations
in packit.

The lines being added by the action script to the downstream Fedora spec
were only meant to keep Fedora happy. But given that they provide
no tangible benefit as github notifies us of security
issues in libraries mentioned in go.mod and go.sum, along with redhat
prodsec's own magic for creating security alerts, there's absolutely
no point to having the pre-sync action run and add a layer of uncertainty.

This commit removes the pre-sync action and
`rpm/update-spec-provides.sh`.

Ref: containers/podman#19232

[NO NEW TESTS NEEDED]

Signed-off-by: Lokesh Mandvekar <lsm5@fedoraproject.org>
@lsm5
Copy link
Member Author

lsm5 commented Jul 17, 2023

/packit copr-build

@rhatdan
Copy link
Member

rhatdan commented Jul 17, 2023

/approve
/lgtm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 17, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lsm5, rhatdan

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot merged commit 8aa4d36 into containers:main Jul 17, 2023
23 checks passed
@lsm5
Copy link
Member Author

lsm5 commented Aug 9, 2023

/cherry-pick release-1.31

@openshift-cherrypick-robot

@lsm5: #4926 failed to apply on top of branch "release-1.31":

Applying: Packit: remove pre-sync action
Using index info to reconstruct a base tree...
M	rpm/buildah.spec
M	rpm/update-spec-provides.sh
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): rpm/update-spec-provides.sh deleted in Packit: remove pre-sync action and modified in HEAD. Version HEAD of rpm/update-spec-provides.sh left in tree.
Auto-merging rpm/buildah.spec
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Packit: remove pre-sync action
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-1.31

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 8, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants