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 2119126 - [RHEL8.6] Wireshark source rpm fails to build due to looking for incorrect libssh header files.
Summary: [RHEL8.6] Wireshark source rpm fails to build due to looking for incorrect li...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: wireshark
Version: 8.6
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Michal Ruprich
QA Contact: František Hrdina
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-17 15:38 UTC by Brandon Clark
Modified: 2022-11-08 11:11 UTC (History)
14 users (show)

Fixed In Version: wireshark-2.6.2-15.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-08 10:03:34 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-131350 0 None None None 2022-08-17 15:48:04 UTC
Red Hat Product Errata RHBA-2022:7663 0 None None None 2022-11-08 10:03:36 UTC

Description Brandon Clark 2022-08-17 15:38:46 UTC 
Description of problem:

RHEL 8.5 and RHEL 8.6 both have wireshark version 2.6.2-14 as their latest. In RHEL 8.5, you are able to successfully build the source rpm. In RHEL 8.6, however, this rpmbuild fails when looking for the following in the BUILDROOT:

usr/lib64/wireshark/extcap/sshdump
usr/lib64/wireshark/extcap/ciscodump

The cu this listing is being opened for noted that, if you rename all occurrences of 'libssh.h' to 'libssh_version.h' in cmake/modules/FindLIBSSH.cmake, the build completes. Speaking with senior backline support engineers, they mentioned that there was a rebasing of libssh in 8.6.

Version-Release number of selected component (if applicable):
wireshark-2.6.2-14.el8.src.rpm

How reproducible:
Consistently in RHEL 8.6.

Steps to Reproduce:
1. Download Source RPM.
2. Gather build dependencies from main and CodeReady Builder repos.
3. 'rpm -ivh' on the source rpm.
4. Attempt to build RPM. Compilation will get near the very end before errors output regarding the two files listed in the problem description.

Actual results:
Errors outputted regarding 'sshdump' and 'ciscodump'.

Expected results:
Successful compilation of the wireshark source rpm.
Comment 1 Michal Ruprich 2022-08-18 11:29:57 UTC 
Interesting, I thought these kinds of things would have been caught in the time when developing RHEL-8.6. Nevertheless, I am not aware of any conversation or announcement of changes of headers in libssh(please refer me to one if there was one that I missed). Changing headers in the middle of RHEL-X development does not sound like a good idea and if the owner of the library has very good reasons for it, he/she should notify everyone involved. Meaning everyone using the library, simple dnf query could help.

This breakage was not caused by wireshark since this package has not been touched since RHEL-8.5.0 so I am reassigning this to libssh. Either this should have been communicated properly or a compat solution should have been created.
Comment 2 Jakub Jelen 2022-08-23 16:01:33 UTC 
Sounds like this is a side-effect of the changes in libssh header files structure and splitting the version information to separate file (to prevent bumping the version on several places for each release). These changed do not have any functional difference, but it looks like it confuses naive cmake modules in wireshark.

The wireshark has this already fixed in upstream. We do not plan to introduce any backward compatibility in libssh side so I would suggest the customer to try the following patch for wireshark and probably suggest to backport it also in the wireshark, if you will be doing some update in the future.

https://github.com/wireshark/wireshark/commit/fd7739de6bc679036c02c7aabbc3f71783751e3d
Comment 3 areis 2022-08-23 18:03:46 UTC 
I have already implemented my own patch that is functionally identical to the patch upstream you linked. Just please be aware that the latest version of the wireshark source RPM from Red Hat will not build due to this.
Comment 4 Michal Ruprich 2022-08-24 06:21:14 UTC 
I think you missed the point from comment #1 here Jakube. I know about the fix from upstream and the naivety of the wireshark check is not what is discussed here. The point is that you introduced a change in headers and did not bother to inform those who are involved. This could have been fixed in RHEL-8.6.0 together with the change in libssh. This will probably result in an unnecessary z-stream errata if the customer wants this fixed in 8.6.0.

Make sure that if you make a change like this in the future, at least make a simple dnf query to check whether this could influence someone else.
Comment 14 errata-xmlrpc 2022-11-08 10:03:34 UTC 
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 (wireshark bug fix and enhancement update), 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-2022:7663
Note You need to log in before you can comment on or make changes to this bug.