vendor to latest c/{common,image,storage}#5929
vendor to latest c/{common,image,storage}#5929openshift-merge-bot[bot] merged 2 commits intocontainers:mainfrom
Conversation
|
Looks like we need to update Line 974 in eac9331 |
|
@mtrmac Tests are broken, it seems to be from your new code containers/image#2613?! |
That very likely needs an equivalent of containers/podman@5235ee5 ; I’ll take a look and file a PR today. |
| github.com/containers/common v0.61.1-0.20250121185748-34a90afcdc6d | ||
| github.com/containers/image/v5 v5.33.1-0.20250121231649-a45ebe065b9e |
There was a problem hiding this comment.
These are, nominally, downgrades.
For c/image, containers/image#2691 should help.
There was a problem hiding this comment.
They are not downgrades?!
34a90afcdc6d (containers/common@34a90af)
a45ebe065b9e (containers/image@a45ebe0)
These are (or were) commits from the latest main branch at the time I did the vendor. So they are not downgrades if we consider main always to be newest which it must be.
There was a problem hiding this comment.
You’re right that main is newer — it’s just that Go doesn’t know that.
#5932 . |
|
Changes LGTM, looks like you may need to rebase. |
Make sure all the test pass before we do a final vendor dance. Signed-off-by: Paul Holzinger <pholzing@redhat.com>
The c/common defaults were changed to no longer mask this path[1]. As such we need to remove it from this test. [1] containers/common#2278 Signed-off-by: Paul Holzinger <pholzing@redhat.com>
|
@TomSweeneyRedHat @nalind This should be good to merge. Then we can vendor buildah@main on the podman side |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Luap99, nalind The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Make sure all the test pass before we do a final vendor dance.
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?