Bug 2139909
Summary: | cmake: 3.20.2-4 throws ninja: error: dependency cycle: src/ceph-volume/setup.py -> src/ceph-volume/setup.py | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | Kaleb KEITHLEY <kkeithle> |
Component: | cmake | Assignee: | Tom Stellard <tstellar> |
Status: | CLOSED MIGRATED | QA Contact: | qe-baseos-tools-bugs |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | CentOS Stream | CC: | besser82, bstinson, extras-qa, jreznik, jwboyer, rdieter, sipoyare, tbaeder, trpost, walter.pete |
Target Milestone: | rc | Keywords: | MigratedToJIRA, Reopened, Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | 2059188 | Environment: | |
Last Closed: | 2023-09-22 16:34:07 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 2057738, 2059188, 2079833 | ||
Bug Blocks: | 2081479 |
Description
Kaleb KEITHLEY
2022-11-03 19:20:52 UTC
> +++ This bug was initially created as a clone of Bug #2059188 +++
That bug and this one are different though, right?
I don't think we have a real cmake expert unfortunately (and if Tom is, he is out for the rest of the year).
It does sound like cmake is at fault here (since an upgrade fixes the problem), but is this really the first
ceph build since that cmake package hit the buildroot? Serge pushed the update mid-2021.
Can you work around the problem by switching back to make files instead?
Is this still an issue? (In reply to Tom Stellard from comment #2) > Is this still an issue? Yes, it's still an issue. Builds still fail in cmake using the cmake from appstream. Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |