Re: BlueZ Status in Fedora.

2013-09-12 Thread Rave it
Current status update for MATE. 1. Creating an applet for using gnome-bluetooth inside MATE is a death project for me. The applet himself is working (thanks kalev), but using gnome-blutooth properties is a problem since 'properties' isn't a standalone application anymore and moved to control-ce

Re: BlueZ Status in Fedora.

2013-08-20 Thread Toshio Kuratomi
On Mon, Aug 19, 2013 at 04:03:17AM +0100, Matthew Garrett wrote: > On Sun, Aug 18, 2013 at 02:28:34PM -0700, Ryan Rix wrote: > > > Basically we ship Fedora 20 in a state where one only of our major desktop > > environments supports bluetooth in a stable fashion? That seems kind of > > like a >

Re: BlueZ Status in Fedora.

2013-08-19 Thread Bastien Nocera
project.org: > > > Message: 13 > > Date: Tue, 13 Aug 2013 01:03:20 +0200 > > From: Kalev Lember > > To: devel@lists.fedoraproject.org > > Subject: Re: BlueZ Status in Fedora. > > Message-ID: <520969b8.1030...@gmail.com> > > Content-Type: text/plai

Re: BlueZ Status in Fedora.

2013-08-19 Thread Lars Seipel
On Sun, Aug 18, 2013 at 09:48:46PM -0700, Richard Vickery wrote: > Instead of shipping it, is there a problem with giving it to those on > the developer list and letting us iron out the kinks? Sure, that's what already happens. If you want to help, this thread contains a multitude of pointers wher

Re: BlueZ Status in Fedora.

2013-08-19 Thread Tomasz Torcz
On Mon, Aug 19, 2013 at 08:55:01AM -0700, Adam Williamson wrote: > Have you tried Bluetooth on our major desktop environments in F19? :P > > (I kid, I kid, it mostly works well. But still, I have to pair my mouse > every damn time I want to use it, for instance.) Oh, is https://bugzilla.redhat.

Re: BlueZ Status in Fedora.

2013-08-19 Thread Adam Williamson
On Sun, 2013-08-18 at 14:28 -0700, Ryan Rix wrote: > It sounds like BlueZ5 is not ready for Fedora, betwen the "early alpha" XFCE > code, and shipping git BlueDevil, mate and cinnamon don't appear to work with > it ... We're not even at Alpha TC1 yet, remember. It's not unusual for stuff roadm

Re: BlueZ Status in Fedora.

2013-08-19 Thread Andreas Tunek
On 19/08/2013 4:31 PM, "Richard Vickery" wrote: > > On Sun, Aug 18, 2013 at 8:03 PM, Matthew Garrett wrote: > > On Sun, Aug 18, 2013 at 02:28:34PM -0700, Ryan Rix wrote: > > > >> Basically we ship Fedora 20 in a state where one only of our major desktop > >> environments supports bluetooth in a s

Re: BlueZ Status in Fedora.

2013-08-19 Thread Richard Vickery
On Sun, Aug 18, 2013 at 8:03 PM, Matthew Garrett wrote: > On Sun, Aug 18, 2013 at 02:28:34PM -0700, Ryan Rix wrote: > >> Basically we ship Fedora 20 in a state where one only of our major desktop >> environments supports bluetooth in a stable fashion? That seems kind of like >> a >> disaster wait

Re: BlueZ Status in Fedora.

2013-08-18 Thread Matthew Garrett
On Sun, Aug 18, 2013 at 02:28:34PM -0700, Ryan Rix wrote: > Basically we ship Fedora 20 in a state where one only of our major desktop > environments supports bluetooth in a stable fashion? That seems kind of like > a > disaster waiting to happen. The current release blocking desktops are Gnom

Re: BlueZ Status in Fedora.

2013-08-18 Thread drago01
On Sun, Aug 18, 2013 at 11:28 PM, Ryan Rix wrote: > On Sun 18 August 2013 10:00:22 Kevin Fenzi wrote: >> On Wed, 14 Aug 2013 12:40:54 +0200 >> >> Rave it wrote: >> > I don't see that adding a bluetooth-panel-applet package is easy for >> > mate/xfce/lxde. First tests shows me that the removed pan

Re: BlueZ Status in Fedora.

2013-08-18 Thread Ryan Rix
On Sun 18 August 2013 10:00:22 Kevin Fenzi wrote: > On Wed, 14 Aug 2013 12:40:54 +0200 > > Rave it wrote: > > I don't see that adding a bluetooth-panel-applet package is easy for > > mate/xfce/lxde. First tests shows me that the removed panel code from > > gnome-bluetooth isn't independent from t

Re: BlueZ Status in Fedora.

2013-08-18 Thread Kevin Fenzi
On Wed, 14 Aug 2013 12:40:54 +0200 Rave it wrote: > I don't see that adding a bluetooth-panel-applet package is easy for > mate/xfce/lxde. First tests shows me that the removed panel code from > gnome-bluetooth isn't independent from the the rest of the code. I > quess for this reason the gnome d

