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

[Nobuhiro Iwamatsu]

Hi, again.

# I added Jordi Mallach, Laurent Bigonville and Christopher Schramm
(blueman maintainer)  to CC.

I want to talk about bluez5 transition on this BTS. OK?

Although it is in the present situation,
 - bluez5 is already contained in expeirmental.
 - gnome-bluetooth by which bluez5 was supported is in experimental by
Laurent Bigonville. (Thanks!)
 - bluedevil by which bluez5 was supported is also in experimental.
 - blueman which bluez4 and bluez5 were both supported is in unstable.

We have an important package required since it already transition in
experimental.
We need to move them to unstable.

An order which I consider is as follows.
1. upload to bluez5 to unstable.
     NOTE: I think that we does not need binary transition, because
bluez5 ABI of library does not change
                   from bluez4 to bluez5.
2. if accepted bluez5, upload gnome-bluetooth and bluedevil.
3. (or 2?) upload other package what depends bluez5.

Since I did not know the state of other packages yet, I wrote simply.
Would you give me an opinion?

Best regards,
  Nobuhiro

2014-06-12 8:27 GMT+09:00 Nobuhiro Iwamatsu <iwamatsu at nigauri.org>:
> Hi,
>
> Sorry, reply was late.
>
> 2014-05-16 1:16 GMT+09:00 Didier 'OdyX' Raboud <odyx at debian.org>:
>> 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.
>
> Thanks for upload!
>
>>
>> [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.
>
> Yes,  However, adjustment with big DE is difficult.
>
>>
>>> 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.
>>
>
> Yes, I think too. I can already upload bluez5 to unstable as bluez part.
> Is bluedevil  2.0~rc1-1 working with bluez5? Can I upload bluze5 to
> unstable by KDE part?
> Of course, I will also ask Gnome team about this.
>
> Best regards,
>   Nobuhiro
>
> --
> Nobuhiro Iwamatsu
>    iwamatsu at {nigauri.org / debian.org}
>    GPG ID: 40AD1FA6
>
> _______________________________________________
> Pkg-bluetooth-maintainers mailing list
> Pkg-bluetooth-maintainers at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-bluetooth-maintainers



-- 
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6