Python-gobject update to 3.0.4, for bluez-simple-agent to work#486
Python-gobject update to 3.0.4, for bluez-simple-agent to work#486viric wants to merge 1 commit intoNixOS:masterfrom
Conversation
|
Trying to package git versions of mypaint I hit additional problems, such as GI_TYPELIB_PATH must be set and similar. I'll contribute those changes to x-updates |
|
Actually, this breaks pygtk and duplicates pull request #470 (which also has a pygtk fix by including pygobject2 as an extra package)... |
|
Current state is: I have both pygtk and gobject (which's trunk version has a pygtk wrapper and is repacing pygtk in the future) both working (mypaint master example). We want to provide patches as gtk3 branch on top of x-updates soon. |
|
Does it make any sense, to get a new pygobject attribute, even if only for bluez? The #470 looks quite complicated to merge. |
|
Excerpts from viric's message of Thu May 09 20:02:10 +0200 2013:
I'm not finished yet, I tried updating pygobject* related stuff - you |
|
I mean, adding pygobject3 wouldn't cause any breakage, and fix bluez. That can be done quickly, causing no harm. Do you agree? |
bluez-simple-agent fails to work otherwise. We discussed this a bit on #486, and this looks like the simplest way to get bluez-simple-agent again.
|
I added pygobject3: ac4dcab. I close this request. |
* Update participants and TC list Roughly based on activity on #ircv3 and github
3 participants
This makes 'bluez' python programs work (they import gi.repository, iirc), like bluez-simple-agent. But I don't know if it breaks things.
bluez-simple-agent is what I use to authenticate bluetooth devices, so for me it is important to have it working.
It'd be nice if some python maintainer could take a look; if it breaks things, we can have two pygobject.