Re: BlueZ Status in Fedora.

2013-08-16 Thread Kalev Lember
On 08/17/2013 01:47 AM, "Jóhann B. Guðmundsson" wrote: > Will the bluez-compat be killed in this move? Yes, already gone in the rawhide package: http://pkgs.fedoraproject.org/cgit/bluez.git/commit/?id=e321c716dddf55724776b8686de01cd7f45cbc4a https://bugzilla.redhat.com/show_bug.cgi?id=754523 --

Re: BlueZ Status in Fedora.

2013-08-16 Thread dan . mashal
:19:27 To: Development discussions related to Fedora Reply-To: Development discussions related to Fedora Subject: Re: BlueZ Status in Fedora. On Thu, 2013-08-15 at 15:10 -0700, Dan Mashal wrote: > On Thu, Aug 15, 2013 at 3:04 PM, Dan Mashal wrote: > > On Thu, Aug 15, 2013 at 10:55 AM,

Re: BlueZ Status in Fedora.

2013-08-16 Thread Adam Williamson
On Thu, 2013-08-15 at 15:10 -0700, Dan Mashal wrote: > On Thu, Aug 15, 2013 at 3:04 PM, Dan Mashal wrote: > > On Thu, Aug 15, 2013 at 10:55 AM, Lars Seipel wrote: > >> On Wed, Aug 14, 2013 at 08:37:19PM -0700, Dan Mashal wrote: > >>> Otherwise we are looking at possibly reforking gnome-bluetooth

Re: BlueZ Status in Fedora.

2013-08-16 Thread Jóhann B. Guðmundsson
On 08/13/2013 09:44 AM, Kalev Lember wrote: On 08/13/2013 02:28 PM, Rave it wrote: Other probs are: 1. gnome-bluetooth upstream has removed the fallback icon for autostart in session,...no systray icon in other DE than gnome itself. 2. if gnome revert this change in upstream 'OnlyShowIn=MAT

Re: BlueZ Status in Fedora.

2013-08-16 Thread Matthias Clasen
On Thu, 2013-08-15 at 15:04 -0700, Dan Mashal wrote: > On Thu, Aug 15, 2013 at 10:55 AM, Lars Seipel wrote: > > On Wed, Aug 14, 2013 at 08:37:19PM -0700, Dan Mashal wrote: > >> Otherwise we are looking at possibly reforking gnome-bluetooth at this > >> point in time. > > > > Reforking? And then wa

Re: BlueZ Status in Fedora.

2013-08-15 Thread Dan Mashal
On Thu, Aug 15, 2013 at 3:04 PM, Dan Mashal wrote: > On Thu, Aug 15, 2013 at 10:55 AM, Lars Seipel wrote: >> On Wed, Aug 14, 2013 at 08:37:19PM -0700, Dan Mashal wrote: >>> Otherwise we are looking at possibly reforking gnome-bluetooth at this >>> point in time. >> >> Reforking? And then wait unt

Re: BlueZ Status in Fedora.

2013-08-15 Thread Dan Mashal
On Thu, Aug 15, 2013 at 10:55 AM, Lars Seipel wrote: > On Wed, Aug 14, 2013 at 08:37:19PM -0700, Dan Mashal wrote: >> Otherwise we are looking at possibly reforking gnome-bluetooth at this >> point in time. > > Reforking? And then wait until the bitrot sets in again? ;-) > > Can't you just use gno

Re: BlueZ Status in Fedora.

2013-08-15 Thread Lars Seipel
On Wed, Aug 14, 2013 at 08:37:19PM -0700, Dan Mashal wrote: > Otherwise we are looking at possibly reforking gnome-bluetooth at this > point in time. Reforking? And then wait until the bitrot sets in again? ;-) Can't you just use gnome-bluetooth proper and resurrect the panel icon stuff like Kale

Re: BlueZ Status in Fedora.

2013-08-14 Thread Dan Mashal
On Tue, Aug 13, 2013 at 6:44 AM, Kalev Lember wrote: > On 08/13/2013 02:28 PM, Rave it wrote: >> Other probs are: >> 1. gnome-bluetooth upstream has removed the fallback icon for autostart in >> session,...no systray icon in other DE than gnome itself. >> 2. if gnome revert this change in ups

Re: BlueZ Status in Fedora.

2013-08-14 Thread Rave it
Am Tue, 13 Aug 2013 23:59:15 + schrieb devel-requ...@lists.fedoraproject.org: > - Original Message - > > On 08/02/2013 10:15 AM, Jaroslav Reznik wrote: > > > Let me know - I'd like to have this one as a Change if it's going to F20 > > > > I have been coordinating with various peop

Re: BlueZ Status in Fedora.

2013-08-13 Thread Kalev Lember
On 08/13/2013 08:06 PM, Jaroslav Reznik wrote: > The page looks good, thanks for coordination. Just could you please extend > the scope with resolution for mate bt? Also for contingency plan, I'd like > to see a real deadline - Beta as a point to revert things as a coordination > would be needed. O

