This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2212302 - Need xcb-util-cursor and dev packages in the default RHEL 9 repo
Summary: Need xcb-util-cursor and dev packages in the default RHEL 9 repo
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: distribution
Version: 9.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Olivier Fourdan
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On: 2238281 2238273
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-05 08:41 UTC by cavendish.qi+fedora
Modified: 2023-09-11 15:04 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-11 15:04:52 UTC
Type: Story
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-2991 0 None Migrated None 2023-09-11 15:04:47 UTC
Red Hat Issue Tracker RHELPLAN-158963 0 None None None 2023-06-05 11:16:12 UTC

Description cavendish.qi+fedora 2023-06-05 08:41:05 UTC 
Description of problem: 
There are some (commercial) users who only can access the default RHEL 9 repos, and Qt 6.5 starts to use xcb-util-cursor instead of Xlib/libXcursor, then they can't build and use Qt 6.5 with the packages only from default RHEL 9 repos.

Version-Release number of selected component (if applicable): 0.1.3


How reproducible: consistent


Actual results: There is no xcb-util-cursor in the default RHEL 9 repo.


Expected results: Include xcb-util-cursor in the default RHEL 9 repo.


Additional info: xcb packages(including xcb-util-cursor) should be considered infrastructure packages.
Comment 1 cavendish.qi+fedora 2023-06-05 08:43:23 UTC 
See also the original request in Qt Project, https://bugreports.qt.io/browse/QTBUG-113647 .
Comment 2 Josh Boyer 2023-06-05 11:13:09 UTC 
Red Hat Enterprise Linux 9 does not offer the Qt6 stack, and has no plans to add it at this time.  We would suggest using the EPEL repository for xcb-util-cursor and Qt6.

If a Red Hat Enterprise Linux customer needs Qt6, please file a customer portal case so we can track and manage the request correctly.
Comment 3 Tomas Popela 2023-06-05 11:30:09 UTC 
This request was already pre-approved internally by Carlos and members of sst_gpu.
Comment 5 Carlos Soriano 2023-06-05 12:10:21 UTC 
(In reply to Tomas Popela from comment #3)
> This request was already pre-approved internally by Carlos and members of
> sst_gpu.

Just to clarify Tomas comment, we're open to evaluate inclusion of packages in certain repositories (which ones TBD), but we still need internal discussion after we receive an official request. I think having an official customer request is a good first step, but we still didn't go through the internal evaluation process. Apologies if that was misinterpreted on my side.
Comment 16 RHEL Program Management 2023-09-11 15:04:35 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 17 RHEL Program Management 2023-09-11 15:04:52 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.
Note You need to log in before you can comment on or make changes to this bug.