[SyncEvolution] Fwd: Problem executing syncevo-phone-config
Mit freundlichen Grüßen
Philipp A. Mohrenweiser
---------- Forwarded message ----------
From: Philipp Mohrenweiser <phiamo(a)googlemail.com>
Date: 2010/5/11
Subject: Re: [SyncEvolution] Problem executing syncevo-phone-config
To: Patrick Ohly <patrick.ohly(a)intel.com>
Perfect thanks,was too tired to read it exactly enough...
but even with the new one my
SE W890 wont work :(
with syncevolution beta2 i got some communication, getting the
contacts and some calendar entrys to evolution, but unfortunatly not
the way back on phone ...
now i do not get anything woking :(
any of the following always result in No working configuration found
python syncevo-phone-config.py -b 00:23:F1:80:C1:C8
python syncevo-phone-config.py -b 00:23:F1:80:C1:C8 --advanced
python syncevo-phone-config.py -b 00:23:F1:80:C1:C8 -p 1.1
python syncevo-phone-config.py -b 00:23:F1:80:C1:C8 -p 1.1 advanced
****************SUMMARY****************
No working configuration found
are there any ideas how to go further ?
could it be that the beta2 config is used somehow ?
how to clear it if nessesarry?
cheers phil
2010/5/11 Patrick Ohly <patrick.ohly(a)intel.com>:
On Tue, 2010-05-11 at 00:27 +0100, Philipp Mohrenweiser wrote:
> hi i was trying to generate a config for my phone ....
>
> syncevo-phone-config --advanced -b 00:23:F1:80:C1:C8 -v
> /usr/bin/syncevo-phone-config:24: DeprecationWarning: The popen2
> module is deprecated. Use the subprocess module.
> import sys, optparse, os, time, popen2, tempfile
> Traceback (most recent call last):
> File "/usr/bin/syncevo-phone-config", line 707, in <module>
> main()
> File "/usr/bin/syncevo-phone-config", line 700, in main
> tempfile = tempfile.mkdtemp(prefix="syncevo-phone-config")
> UnboundLocalError: local variable 'tempfile' referenced before assignment
>
>
> but i got that error ... any ideas ?
Known problem in 1.0 beta 3, please use the updated script pointed to on
http://syncevolution.org/development/sync-phone
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.