bluez & blueman seem out of order

[jur]

Confirmed, now I have it going.

[Jason W]

Juanito -  Sorry I missed your question, I have obviously been distracted from lately from the task at hand. 

Yeah, my preference is for python-2.7 dependent stuff to keep the -2.7 suffix even after the migration, since it will be shortly after that there will be a desire to migrate to yet the next python.  With the suffix remaining in place, we will always know which python an app is built against, and the transition between pythons would remain seamless. 

I did see Arslan's 2.7 dependent stuff being renamed back to not having the -2.7 suffix, but I assumed that each of those apps were confirmed not to have anything built against python 2.6 dependent on them.  Since if they had no 2.6 dependent apps depending on them, then not having the 2.7 suffix would be ok.

Since there has been an issue I think we need to stay with using the 2.7 suffix. 

[Arslan S.]

@Arslan S: If you let me know which of your updated extensions need renaming "-2.7", I'll try to fix things.

i searched my extensions and i have only emesene that optionally depends on notify-python-2.7

[Juanito]

i searched my extensions and i have only emesene that optionally depends on notify-python-2.7

..and I guess dbus-python-2.7, but since they're optional, I believe we can leave things as they are.

[jur]

I'm having the same problem again with blueman:

Code: [Select]


tc@box:~$ bluemanj
tcl.tcz: OK
tk.tcz: OK
python.tcz: OK
pycairo.tcz: OK
libffi.tcz: OK
pygobject.tcz: OK
pygtk.tcz: OK
notify-python.tcz: OK
dbus-python.tcz: OK
blueman.tcz: OK
libiconv.tcz: OK
fuse.tcz: OK
obex.tcz: OK
Traceback (most recent call last):
  File "/usr/local/bin/blueman-manager", line 25, in <module>
    import gtk
ImportError: No module named gtk
sudo: rox: command not found
tc@box:~$ blueman-manager
Traceback (most recent call last):
  File "/usr/local/bin/blueman-manager", line 25, in <module>
    import gtk
ImportError: No module named gtk


[Juanito]

If the repo has been adjusted so that python-2.7 -> python, then you'll need to use blueman-2.7

[jur]

I just did a dep update, and it turns out the deps were adjusted so it is asking for python-2.6 which I didn't have. With python-2.6 loaded it works again.