Re: BlueZ Status in Fedora.
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-center. In result a user needs to install control-center and deps which is totally worse. 2. after vacation time MATE upstream has decided to port mate-bluetooth to bluez5 which will come for MATE-1.8 maybe and of the year or later. This means for f20 MATE won't support bluetooth. We will obsolete mate-bluetooth for the moment to avoid bug reports about this and re-activate it if it is ported to bluez5 during the release cycle of f20 and for f21. 3. A user of MATE desktop can use bluedevil from KDE for f20, which seems to be well working inside MATE. Bluedevil has also a systray applet. It would be very nice to mention this in f20 release notes. 4. From my personal side i won't block bluez5 for f20 Wolfgang -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
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 disaster waiting to happen. The current release blocking desktops are Gnome and KDE. If those are broken then F20 doesn't ship - if they're working, it ships. It'd be unfortunate to ship a release that doesn't support the non-blocking desktops, but (right now) it's fundamentally up to them to provide the development effort to ensure that they have a full feature set. Actually, due to this Change being submitted after the deadline, this isn't 100% true in this case. Fesco approved the Change like this: Bluez5 (nirik, 18:54:28) * AGREED: approve bluez5 landing now -- if the other alternate desktop envs agree to not be blocking, they do not need to be fixed in order for the feature to stay in. If they don't we'll need to see that they can get bluez5 support in time for F20 or evaluate whether to trigger the contingency plan. (+7,0) (nirik, 19:09:11) At the meeting, nirik expressed the opinion that xfce could ship in Fedora 20 without working bluetooth but he couldn't speak for the other desktop environments. The other exnivronments need to decide whether they can (A) get some working code that works with the new bluetooth stack or (B) are okay with possibly not shipping with working bluetooth support. If they can't and are not then this Change may need to activate its contingency plan. -Toshio pgpBq17PQnF2j.pgp Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
On Sun, Aug 18, 2013 at 8:03 PM, Matthew Garrett mj...@srcf.ucam.org 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 waiting to happen. The current release blocking desktops are Gnome and KDE. If those are broken then F20 doesn't ship - if they're working, it ships. It'd be unfortunate to ship a release that doesn't support the non-blocking desktops, but (right now) it's fundamentally up to them to provide the development effort to ensure that they have a full feature set. -- Matthew Garrett | mj...@srcf.ucam.org -- Instead of shipping it, is there a problem with giving it to those on the developer list and letting us iron out the kinks? -- Richard -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
On 19/08/2013 4:31 PM, Richard Vickery richard.vicker...@gmail.com wrote: On Sun, Aug 18, 2013 at 8:03 PM, Matthew Garrett mj...@srcf.ucam.org 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 waiting to happen. The current release blocking desktops are Gnome and KDE. If those are broken then F20 doesn't ship - if they're working, it ships. It'd be unfortunate to ship a release that doesn't support the non-blocking desktops, but (right now) it's fundamentally up to them to provide the development effort to ensure that they have a full feature set. -- Matthew Garrett | mj...@srcf.ucam.org -- Instead of shipping it, is there a problem with giving it to those on the developer list and letting us iron out the kinks? I do not really understand what you mean here /Andreas -- Richard -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
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 roadmapped for F20 Final to be in a fairly early stage at this point. (Plus what mclasen pointed out about only blocking on GNOME and KDE). 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. 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.) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
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.com/show_bug.cgi?id=716479 still the case? -- Tomasz Torcz ,,If you try to upissue this patchset I shall be seeking xmpp: zdzich...@chrome.pl an IP-routable hand grenade.'' -- Andrew Morton (LKML) -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
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 where to start. Lars -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
The whole reason why the bluez5 package was proposed as a separate one was so that we didn't have to cater for every desktop under the sun that's included in Fedora. bluez5 would conflict with bluez. If you had both MATE and GNOME installed, you wouldn't be able to upgrade to the latest version of GNOME as it would require bluez5 and the installed MATE bluez (4.x). That was the main idea, and would have avoided breaking all the desktops. At the end of the day, if somebody pushes bluez 5.x in the old bluez package, and it ends up breaking other things, I'm fine with it as well. Other desktops will need to follow up and make sure they get the porting in updates or admit that they don't have the manpower to keep up with that particular feature. - Original Message - 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 kalevlem...@gmail.com To: devel@lists.fedoraproject.org Subject: Re: BlueZ Status in Fedora. Message-ID: 520969b8.1030...@gmail.com Content-Type: text/plain; charset=UTF-8 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 move forward and try to integrate everything together in Rawhide before branching F20. I've cleaned up the feature page and marked it as ready for wrangler: https://fedoraproject.org/wiki/Changes/Bluez5 Sorry it's coming so late -- I didn't feel comfortable submitting it earlier knowing how much of the upstream development was still in flux. 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 dependencies for mate-bluetooth to avoid that xfce/lxde user don't have to be install to many mate packages if they want to use mate-bluetooth. It seems there is a plan that xfce/lxde also want to be use mate-bluetooth. (maybe) So f21 is Ok as goal, but f20 is definitely to early for mate. Thank you Wolfgang -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
On Wed, 14 Aug 2013 12:40:54 +0200 Rave it chat-to...@raveit.de 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 dev didn't remove /usr/lib64/gnome-bluetooth/libgnome-bluetooth-applet.so.0, which is in latest upstream. Ok, i need really help to create such a package. But there is also another simple solution gnome-bluetooth dev should add the removed (fallback) panel applet code back. I'm pretty shure that is more easier for someone who knows the code to do that. If gnome-bluetooth is the only client after the bluez5 switch which is working in fedora, than it should be work for all desktops, imo. So adding the applet back would be a noble gesture from gnome to other desktops ;) PS: i think cinnamon is also affected, because so far i know use cinnamon blueman code in the momment. But i'm not shure in this point. I've exchanged some emails with the author of https://github.com/ncopa/xfce-bluetooth Unfortunately, the code there is in very early alpha stage. It doesn't do a whole lot yet. He's happy to have any help implementing things, but makes no promises as to when things will be usable. This applet depends on vala and the xfce-vala bindings, so I am not sure if it would work for other desktops, but its possible that it could. If anyone would be interested in helping out with this applet, please contact the maintainer. For Xfce, we could use this if it becomes usable in time, or we could use some other systray producting applet, or we could just not support bluetooth from the desktop for this release. ;( kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
On Sun 18 August 2013 10:00:22 Kevin Fenzi wrote: On Wed, 14 Aug 2013 12:40:54 +0200 Rave it chat-to...@raveit.de 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 dev didn't remove /usr/lib64/gnome-bluetooth/libgnome-bluetooth-applet.so.0, which is in latest upstream. Ok, i need really help to create such a package. But there is also another simple solution gnome-bluetooth dev should add the removed (fallback) panel applet code back. I'm pretty shure that is more easier for someone who knows the code to do that. If gnome-bluetooth is the only client after the bluez5 switch which is working in fedora, than it should be work for all desktops, imo. So adding the applet back would be a noble gesture from gnome to other desktops ;) PS: i think cinnamon is also affected, because so far i know use cinnamon blueman code in the momment. But i'm not shure in this point. I've exchanged some emails with the author of https://github.com/ncopa/xfce-bluetooth Unfortunately, the code there is in very early alpha stage. It doesn't do a whole lot yet. He's happy to have any help implementing things, but makes no promises as to when things will be usable. This applet depends on vala and the xfce-vala bindings, so I am not sure if it would work for other desktops, but its possible that it could. If anyone would be interested in helping out with this applet, please contact the maintainer. For Xfce, we could use this if it becomes usable in time, or we could use some other systray producting applet, or we could just not support bluetooth from the desktop for this release. ;( 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 ... 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. Ryan -- Ryan Rix http://rix.si signature.asc Description: This is a digitally signed message part. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
On Sun, Aug 18, 2013 at 11:28 PM, Ryan Rix r...@n.rix.si wrote: On Sun 18 August 2013 10:00:22 Kevin Fenzi wrote: On Wed, 14 Aug 2013 12:40:54 +0200 Rave it chat-to...@raveit.de 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 dev didn't remove /usr/lib64/gnome-bluetooth/libgnome-bluetooth-applet.so.0, which is in latest upstream. Ok, i need really help to create such a package. But there is also another simple solution gnome-bluetooth dev should add the removed (fallback) panel applet code back. I'm pretty shure that is more easier for someone who knows the code to do that. If gnome-bluetooth is the only client after the bluez5 switch which is working in fedora, than it should be work for all desktops, imo. So adding the applet back would be a noble gesture from gnome to other desktops ;) PS: i think cinnamon is also affected, because so far i know use cinnamon blueman code in the momment. But i'm not shure in this point. I've exchanged some emails with the author of https://github.com/ncopa/xfce-bluetooth Unfortunately, the code there is in very early alpha stage. It doesn't do a whole lot yet. He's happy to have any help implementing things, but makes no promises as to when things will be usable. This applet depends on vala and the xfce-vala bindings, so I am not sure if it would work for other desktops, but its possible that it could. If anyone would be interested in helping out with this applet, please contact the maintainer. For Xfce, we could use this if it becomes usable in time, or we could use some other systray producting applet, or we could just not support bluetooth from the desktop for this release. ;( 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 ... 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. Well the problem is that we have way to many desktops (more desktops then resources). We can't delay changes until every desktop catches up (it basically means we can't move on with stuff at all). -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
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 Gnome and KDE. If those are broken then F20 doesn't ship - if they're working, it ships. It'd be unfortunate to ship a release that doesn't support the non-blocking desktops, but (right now) it's fundamentally up to them to provide the development effort to ensure that they have a full feature set. -- Matthew Garrett | mj...@srcf.ucam.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
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 -- Kalev -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
On Thu, 2013-08-15 at 15:04 -0700, Dan Mashal wrote: On Thu, Aug 15, 2013 at 10:55 AM, Lars Seipel lars.sei...@gmail.com 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 gnome-bluetooth proper and resurrect the panel icon stuff like Kalev proposed? Not so simple as reverting a commit. Must discuss with upstream. Please make it a separate package. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
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=MATE needs to be added. 3. Also runtime dependencies needs to be checked, we don't want to be install more gnome as necessary in mate. I discussed this with raveit65 on IRC and we found a way forward with this. The issue with MATE switching from mate-bluetooth to gnome-bluetooth is that gnome-bluetooth no longer ships the panel applet that MATE needs. This was removed from gnome-bluetooth in commit https://git.gnome.org/browse/gnome-bluetooth/commit/?id=c54e93e4310342ffce13e15b5a1b9a6ee9500a05 when GNOME stopped shipping the fallback mode. However, the panel applet code is pretty self contained. The way to make it work would be to move the panel applet code to a separate package. It could be called mate-panel-bluetooth or gnome-panel-bluetooth or similar. The package would then include the panel applet files that are no longer part of gnome-bluetooth, and link with libgnome-bluetooth. Anyone interested in teaming up with raveit65 to create a separate package for this? This package might also be useful for XFCE/LXDE. In any case, the best way forward is probably to go on with importing BlueZ 5 into rawhide so that it can be used as a development platform. Otherwise it's pretty hard to test the new code. Will the bluez-compat be killed in this move? JBG -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
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 dan.mas...@gmail.com wrote: On Thu, Aug 15, 2013 at 10:55 AM, Lars Seipel lars.sei...@gmail.com 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 gnome-bluetooth proper and resurrect the panel icon stuff like Kalev proposed? Not so simple as reverting a commit. Must discuss with upstream. Dan Also as Wolfgang (comaintainer for MATE) said and I personally would like to reiterate: 3. Also runtime dependencies needs to be checked, we don't want to be install more gnome as necessary in mate. The whole point of forking to be dependant on gnome upstream as little as possible. If you want to be independent of GNOME upstream, you need the resources to keep up to date with upstream changes in a timely fashion. It's not going to work for Fedora to delay moving to new upstream releases of major components for entire release cycles because MATE didn't have the resources to be ready for the change. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
We've go the resources. An entire DE doesn't appear out of nowhere. Just trying to determine how to proceed. Dan Sent from my Verizon Wireless BlackBerry -Original Message- From: Adam Williamson awill...@redhat.com Sender: devel-boun...@lists.fedoraproject.org Date: Fri, 16 Aug 2013 17:19:27 To: Development discussions related to Fedoradevel@lists.fedoraproject.org Reply-To: Development discussions related to Fedora devel@lists.fedoraproject.org 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 dan.mas...@gmail.com wrote: On Thu, Aug 15, 2013 at 10:55 AM, Lars Seipel lars.sei...@gmail.com 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 gnome-bluetooth proper and resurrect the panel icon stuff like Kalev proposed? Not so simple as reverting a commit. Must discuss with upstream. Dan Also as Wolfgang (comaintainer for MATE) said and I personally would like to reiterate: 3. Also runtime dependencies needs to be checked, we don't want to be install more gnome as necessary in mate. The whole point of forking to be dependant on gnome upstream as little as possible. If you want to be independent of GNOME upstream, you need the resources to keep up to date with upstream changes in a timely fashion. It's not going to work for Fedora to delay moving to new upstream releases of major components for entire release cycles because MATE didn't have the resources to be ready for the change. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
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 Kalev proposed? Lars -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
On Thu, Aug 15, 2013 at 10:55 AM, Lars Seipel lars.sei...@gmail.com 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 gnome-bluetooth proper and resurrect the panel icon stuff like Kalev proposed? Not so simple as reverting a commit. Must discuss with upstream. Dan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
On Thu, Aug 15, 2013 at 3:04 PM, Dan Mashal dan.mas...@gmail.com wrote: On Thu, Aug 15, 2013 at 10:55 AM, Lars Seipel lars.sei...@gmail.com 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 gnome-bluetooth proper and resurrect the panel icon stuff like Kalev proposed? Not so simple as reverting a commit. Must discuss with upstream. Dan Also as Wolfgang (comaintainer for MATE) said and I personally would like to reiterate: 3. Also runtime dependencies needs to be checked, we don't want to be install more gnome as necessary in mate. The whole point of forking to be dependant on gnome upstream as little as possible. Dan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
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 people and looks like all teams are go. NetworkManager and PulseAudio changes are slightly lagging behind, but it's probably best if we move forward and try to integrate everything together in Rawhide before branching F20. I've cleaned up the feature page and marked it as ready for wrangler: https://fedoraproject.org/wiki/Changes/Bluez5 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. Once done, pls let me know and I'll announce it and report to FESCo to get an exception. 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 dev didn't remove /usr/lib64/gnome-bluetooth/libgnome-bluetooth-applet.so.0, which is in latest upstream. Ok, i need really help to create such a package. But there is also another simple solution gnome-bluetooth dev should add the removed (fallback) panel applet code back. I'm pretty shure that is more easier for someone who knows the code to do that. If gnome-bluetooth is the only client after the bluez5 switch which is working in fedora, than it should be work for all desktops, imo. So adding the applet back would be a noble gesture from gnome to other desktops ;) PS: i think cinnamon is also affected, because so far i know use cinnamon blueman code in the momment. But i'm not shure in this point. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
On Tue, Aug 13, 2013 at 6:44 AM, Kalev Lember kalevlem...@gmail.com 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=MATE needs to be added. 3. Also runtime dependencies needs to be checked, we don't want to be install more gnome as necessary in mate. I discussed this with raveit65 on IRC and we found a way forward with this. The issue with MATE switching from mate-bluetooth to gnome-bluetooth is that gnome-bluetooth no longer ships the panel applet that MATE needs. This was removed from gnome-bluetooth in commit https://git.gnome.org/browse/gnome-bluetooth/commit/?id=c54e93e4310342ffce13e15b5a1b9a6ee9500a05 when GNOME stopped shipping the fallback mode. However, the panel applet code is pretty self contained. The way to make it work would be to move the panel applet code to a separate package. It could be called mate-panel-bluetooth or gnome-panel-bluetooth or similar. The package would then include the panel applet files that are no longer part of gnome-bluetooth, and link with libgnome-bluetooth. Anyone interested in teaming up with raveit65 to create a separate package for this? This package might also be useful for XFCE/LXDE. In any case, the best way forward is probably to go on with importing BlueZ 5 into rawhide so that it can be used as a development platform. Otherwise it's pretty hard to test the new code. -- Kalev -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Could we reverse this commit? Everyone wins. Otherwise we are looking at possibly reforking gnome-bluetooth at this point in time. Dan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
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 kalevlem...@gmail.com To: devel@lists.fedoraproject.org Subject: Re: BlueZ Status in Fedora. Message-ID: 520969b8.1030...@gmail.com Content-Type: text/plain; charset=UTF-8 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 move forward and try to integrate everything together in Rawhide before branching F20. I've cleaned up the feature page and marked it as ready for wrangler: https://fedoraproject.org/wiki/Changes/Bluez5 Sorry it's coming so late -- I didn't feel comfortable submitting it earlier knowing how much of the upstream development was still in flux. 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 dependencies for mate-bluetooth to avoid that xfce/lxde user don't have to be install to many mate packages if they want to use mate-bluetooth. It seems there is a plan that xfce/lxde also want to be use mate-bluetooth. (maybe) So f21 is Ok as goal, but f20 is definitely to early for mate. Thank you Wolfgang -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
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 dependencies for mate-bluetooth to avoid that xfce/lxde user don't have to be install to many mate packages if they want to use mate-bluetooth. It seems there is a plan that xfce/lxde also want to be use mate-bluetooth. (maybe) Can you use gnome-bluetooth instead? I mean, mate-bluetooth is just a fork on an older version of gnome-bluetooth. It probably made sense to use the fork when MATE was based on gtk2 (because you can't mix gtk2 and gtk3 librarires), but now that MATE has switched to gtk3, you guys should be able to switch back to gnome-bluetooth proper. -- Kalev -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
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 kalevlem...@gmail.com To: Development discussions related to Fedora devel@lists.fedoraproject.org Subject: Re: BlueZ Status in Fedora. Message-ID: 5209fbad.50...@gmail.com Content-Type: text/plain; charset=UTF-8 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 dependencies for mate-bluetooth to avoid that xfce/lxde user don't have to be install to many mate packages if they want to use mate-bluetooth. It seems there is a plan that xfce/lxde also want to be use mate-bluetooth. (maybe) Can you use gnome-bluetooth instead? I mean, mate-bluetooth is just a fork on an older version of gnome-bluetooth. It probably made sense to use the fork when MATE was based on gtk2 (because you can't mix gtk2 and gtk3 librarires), but now that MATE has switched to gtk3, you guys should be able to switch back to gnome-bluetooth proper. In general this is a possibility for the future (for fedora and upstream), because GTK3 is a development goal in mate upstream. But we have currently no fixed release date for MATE-1.8. And i'm pretty shure it doen't comes before next year. So GTK3 in MATE is a feature for f21/22. 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 runtime dependencies needs to be checked, we don't want to be install more gnome as necessary in mate. -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
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 runtime dependencies needs to be checked, we don't want to be install more gnome as necessary in mate. I discussed this with raveit65 on IRC and we found a way forward with this. The issue with MATE switching from mate-bluetooth to gnome-bluetooth is that gnome-bluetooth no longer ships the panel applet that MATE needs. This was removed from gnome-bluetooth in commit https://git.gnome.org/browse/gnome-bluetooth/commit/?id=c54e93e4310342ffce13e15b5a1b9a6ee9500a05 when GNOME stopped shipping the fallback mode. However, the panel applet code is pretty self contained. The way to make it work would be to move the panel applet code to a separate package. It could be called mate-panel-bluetooth or gnome-panel-bluetooth or similar. The package would then include the panel applet files that are no longer part of gnome-bluetooth, and link with libgnome-bluetooth. Anyone interested in teaming up with raveit65 to create a separate package for this? This package might also be useful for XFCE/LXDE. In any case, the best way forward is probably to go on with importing BlueZ 5 into rawhide so that it can be used as a development platform. Otherwise it's pretty hard to test the new code. -- Kalev -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
- 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 behind, but it's probably best if we move forward and try to integrate everything together in Rawhide before branching F20. I've cleaned up the feature page and marked it as ready for wrangler: https://fedoraproject.org/wiki/Changes/Bluez5 Ok, thanks Kalev. I'm going to take a look. Sorry it's coming so late -- I didn't feel comfortable submitting it earlier knowing how much of the upstream development was still in flux. Well, thank you for work on the coordination side, for such big change, we definitely need it. Jaroslav -- Thanks, Kalev -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
- 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 behind, but it's probably best if we move forward and try to integrate everything together in Rawhide before branching F20. I've cleaned up the feature page and marked it as ready for wrangler: https://fedoraproject.org/wiki/Changes/Bluez5 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. Once done, pls let me know and I'll announce it and report to FESCo to get an exception. Thanks Jaroslav Sorry it's coming so late -- I didn't feel comfortable submitting it earlier knowing how much of the upstream development was still in flux. -- Thanks, Kalev -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
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. Once done, pls let me know and I'll announce it and report to FESCo to get an exception. Thanks, I've added a section on MATE and a detailed contingency plan. Let me know if I should change anything else. -- Kalev -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
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 move forward and try to integrate everything together in Rawhide before branching F20. I've cleaned up the feature page and marked it as ready for wrangler: https://fedoraproject.org/wiki/Changes/Bluez5 Sorry it's coming so late -- I didn't feel comfortable submitting it earlier knowing how much of the upstream development was still in flux. -- Thanks, Kalev -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
- 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 plan what to do. It's possible that it gets delayed to F21, but it will definitely land in Fedora sooner or later. Let me know - I'd like to have this one as a Change if it's going to F20 (I was in touch with a new owner). Not a problem to talk personally :) Hope to make at least one day to attend GUADEC (or I organize the GUADEC football match ;-). Thanks Jaroslav -- Kalev -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
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-May/182355.html -- Tomasz Torcz Never underestimate the bandwidth of a station xmpp: zdzich...@chrome.plwagon filled with backup tapes. -- Jim Gray -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
On Thu, Aug 1, 2013 at 6:14 PM, Tomasz Torcz to...@pipebreaker.pl 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 starting at https://lists.fedoraproject.org/pipermail/devel/2013-May/182355.html 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 Peter -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
On Thu, 2013-08-01 at 18:36 +0100, Peter Robinson wrote: On Thu, Aug 1, 2013 at 6:14 PM, Tomasz Torcz to...@pipebreaker.pl 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 starting at https://lists.fedoraproject.org/pipermail/devel/2013-May/182355.html 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 For the NetworkManager side, porting to Bluez5 requires a couple things yet to finish: 1) DUN support: bluez5 makes this incredibly difficult because the DUN serial channel is no longer a kernel device and thus can't be used with pppd, can only be seen by one process, thus we pretty much have to cut Bluez5 out of the DUN path entirely. That's being worked on slowly. 2) a behavior change in NetworkManager to show all PAN/DUN capable devices immediately, not just ones that have been configured during pairing. This requires some updates to the GUI apps and some additional changes to NetworkManager to prompt the user to configure the device upon first-use, instead of at pair-time. Dan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: BlueZ Status in Fedora.
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 gets delayed to F21, but it will definitely land in Fedora sooner or later. -- Kalev -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
