Chris Evich
Chris Evich
> Do we actually need that? (mlocate) Git blame says it came in by 38fa0c65 which is incredibly ancient. However, the origin of that change was exclusive to podman CI....
Note: I re-ran a few container build tasks. Looks like quay or networking flakes.
> This is not code touched by this PR. Agreed, this is unrelated. Must be the result of a `git` fix/update. I'll take a look and work on this today,...
Well...was an easy fix but hard to find the right place to implement. Local testing shows I found it, so https://github.com/containers/automation_images/pull/356 should fix this.
Done. Okay, rebase this and it should work :crossed_fingers:
@mtrmac Ed's second suggestion (unfortunately) isn't abnormal for this repo. If you're at all uncomfortable making that change, poke me and I'll take care of it for you. Edit: It...
I'd like to suggest something helpful, but I'm out of my depth here. Debugging problems in the "base" stage build can be challenging. It's not possible to use `hack/get_ci_vm.sh` to...
Since you're going to be building images in the other PR right away anyway (with a newer IMG_SFX) maybe it's okay to just force-merge this?
Oh! You could stick '[skip-ci]' in the title, and re-push. That will 100% bypass all of Cirrus-CI.