Bug 2117934
| Summary: | Please include libappindicator-devel in codeready-builder repo | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Markus Muckhoff <markus.muckhoff> |
| Component: | libappindicator | Assignee: | -RETIRED- <erack> |
| Status: | CLOSED WONTFIX | QA Contact: | Tomas Pelka <tpelka> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | CentOS Stream | CC: | pholica, tpelka, tpopela |
| Target Milestone: | rc | Keywords: | Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| 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: | 2022-08-29 11:57:42 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: | |||
| Deadline: | 2022-08-29 | ||
|
Description
Markus Muckhoff
2022-08-12 18:23:23 UTC
libappindicator-devel is needed as dependency for building xpad in epel8 (ticket #2041567) This ticket has been filed due to a comment from Davide Cavalca in ticket #2117860 @markus.muckhoff This may be a misunderstanding. RHEL-8 ships only libappindicator-gtk3-12.10.0-19, no libappindicator-12.10.0-19. Only RHEL-9 introduced an additional libappindicator-12.10.0-29 with accompanying libappindicator-devel-12.10.0-29. May it be you just need libappindicator-gtk3-devel-12.10.0-19 that is already in CRB? For example libappindicator-gtk3-devel-12.10.0-19.el8.x86_64.rpm (In reply to Eike Rathke from comment #9) > @markus.muckhoff > This may be a misunderstanding. RHEL-8 ships only > libappindicator-gtk3-12.10.0-19, no libappindicator-12.10.0-19. > Only RHEL-9 introduced an additional libappindicator-12.10.0-29 with > accompanying libappindicator-devel-12.10.0-29. > May it be you just need libappindicator-gtk3-devel-12.10.0-19 that is > already in CRB? > For example libappindicator-gtk3-devel-12.10.0-19.el8.x86_64.rpm I know what's going on here and I'm here the one to "blame". First let me mention that: libappindicator = source package libappindicator = package built from libappindicator source package providing gtk2 support libappindicator-python2-appindicator = package built from libappindicator source package providing gtk2 and python2 support libappindicator-gtk3 = package built from libappindicator source package providing gtk3 support (doesn't depend on libappindicator package) libappindicator-sharp = package built from libappindicator source package providing Mono support When RHEL 8 was being developed we were not interested in having libappindicator (and any of its dependencies) in RHEL 8 as we had no use for them in the OS, but Google Chrome required the libappindicator3.so.1 (https://bugs.chromium.org/p/chromium/issues/detail?id=799144): $ rpm -qpR google-chrome-stable-66.0.3359.181-1.x86_64.rpm | grep app libappindicator3.so.1()(64bit) that was provided by the libappindicator-gtk3 package of the libappindicator source package. As we had to disable the python2 support and we were not interested in gtk2 bits and also no Mono stack in RHEL, we've decided to import that libappindicator source package into RHEL 8 and just build and ship libappindicator-gtk3(-devel) from it (in retrospective we should rather introduce it as a libappindicator-gtk3 source package and just don't build it in EPEL) and remove everything else, see https://git.centos.org/rpms/libappindicator/blob/c8/f/SPECS/libappindicator.spec - I made a small mistake that I left the libappindicator-devel subpackage definition there, but as it had no %files section it didn't produce any packages. So my suggestion for getting the libappindicator with gtk2 support into EPEL 8 is to package it there (i.e. using the libappindicator-gtk2 source package name) and build the gtk2 bits from it - there is nothing that we can do about it from RHEL's side. Thank you for clarifying things and sorry for the late reply. I am very busy at the moment and have been trying to understand what this package is all about before responding to the questions in this thread. I will copy your reply to the appropriate ticket #2117860 |