Project

General

Profile

action #75235

container image devel:openQA:ci/base is unresolvable with "nothing provides this-is-only-for-build-envs needed by cmake-mini"

Added by okurz 3 months ago. Updated 3 months ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
Start date:
2020-10-24
Due date:
% Done:

0%

Estimated time:

Description

Observation

container image devel:openQA:ci/base in https://build.opensuse.org/package/show/devel:openQA:ci/base is unresolvable with "nothing provides this-is-only-for-build-envs needed by cmake-mini", probably caused by #69154 and okurz switching the base OS config from openSUSE Leap 15.1 to openSUSE Leap 15.2

Impact

Likely we need this container in os-autoinst but not anymore in openQA but os-autoinst then could fail eventually

Suggestions

Research what the error message means, potentially ask in IRC e.g. [#opensuse-factory](irc://chat.freenode.net/opensuse-factory) or mailing lists


Related issues

Related to openQA Project - action #69154: Improve package and base OS version support: Bump versions to Leap 15.2Resolved2020-07-21

History

#1 Updated by okurz 3 months ago

  • Related to action #69154: Improve package and base OS version support: Bump versions to Leap 15.2 added

#2 Updated by mkittler 3 months ago

  • Assignee set to mkittler

#3 Updated by mkittler 3 months ago

I tried adding Prefer: cmake-full to https://build.opensuse.org/projects/devel:openQA:ci/prjconf as suggested on IRC. So far it doesn't seem to make a difference but maybe it just takes a while until dependencies are recomputed (triggering services didn't help).

If it doesn't work we can still workaround the issue by adding cmake-full explicitly in the Dockerfile. That seems to work for the branch within my home project: https://build.opensuse.org/package/show/home:mkittler:branches:devel:openQA:ci/base

#4 Updated by mkittler 3 months ago

  • Status changed from Workable to Resolved

Fixed on the level of the 15.2 template project by adrianS_. So the container is now resolvable again and I changed our project config to how it was before.

#5 Updated by okurz 3 months ago

awesome! This is like the third issue where adrianS helped with problems I have seen today :)

Also available in: Atom PDF