Hello community,

here is the log from the commit of package bluez for openSUSE:Factory checked 
in at 2014-02-25 16:41:17
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/bluez (Old)
 and      /work/SRC/openSUSE:Factory/.bluez.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "bluez"

Changes:
--------
--- /work/SRC/openSUSE:Factory/bluez/bluez.changes      2013-12-31 
16:47:08.000000000 +0100
+++ /work/SRC/openSUSE:Factory/.bluez.new/bluez.changes 2014-02-25 
16:41:18.000000000 +0100
@@ -1,0 +2,26 @@
+Sat Feb 22 10:31:52 UTC 2014 - [email protected]
+
+- update to version 5.15:
+  * Fix issue with LE enabling and background scanning.
+  * Fix issue with HID over GATT input device name.
+  * Fix issue with storage of slave long term keys.
+  * Add support for handling identity resolving keys.
+  * various android features (not relevant for us)
+- minor specfile tweaks to avoid some rpmlint warnings
+- permissions of some bluez-test files changes to please rpmlint
+
+-------------------------------------------------------------------
+Thu Jan 23 10:43:53 UTC 2014 - [email protected]
+
+- Update to version 5.14:
+  * Fix issue with marking PS3 controllers as trusted.
+  * Fix issue with authorization of PS3 controllers.
+  * Add support for DualShock 4 controller detection.
+  * Add support for legacy pairing emulation.
+  * Add support for secure simple pairing emulation.
+  * Add support for automated pairing testing.
+  * Add support for RFCOMM protocol testing.
+  * Add support for HCI controller testing.
+- Add "bluemoon" configuration tool
+
+-------------------------------------------------------------------
@@ -21,0 +48,5 @@
+
+-------------------------------------------------------------------
+Wed Dec  4 13:44:23 UTC 2013 - [email protected]
+
+- add bluez-5.11-logitech-hid2hci.patch, (bnc#681049; bnc#850478)

Old:
----
  bluez-5.13.tar.xz

New:
----
  bluez-5.11-logitech-hid2hci.patch
  bluez-5.15.tar.xz

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ bluez.spec ++++++
--- /var/tmp/diff_new_pack.xAZtpe/_old  2014-02-25 16:41:19.000000000 +0100
+++ /var/tmp/diff_new_pack.xAZtpe/_new  2014-02-25 16:41:19.000000000 +0100
@@ -1,8 +1,8 @@
 #
 # spec file for package bluez
 #
-# Copyright (c) 2013 SUSE LINUX Products GmbH, Nuernberg, Germany.
-# Copyright (c) 2010-2013 B1 Systems GmbH, Vohburg, Germany
+# Copyright (c) 2014 SUSE LINUX Products GmbH, Nuernberg, Germany.
+# Copyright (c) 2010-2014 B1 Systems GmbH, Vohburg, Germany
 #
 # All modifications and additions to the file contributed by third parties
 # remain the property of their copyright owners, unless otherwise agreed
@@ -24,7 +24,7 @@
 BuildRequires:  systemd-devel
 BuildRequires:  pkgconfig(dbus-1) >= 1.4
 %{?systemd_requires}
-Version:        5.13
+Version:        5.15
 Release:        0
 Summary:        Bluetooth Stack for Linux
 License:        GPL-2.0+
@@ -35,6 +35,8 @@
 Source6:        README.SUSE
 Source7:        bluetooth.modprobe
 Source99:       README.packagers
+# fix some logitech HID devices, bnc#681049, bnc#850478 
[email protected]
+Patch1:         bluez-5.11-logitech-hid2hci.patch
 Patch2:         bluez-sdp-unix-path.patch
 BuildRequires:  alsa-devel
 BuildRequires:  automake
@@ -90,7 +92,6 @@
 Summary:        CUPS Driver for Bluetooth Printers
 License:        GPL-2.0+
 Group:          Hardware/Printing
-#Requires:       libbluetooth3 = %{version}
 
 %description cups
 Contains the files required by CUPS for printing to Bluetooth-connected
@@ -102,7 +103,6 @@
 License:        GPL-2.0+ and MIT
 Group:          Development/Tools/Debuggers
 Requires:       dbus-1-python
-#Requires:       libbluetooth3 = %{version}
 Requires:       python-gobject2
 
 %description test
@@ -111,6 +111,7 @@
 
 %prep
 %setup -q
+%patch1 -p1
 %patch2 -p1
 cp %{SOURCE6} .
 mkdir dbus-apis
@@ -152,6 +153,10 @@
 rm %{buildroot}%{_prefix}/lib/systemd/user/obex.service
 # end FIXME
 
+# rpmlint warnings...
+cd %{buildroot}%{_libdir}/bluez/test
+chmod 0644 *.py *.xml *.dtd
+
 %check
 %if ! 0%{?qemu_user_space_build}
 make check
@@ -184,6 +189,7 @@
 %files
 %defattr(-, root, root)
 %doc AUTHORS COPYING ChangeLog README README.SUSE dbus-apis
+%{_bindir}/bluemoon
 %{_bindir}/hcitool
 %{_bindir}/l2ping
 %{_bindir}/rfcomm
@@ -211,9 +217,6 @@
 %doc %{_mandir}/man1/ciptool.1.gz
 %doc %{_mandir}/man1/rfcomm.1.gz
 %doc %{_mandir}/man1/rctest.1.gz
-#%dir %{_sysconfdir}/bluetooth
-#%config(noreplace) %{_sysconfdir}/bluetooth/main.conf
-#%config(noreplace) %{_sysconfdir}/bluetooth/rfcomm.conf
 %config %{_sysconfdir}/dbus-1/system.d/bluetooth.conf
 %dir %{_localstatedir}/lib/bluetooth
 %dir %{_sysconfdir}/modprobe.d

++++++ bluez-5.11-logitech-hid2hci.patch ++++++
Apparently some Logitech devices need different rules.
https://bugzilla.novell.com/show_bug.cgi?id=681049
https://bugzilla.novell.com/show_bug.cgi?id=850478

Index: b/tools/hid2hci.rules
===================================================================
--- a/tools/hid2hci.rules
+++ b/tools/hid2hci.rules
@@ -9,11 +9,13 @@ SUBSYSTEM!="usb*", GOTO="hid2hci_end"
 ATTR{bInterfaceClass}=="03", ATTR{bInterfaceSubClass}=="01", 
ATTR{bInterfaceProtocol}=="02", \
   ATTRS{bDeviceClass}=="00", ATTRS{idVendor}=="413c", 
ATTRS{bmAttributes}=="e0", \
   RUN+="hid2hci --method=dell --devpath=%p", ENV{HID2HCI_SWITCH}="1"
 
 # Logitech devices
-KERNEL=="hiddev*", ATTRS{idVendor}=="046d", 
ATTRS{idProduct}=="c70[345abce]|c71[34bc]", \
+KERNEL=="hiddev*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c70[5e]", \
+  RUN+="hid2hci --method=logitech-hid --devpath=%p"
+KERNEL=="hidraw*", ATTRS{idVendor}=="046d", 
ATTRS{idProduct}=="c70[34abc]|c71[34bc]", \
   RUN+="hid2hci --method=logitech-hid --devpath=%p"
 
 ENV{DEVTYPE}!="usb_device", GOTO="hid2hci_end"
 
 # When a Dell device recovers from S3, the mouse child needs to be repoked
++++++ bluez-5.13.tar.xz -> bluez-5.15.tar.xz ++++++
++++ 59457 lines of diff (skipped)

-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to