Bug 1746885 - [DTS 9.0 RHEL 7] Enable building with bluetooth headers
Summary: [DTS 9.0 RHEL 7] Enable building with bluetooth headers
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Developer Toolset
Classification: Red Hat
Component: strace
Version: DTS 9.0 RHEL 7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: alpha
: 9.0
Assignee: Eugene Syromiatnikov
QA Contact: Edjunior Barbosa Machado
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-29 12:42 UTC by Eugene Syromiatnikov
Modified: 2019-12-10 07:49 UTC (History)
3 users (show)

Fixed In Version: devtoolset-9-strace-5.1-3.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-10 07:49:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:4135 0 None None None 2019-12-10 07:49:38 UTC

Description Eugene Syromiatnikov 2019-08-29 12:42:46 UTC
There's an unconditional build requirement for pkgconfig(blues) in RHEL 7.8 strace spec file, but for DTS, the spec file is mostly inherited from upstream, where it's conditioned with "0%{?centos} >= 8 || 0%{?rhel} >= 8"; as a result, update from the system version to the DTS version may result in regression in Bluetooth-related decoding capabilities.

Comment 2 Eugene Syromiatnikov 2019-08-29 13:06:54 UTC
Testing notes: if Bluetooth address decoding is enabled, then tests/net-sockaddr.dir/exp and tests/net-sockaddr.dir/log contain lines with "sa_family=AF_BLUETOOTH".

Comment 4 Eugene Syromiatnikov 2019-08-29 15:11:43 UTC
Correction: the headers are needed only for tests after commit v4.23~160, so impact is not severe (no decoding regression, only lack of proper testing).

Comment 7 errata-xmlrpc 2019-12-10 07:49: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, 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/RHEA-2019:4135


Note You need to log in before you can comment on or make changes to this bug.