Why rpm dependencies conflict is not stopping the build
In my
rpm-ostree module I wanted to remove some package without knowing they were needed by other packages. This leads to error while resolving dependencies at build time. Somehow the build in the CI was successful and I rebased without being aware of these conflicts. I would like to know if this behavior is on purpose or not.
Here is a link to the action log (line 3355) : https://github.com/benoitlx/custom-desktop-image/actions/runs/10683413026/job/29611427107GitHub
fix: adding pop-launcher and removing unused system extension · ben...
Custom Linux Desktop Image build on top of fedora atomic - powered by BlueBuild - fix: adding pop-launcher and removing unused system extension · benoitlx/custom-desktop-image@f26291f
6 Replies
Hmm, that should fail. I did make some changes so that we could get some better visual indicators that a module failed. I wonder if I missed something. I'll take a look today
Yup, made a bash mistake
Pushing the fix now
Solution
Here's the build https://github.com/blue-build/cli/actions/runs/10685440781
When the
build step finishes, you should be good to go. It's the unstable_cli for a reason lolGitHub
fix: Make build fail if module fails · blue-build/cli@4634f40
BlueBuild's command line program that builds custom Fedora Atomic images based on your recipe.yml - fix: Make build fail if module fails · blue-build/cli@4634f40
Thanks for catching it
Thanks a lot for fixing it 🙃
Not a problem!