-
Notifications
You must be signed in to change notification settings - Fork 17
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
Fix dnf update installing netavark/aardvark-dns #149
Conversation
The netavark & aardvark-dns binaries should _never_ be present in the netavark CI images for testing. However, the packages are needed to ensure dependencies are properly handled. Since CI runtime will take care of installing or building the binaries, just remove the on-disk files referenced by the packages. Signed-off-by: Chris Evich <[email protected]>
Signed-off-by: Chris Evich <[email protected]>
force-push: Fixed permission-denied problem. |
Cirrus CI build successful. Image ID |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Try using VM image from containers/automation_images#149 Signed-off-by: Aditya R <[email protected]>
I see some failures in |
shouldn't we install packages from podman-next copr instead? EDIT: s/pull/install. |
I'm thinking this:
That way we can perhaps get rid of build_cross targets altogether and also not worry about curling zips or tarballs. |
hmm, installing packages here would mean the image would need to get built continuously to test with the latest commits merged upstream? Maybe any package installation from the copr should actually be done in the individual repos and not here? |
Yes, and good on you for observing this. Yes, we want the stuff being tested to come from builds in the PR and/or be very recent builds from podman-next (for dependencies). Otherwise, for the basic environment stuff that doesn't need to be updated constantly, it should be pre-installed in the images. |
Ugh, I need to go manually trudging through the tasks and pull out image Id's, need to update that bot. So looks like:
|
Ref: containers/automation_images#140 and containers/automation_images#149 Signed-off-by: Chris Evich <[email protected]>
Note: Fedora-35 is disabled due to missing golang 1.18 Ref: containers/automation_images#140 and containers/automation_images#149 and containers/automation_images#146 Signed-off-by: Chris Evich <[email protected]>
Note: Fedora-35 is disabled due to missing golang 1.18 Ref: containers/automation_images#140 and containers/automation_images#149 and containers/automation_images#146 Signed-off-by: Chris Evich <[email protected]>
Note: Fedora-35 is disabled due to missing golang 1.18 Ref: containers/automation_images#140 and containers/automation_images#149 and containers/automation_images#146 Signed-off-by: Chris Evich <[email protected]>
These packages should never be pre-installed in the CI images for
testing in the netavark & aardvark-dns repositories. Ensure they aren't
brought in by a package update in addition to the install.
Signed-off-by: Chris Evich [email protected]