[Pkg-bluetooth-maintainers] Bug#746078: Please provide bluez 5 in unstable

[Didier 'OdyX' Raboud]

Dear Bluetooth maintainers,

I would like to emphasize Sjoerd's point:

Le dimanche, 27 avril 2014, 15.07:45 Sjoerd Simons a écrit :
> 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.

For what is worth, as I mentioned on debian-devel [0], KDE can be made 
ready for Bluez5 with two straightforward uploads of new upstream 
versions of {lib,}bluedevil. I plan to upload these in coordination with 
their respective maintainers to experimental in the next days.

[0] https://lists.debian.org/debian-devel/2014/05/msg00076.html

> 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.

I'm rather leaning towards deprecating Bluez4 as early as possible, but 
that's really up to you to decide.

> 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?

Having Bluez5 in Jessie would be nice, to say the least.

Cheers,
OdyX