Re: BlueZ Status in Fedora.

2013-08-13 Thread Jaroslav Reznik
- Original Message - > On 08/02/2013 10:15 AM, Jaroslav Reznik wrote: > > Let me know - I'd like to have this one as a Change if it's going to F20 > > I have been coordinating with various people and looks like all teams > are go. NetworkManager and PulseAudio changes are slightly lagging

Re: BlueZ Status in Fedora.

2013-08-13 Thread Jaroslav Reznik
- Original Message - > On 08/02/2013 10:15 AM, Jaroslav Reznik wrote: > > Let me know - I'd like to have this one as a Change if it's going to F20 > > I have been coordinating with various people and looks like all teams > are go. NetworkManager and PulseAudio changes are slightly lagging

Re: BlueZ Status in Fedora.

2013-08-13 Thread Kalev Lember
On 08/13/2013 02:28 PM, Rave it wrote: > Other probs are: > 1. gnome-bluetooth upstream has removed the fallback icon for autostart in > session,...no systray icon in other DE than gnome itself. > 2. if gnome revert this change in upstream 'OnlyShowIn=MATE" needs to be > added. > 3. Also runt

Re: BlueZ Status in Fedora.

2013-08-13 Thread Rave it
Am Tue, 13 Aug 2013 12:00:01 + schrieb devel-requ...@lists.fedoraproject.org: > Message: 4 > Date: Tue, 13 Aug 2013 11:26:05 +0200 > From: Kalev Lember > To: Development discussions related to Fedora > > Subject: Re: BlueZ Status in Fedora. > Message-ID: <

Re: BlueZ Status in Fedora.

2013-08-13 Thread Kalev Lember
On 08/13/2013 11:11 AM, Rave it wrote: > mate-bluetooth doesn't support bluez5, and upstream doesn't have started to > port it. > I don't expect that is is ready before f20 alpha or beata. > So it would be very nice not to push bluez5 into f20. > Also Cristofph Wickert asked me to clean up runtime

Re: BlueZ Status in Fedora.

2013-08-13 Thread Rave it
Am Tue, 13 Aug 2013 08:34:53 + schrieb devel-requ...@lists.fedoraproject.org: > Message: 13 > Date: Tue, 13 Aug 2013 01:03:20 +0200 > From: Kalev Lember > To: devel@lists.fedoraproject.org > Subject: Re: BlueZ Status in Fedora. > Message-ID: <520969b8.1030...@gmail.com&

Re: BlueZ Status in Fedora.

2013-08-12 Thread Kalev Lember
On 08/02/2013 10:15 AM, Jaroslav Reznik wrote: > Let me know - I'd like to have this one as a Change if it's going to F20 I have been coordinating with various people and looks like all teams are go. NetworkManager and PulseAudio changes are slightly lagging behind, but it's probably best if we mo

Re: BlueZ Status in Fedora.

2013-08-02 Thread Jaroslav Reznik
- Original Message - > On 08/01/2013 07:36 PM, Peter Robinson wrote: > > I was kind of expecting this would have landed by now though, Bastien > > will be @ GUADEC this week so not sure if he'll respond quickly > > We'll discuss this at GUADEC and I'll follow up here once we figure out > a

Re: BlueZ Status in Fedora.

2013-08-01 Thread Kalev Lember
On 08/01/2013 07:36 PM, Peter Robinson wrote: I was kind of expecting this would have landed by now though, Bastien will be @ GUADEC this week so not sure if he'll respond quickly We'll discuss this at GUADEC and I'll follow up here once we figure out a plan what to do. It's possible that it

Re: BlueZ Status in Fedora.

2013-08-01 Thread Dan Williams
On Thu, 2013-08-01 at 18:36 +0100, Peter Robinson wrote: > On Thu, Aug 1, 2013 at 6:14 PM, Tomasz Torcz wrote: > > On Thu, Aug 01, 2013 at 07:05:39PM +0200, Stefan Held wrote: > >> What exactly is holding the Updates back in Fedora? > >> Is there a reason for excluding the 5.x Series? > > > > > >

Re: BlueZ Status in Fedora.

2013-08-01 Thread Peter Robinson
On Thu, Aug 1, 2013 at 6:14 PM, Tomasz Torcz wrote: > On Thu, Aug 01, 2013 at 07:05:39PM +0200, Stefan Held wrote: >> What exactly is holding the Updates back in Fedora? >> Is there a reason for excluding the 5.x Series? > > > See https://fedoraproject.org/wiki/Changes/Bluez5 > and the thread st

Re: BlueZ Status in Fedora.

2013-08-01 Thread Tomasz Torcz
On Thu, Aug 01, 2013 at 07:05:39PM +0200, Stefan Held wrote: > What exactly is holding the Updates back in Fedora? > Is there a reason for excluding the 5.x Series? See https://fedoraproject.org/wiki/Changes/Bluez5 and the thread starting at https://lists.fedoraproject.org/pipermail/devel/2013