On 08/14/2013 06:29 PM, Than Ngo wrote:
> it's effected in KDE (libbluedevil). someone is working on this, but
> it's not expected the bluez5 support will be ready for F20!
>
> So f21 is Ok as goal, but f20 is definitely to early for KDE!
I brought this up at a KDE meeting [1] last month and Kevi
Am Freitag, 21. Juni 2013, 17:16:09 schrieben Sie:
> 2013-05-06 11:13, Peter Robinson skrev:
> > On Mon, May 6, 2013 at 8:35 AM, Bastien Nocera wrote:
> >> Heya,
> >>
> >> In Fedora 20, we'll be using BlueZ 5.x to manage Bluetooth devices.
> >>
> >> Bluez5 uses a D-Bus API that's not compatible
On Fri, Jun 21, 2013 at 5:29 PM, Bastien Nocera wrote:
> On Fri, 2013-06-21 at 17:16 +0200, Kalev Lember wrote:
>> 2013-05-06 11:13, Peter Robinson skrev:
>> > On Mon, May 6, 2013 at 8:35 AM, Bastien Nocera wrote:
>> >> Heya,
>> >>
>> >> In Fedora 20, we'll be using BlueZ 5.x to manage Bluetooth
On Fri, 2013-06-21 at 17:16 +0200, Kalev Lember wrote:
> 2013-05-06 11:13, Peter Robinson skrev:
> > On Mon, May 6, 2013 at 8:35 AM, Bastien Nocera wrote:
> >> Heya,
> >>
> >> In Fedora 20, we'll be using BlueZ 5.x to manage Bluetooth devices.
> >>
> >> Bluez5 uses a D-Bus API that's not compatibl
2013-05-06 11:13, Peter Robinson skrev:
> On Mon, May 6, 2013 at 8:35 AM, Bastien Nocera wrote:
>> Heya,
>>
>> In Fedora 20, we'll be using BlueZ 5.x to manage Bluetooth devices.
>>
>> Bluez5 uses a D-Bus API that's not compatible with Bluez4[1] and as
>> such, management applications and a number
- Original Message -
> On Mon, 2013-05-06 at 10:08 -0400, Josh Boyer wrote:
> > On Mon, May 6, 2013 at 3:35 AM, Bastien Nocera wrote:
> > > Heya,
> > >
> > > In Fedora 20, we'll be using BlueZ 5.x to manage Bluetooth devices.
> >
> > So your Subject says this is a Feature, yet there's no
On Mon, 2013-05-06 at 10:08 -0400, Josh Boyer wrote:
> On Mon, May 6, 2013 at 3:35 AM, Bastien Nocera wrote:
> > Heya,
> >
> > In Fedora 20, we'll be using BlueZ 5.x to manage Bluetooth devices.
>
> So your Subject says this is a Feature, yet there's no link to a
> Feature page. I can't find one
On Mon, 2013-05-06 at 09:35 +0200, Bastien Nocera wrote:
> Heya,
>
> In Fedora 20, we'll be using BlueZ 5.x to manage Bluetooth devices.
>
> Bluez5 uses a D-Bus API that's not compatible with Bluez4[1] and as
> such, management applications and a number of libraries and daemons will
> need to be
On Mon, May 6, 2013 at 3:35 AM, Bastien Nocera wrote:
> Heya,
>
> In Fedora 20, we'll be using BlueZ 5.x to manage Bluetooth devices.
So your Subject says this is a Feature, yet there's no link to a
Feature page. I can't find one in the wiki either, and I know this
hasn't gone through FESCo.
Ca
On Mon, 2013-05-06 at 10:13 +0100, Peter Robinson wrote:
> On Mon, May 6, 2013 at 8:35 AM, Bastien Nocera wrote:
> > Heya,
> >
> > In Fedora 20, we'll be using BlueZ 5.x to manage Bluetooth devices.
> >
> > Bluez5 uses a D-Bus API that's not compatible with Bluez4[1] and as
> > such, management ap
On Mon, May 6, 2013 at 10:38 AM, Roberto Ragusa wrote:
> On 05/06/2013 11:13 AM, Peter Robinson wrote:
>> On Mon, May 6, 2013 at 8:35 AM, Bastien Nocera wrote:
>
>>> For GNOME 3.10 (due September 2013), Gustavo Padovan and I are going to
>>> be porting gnome-bluetooth, NetworkManager and PulseAud
On Mon, May 6, 2013 at 11:38 AM, Roberto Ragusa wrote:
>>> Bluez4 and Bluez5 are not parallel-installable, and incompatible, so
>>> other applications relying on Bluez4 will need to be ported by their
>>> respective maintainers.
>
> Impact on KDE?
>
Probably not much as the upstream developers ar
On 05/06/2013 11:13 AM, Peter Robinson wrote:
> On Mon, May 6, 2013 at 8:35 AM, Bastien Nocera wrote:
>> For GNOME 3.10 (due September 2013), Gustavo Padovan and I are going to
>> be porting gnome-bluetooth, NetworkManager and PulseAudio to BlueZ5.
>> Packages for BlueZ5 will be available as soon
On Mon, May 6, 2013 at 8:35 AM, Bastien Nocera wrote:
> Heya,
>
> In Fedora 20, we'll be using BlueZ 5.x to manage Bluetooth devices.
>
> Bluez5 uses a D-Bus API that's not compatible with Bluez4[1] and as
> such, management applications and a number of libraries and daemons will
> need to be port
Heya,
In Fedora 20, we'll be using BlueZ 5.x to manage Bluetooth devices.
Bluez5 uses a D-Bus API that's not compatible with Bluez4[1] and as
such, management applications and a number of libraries and daemons will
need to be ported.
For GNOME 3.10 (due September 2013), Gustavo Padovan and I are
15 matches
Mail list logo
