Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
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:
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
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
(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)
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.
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