Bug 1401501

Summary: bluez package should either bluez-obexd or bluez-obexd should be split to separate rpm
Product: Red Hat Enterprise Linux 7 Reporter: David Jaša <djasa>
Component: bluezAssignee: David Arcari <darcari>
Status: CLOSED ERRATA QA Contact: Ken Benoit <kbenoit>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: darcari, jshortt, tpelka
Target Milestone: rc   
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: 2017-08-01 23:14:58 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:
Bug Depends On:    
Bug Blocks: 1353018    

Description David Jaša 2016-12-05 12:50:22 UTC
Description of problem:
unlike Fedora with bluez-obexd in separate package, el7's blues-obexd is distributed in main package. The main package doesn't however Provide bluez-obexd:
# rpm -ql bluez | grep obex
/usr/lib/systemd/user/obex.service
/usr/libexec/bluetooth/obexd
/usr/share/dbus-1/services/org.bluez.obex.service
# dnf info bluez-obexd
Error: No matching Packages to list
[root@cihla ~]# dnf provides bluez-obexd
Error: No Matches found

so some packages depending on bluez's obexd require different dependencies than on Fedora with no "real" reason.

Version-Release number of selected component (if applicable):
bluez-5.41-1.el7.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Don Zickus 2016-12-05 15:37:08 UTC
Hi,

Yes, the original thought was to not add the additional package and break
an end-users setup.

My concern is if I separate the package as you request, the customer
will do an 'yum update bluez' and lose the ability to do an 'obex'
file transfer unless they manually run 'yum install bluez-obexd'.
Not a good idea.

I can add a dependency on bluez to also install bluez-obexd, but
that would make things different from Fedora.  Though the Fedora
soultion isn't ideal as everyone complains about it.


So I am thinkig of splitting the package out and adding a dependency,
which should fix your problem?  Meanwhile I will have to figure out
the Fedora situation and perhaps backport that to RHEL.

Thoughts?

Cheers,
Don

Comment 3 Don Zickus 2016-12-05 19:00:11 UTC
Ah, good suggestion.  I think so.  Should be easy to implement and test.

Do you have a particular package that has this explicit Requires that I can
verify with?

Cheers,
Don

Comment 4 David Jaša 2016-12-05 23:21:28 UTC
(In reply to Don Zickus from comment #3)
> Ah, good suggestion.  I think so.  Should be easy to implement and test.
> 
> Do you have a particular package that has this explicit Requires that I can
> verify with?
> 
> Cheers,
> Don

rebuild of Fedora's gnome-user-share (which needs mod_dnssd), both rebuilt using mock (mock --rebuild mod_dnssd.src.rpm ; mock --clean ; mock -i mod_dnssd.rpm ; mock --no-clean --rebuild gnome-user-share.src.rpm)

Comment 7 Ken Benoit 2017-04-11 16:28:37 UTC
Tested on a system with RHEL-7.4-20170410.n.3 installed.

# yum provides bluez-obexd
Loaded plugins: product-id, search-disabled-repos, subscription-manager
This system is not registered with an entitlement server. You can use subscription-manager to register.
bluez-5.44-2.el7.x86_64 : Bluetooth utilities
Repo        : beaker-Workstation
Matched from:
Provides    : bluez-obexd

Marking as verified.

Comment 8 errata-xmlrpc 2017-08-01 23:14:58 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/RHBA-2017:2209