-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[packit] Propose downstream failed for release v4.6.0-rc2 #19232
Labels
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
stale-issue
Comments
ughhhh I think I will just get rid of that action script. Building manually. |
lsm5
added a commit
to lsm5/podman
that referenced
this issue
Jul 14, 2023
The pre-sync action constantly breaks and is hard to test. The lines being added by it downstream were only mean to keep Fedora happy. But given that they provide no tangible benefit as security teams look at go.mod and go.sum, there's absolutely no point to having the action run and break constantly. This commit removes the pre-sync action and `rpm/update-spec-provides.sh`. Ref: containers#19232 Signed-off-by: Lokesh Mandvekar <lsm5@fedoraproject.org>
lsm5
added a commit
to lsm5/podman
that referenced
this issue
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#19232 [NO NEW TESTS NEEDED] Signed-off-by: Lokesh Mandvekar <lsm5@fedoraproject.org>
lsm5
added a commit
to lsm5/skopeo
that referenced
this issue
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 Signed-off-by: Lokesh Mandvekar <lsm5@fedoraproject.org>
lsm5
added a commit
to lsm5/buildah
that referenced
this issue
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] Signed-off-by: Lokesh Mandvekar <lsm5@fedoraproject.org>
This was referenced Jul 14, 2023
lsm5
added a commit
to lsm5/aardvark-dns
that referenced
this issue
Jul 14, 2023
It is currently not possible to reliably test the job-specific pre-sync action 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, 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
added a commit
to lsm5/netavark
that referenced
this issue
Jul 14, 2023
It is currently not possible to reliably test the job-specific pre-sync action 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, 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>
openshift-cherrypick-robot
pushed a commit
to openshift-cherrypick-robot/podman
that referenced
this issue
Jul 17, 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#19232 [NO NEW TESTS NEEDED] Signed-off-by: Lokesh Mandvekar <lsm5@fedoraproject.org>
lsm5
added a commit
to lsm5/skopeo
that referenced
this issue
Jul 20, 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 Signed-off-by: Lokesh Mandvekar <lsm5@fedoraproject.org> (cherry picked from commit a4aa15f) Signed-off-by: Lokesh Mandvekar <lsm5@fedoraproject.org>
lsm5
added a commit
to lsm5/buildah
that referenced
this issue
Aug 9, 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] Signed-off-by: Lokesh Mandvekar <lsm5@fedoraproject.org> (cherry picked from commit 9cc5d5e) Signed-off-by: Lokesh Mandvekar <lsm5@fedoraproject.org>
lsm5
added a commit
to lsm5/buildah
that referenced
this issue
Aug 9, 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] Signed-off-by: Lokesh Mandvekar <lsm5@fedoraproject.org> (cherry picked from commit 9cc5d5e) Signed-off-by: Lokesh Mandvekar <lsm5@fedoraproject.org>
A friendly reminder that this issue had no activity for 30 days. |
This has been fixed. Podman v4.6.1 on Fedora was handled by Packit. |
github-actions
bot
added
the
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
label
Nov 13, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
stale-issue
Packit failed on creating pull-requests in dist-git (https://src.fedoraproject.org/rpms/podman.git):
f37
f38
rawhide
You can retrigger the update by adding a comment (
/packit propose-downstream
) into this issue.The text was updated successfully, but these errors were encountered: