Bug 2208516

Summary:	Rebase CMake to version 3.26 or higher
Product:	Red Hat Enterprise Linux 9	Reporter:	Neal Gompa <ngompa13>
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:	brandon.johnson, bstinson, davide, jwboyer, michel, mroche, sipoyare
Target Milestone:	rc	Keywords:	MigratedToJIRA, 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:
Clones:	2208522 (view as bug list)		Environment:
Last Closed:	2023-09-22 16:40:04 UTC	Type:	Component Upgrade
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Neal Gompa 2023-05-19 11:00:08 UTC

Description of problem:
Please upgrade CMake to the latest version (3.26 at this time).

The request for a newer CMake is triggered by the need for the following features:

* Support for C17/C18 (introduced in CMake 3.21)
* Support for os-release(5) for OS identification data (introduced in CMake 3.22)
* Support for CUDA 20 and nvxt3 (introduced in 3.25)
* Support for Python's stable application binary interface (introduced in 3.26)
* Support for Perl5 in SWIG (introduced in 3.26)

Version-Release number of selected component (if applicable):
3.20.2-8.el9

Comment 1 Neal Gompa 2023-05-19 11:31:03 UTC

Merge request proposed: https://gitlab.com/redhat/centos-stream/rpms/cmake/-/merge_requests/11

Comment 4 RHEL Program Management 2023-09-22 16:39:33 UTC

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.

Comment 5 RHEL Program Management 2023-09-22 16:40:04 UTC

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.