Hide Forgot
This is part of rebasing GNOME to 3.22.
I've pushed a WIP branch with initial rebase work. Package maintainers, please look over the branch and fix up anything if needed: http://pkgs.devel.redhat.com/cgit/rpms/gnome-bluetooth/log/?h=private-rhel-7.4-rebase
(In reply to Kalev Lember from comment #2) > I've pushed a WIP branch with initial rebase work. Package maintainers, > please look over the branch and fix up anything if needed: > > http://pkgs.devel.redhat.com/cgit/rpms/gnome-bluetooth/log/?h=private-rhel-7. > 4-rebase Any reason why you're removing the gobject-introspection* Requires? +%if 0%{?fedora} +Requires: bluez-obexd +%endif This is wrong, the bluez-obexd sub-package should be in RHEL as well, or it'll break the "receive files" functionality in the Bluetooth Settings panel.
(In reply to Bastien Nocera from comment #3) > Any reason why you're removing the gobject-introspection* Requires? It's just a sync from Fedora where we've been standardizing on using multiple directory ownership for /usr/share/gir-1.0/ and /usr/lib64/girepository-1.0/ directories. Instead of pulling in gobject-introspection for all packages that drop files in those directories, we just list the directories in the packages that ship gir files, as per https://fedoraproject.org/wiki/Packaging:Guidelines#The_directory_is_owned_by_a_package_which_is_not_required_for_your_package_to_function . With this scheme, it's up to for the introspection consumer (gnome-shell in this case) to add 'Requires: gobject-introspection'. > +%if 0%{?fedora} > +Requires: bluez-obexd > +%endif > > This is wrong, the bluez-obexd sub-package should be in RHEL as well, or > it'll break the "receive files" functionality in the Bluetooth Settings > panel. In RHEL, the obexd functionality is in the main 'bluez' package and there's no 'bluez-obexd' subpackage. It's only in Fedora where we have the bluez / bluez-obexd split.
I've now merged the rebase branch and built gnome-bluetooth-3.20.0-1.el7 for the rhel-7.4-gnome build target.
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:2096