Package: bluez Version: 5.17-1~exp0 Severity: wishlist We're currently in the processes move transitioning gnome 3.12 into unstable (a few big transitions are ongoing, further are planned to complete later on). As mentioned on #732453, starting with 3.12 gnome only supports bluez 5.
Furthermore as bluez 4 has been deprecated for some time now, there are now several devices around that simply don't work with it but do work with bluez 5. For jessie it would be good to at least have bluez 5 be available if not be used as the default for Debian. Which obviously as a first step need to have bluez 5 transition to unstable. Given it's a pretty massive transition (involving e.g. all the desktops), the thinking at the Debian gnome sprint was it would probably be best (as a temporary solution) to have both bluez 5 and bluez 4 in unstable and conflicting (so only one can be installed at any one time). In that way packages can transition at their own time instead of requiring the whole distribution in one go. Would it be possible to do such a strategy in a reasonable timeframe so the transition and testing can happen with a good amount of time left before the Jessie freeze? -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bluez depends on: ii dbus 1.8.0-3 ii init-system-helpers 1.18 ii kmod 16-2 ii libc6 2.18-4 ii libdbus-1-3 1.8.0-3 iu libglib2.0-0 2.40.0-3 ii libreadline6 6.3-6 ii libudev1 204-9 ii lsb-base 4.1+Debian12 ii udev 204-9 bluez recommends no packages. bluez suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
