Bug 1668365
Summary: | Please add "xorg-x11-drv-evdev" package to the "Server with GUI" group on RHEL-7 Server | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Jiri Hladky <jhladky> |
Component: | releng | Assignee: | Bohdan Khomutskyi <bkhomuts> |
Status: | CLOSED ERRATA | QA Contact: | Jiri Hladky <jhladky> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 7.6 | CC: | bgollahe, bmilar, dmach, james.antill, jhladky, jmracek, kkolakow, lmusil, salmy |
Target Milestone: | rc | ||
Target Release: | 7.7 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-08-06 11:42:01 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: | |||
Bug Blocks: | 1647087 |
Description
Jiri Hladky
2019-01-22 14:34:46 UTC
This is a change in comps xml, nothing to be done in yum code. Reassigning to releng. Thanks for reassigning BZ to the correct group! You can use repoquery --groupmember xorg-x11-drv-evdev to check to which groups package belongs. Currently (tested on RHEL-7.6 Server) package does not belong to any group: [root@p50 ~]# repoquery --groupmember xorg-x11-drv-evdev xorg-x11-drv-evdev-2.10.6-1.el7.x86_64 Thanks! Jirka Brian, we need a pm_ack. I'm assigning the bug to you. Tested p50.tpb.lab.eng.brq.redhat.com with RHEL-7.7-20190404.n.0 Server. $ repoquery --groupmember xorg-x11-drv-evdev xorg-x11-drv-evdev-2.10.6-1.el7.x86_64 @x11 $ rpm -qa | grep xorg-x11-drv-evdev => no match $ yum groupinstall "Server with GUI" -y $ rpm -qa | grep xorg-x11-drv-evdev xorg-x11-drv-evdev-2.10.6-1.el7.x86_64 It's fixed. Thank you! Jirka Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2351 |