-
Notifications
You must be signed in to change notification settings - Fork 785
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
[release-1.33] Fixes Listing tags in JFrog Artifactory may fail #5631
[release-1.33] Fixes Listing tags in JFrog Artifactory may fail #5631
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: TomSweeneyRedHat 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 |
Ephemeral COPR build failed. @containers/packit-build please check. |
Addresses the problem first described in containers/skopeo#2346 Also addresses: https://issues.redhat.com/browse/RHEL-40802 and https://issues.redhat.com/browse/RHEL-40799 [NO NEW TESTS NEEDED] Signed-off-by: tomsweeneyredhat <[email protected]>
As the title says, bumping to v1.33.9 to incorporate the JFrog fix. [NO NEW TESTS NEEDED] Signed-off-by: tomsweeneyredhat <[email protected]>
7ef1729
to
c56554e
Compare
@lsm5 I've just pushed the button to rerun the tests again, is there anything else I can do to cure the packet errors here? |
the current packit targets are stale. Ignore them. If we absolutely need packit to pass here, we'll need to use the right targets. |
@edsantiago @lsm5 I hit a Docker rate limit now on this, and prior, we'd run into Packit issues. Any advice on how we can move this along? We need it for the Jira cards above. |
/lgtm |
a77bd8e
into
containers:release-1.33
Addresses the problem first described in containers/skopeo#2346
Also addresses: https://issues.redhat.com/browse/RHEL-40802 and
https://issues.redhat.com/browse/RHEL-40799
Then bump to Buildah v1.33.9
What type of PR is this?
What this PR does / why we need it:
How to verify it
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?