Bug 1993424

Summary: gnome-settings-daemon: incomplete disabling of subman plugin
Product: Red Hat Enterprise Linux 8 Reporter: Carl George 🤠 <carl>
Component: gnome-settings-daemonAssignee: Kalev Lember <klember>
Status: CLOSED MIGRATED QA Contact: Jiri Koten <jkoten>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: CentOS StreamCC: bstinson, feborges, jwboyer, tpelka, tpopela
Target Milestone: betaKeywords: MigratedToJIRA
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-15 16:54:19 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:
Attachments:
Description Flags
Disable subman plugin on CentOS none

Description Carl George 🤠 2021-08-13 02:07:51 UTC 
Description of problem:
In bug 1827030 changes were made to the gnome-settings-daemon spec file to disable the subman plugin when built on CentOS.  Later, the subman plugin patches were removed entirely.  Then, they were added back, but the subman conditionals were only partially brought back.  This results in CentOS having to modify the spec file [0] before building to make the conditionals work correctly.  Please add the CentOS modifications to the RHEL spec file so that it can be built directly without modification.


Version-Release number of selected component (if applicable):
gnome-settings-daemon-3.32.0-15.el8


Additional info:
[0] https://git.centos.org/rpms/gnome-settings-daemon/c/c29cb92fc2f5343fbce87265cceac56f2d173fcd?branch=c8s
Comment 2 Carl George 🤠 2021-10-19 18:28:29 UTC 
Created attachment 1834740 [details]
Disable subman plugin on CentOS
Comment 3 Carl George 🤠 2021-10-19 18:30:05 UTC 
With the addition of Patch50017 and Patch60001, an upper limit must now be set on %autopatch.  I've updated the CentOS modification to do this, and attached a patch file for the same that can be applied to the RHEL spec file.
Comment 6 RHEL Program Management 2023-09-15 16:52:25 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 7 RHEL Program Management 2023-09-15 16:54:19 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.