|
2010-02-02
, 11:55
|
Posts: 479 |
Thanked: 641 times |
Joined on Dec 2007
@ Switzerland
|
#102
|
I've tried your software and I receive the next error:
Code:File "erminig-ng", line 43, in <module> import cwrapper File "/home/user/MyDocs/erminig-ng/erminig-ng-0.1.1/cwrapper.py", line 13, in module> lib = cd11.LoadLibrary(erminig_conf.libpath + "/libcalccess.so") File "/usr/lib/python2.5/ctypes/__init__.py", line 431, in LoadLibrary return self._dlltype(name) File "/usr/lib/python2.5/ctypes/__init__.py", line 348, in __init__ self.handle = _dlopen(self._name, mode) ODError: /home/user/MyDocs/erminig-ng/erminig-ng-0.1.1/libcalaccess.so: failed to map segment form shared object: Operation not permitted
|
2010-02-02
, 15:30
|
Posts: 22 |
Thanked: 6 times |
Joined on Dec 2009
@ Utrecht, the Netherlands
|
#103
|
The Following User Says Thank You to dreixel For This Useful Post: | ||
|
2010-02-02
, 15:33
|
Posts: 479 |
Thanked: 641 times |
Joined on Dec 2007
@ Switzerland
|
#104
|
|
2010-02-02
, 15:54
|
Posts: 22 |
Thanked: 6 times |
Joined on Dec 2009
@ Utrecht, the Netherlands
|
#105
|
|
2010-02-02
, 20:46
|
Posts: 34 |
Thanked: 17 times |
Joined on Dec 2009
|
#106
|
The Following User Says Thank You to petibub For This Useful Post: | ||
|
2010-02-02
, 21:21
|
Posts: 479 |
Thanked: 641 times |
Joined on Dec 2007
@ Switzerland
|
#107
|
The calendars are created on google as they should be - even the names are correct now. The events are (almost) correctly synchronized, the recurring events are ignored. "Almost" because: the end date of the events is wrong: the new events on Google are one day shorter than the original events in N900. I checked the time zone and it does not matter - the bug exists even for whole-day events.
What about the roadmap for recurring events? Having that I could start using Erminig-NG on a regular basis with my real calendar, which would be really coo
|
2010-02-03
, 08:10
|
Posts: 168 |
Thanked: 265 times |
Joined on Oct 2009
@ London, UK
|
#108
|
|
2010-02-03
, 11:39
|
Posts: 123 |
Thanked: 33 times |
Joined on Jan 2010
@ Stockholm
|
#109
|
~ $ cd erminig-ng-0.1.0/ ~/erminig-ng-0.1.0 $ python2.5 erminig-ng Traceback (most recent call last): File "erminig-ng", line 526, in <module> syncNewEvents() File "erminig-ng", line 505, in syncNewEvents getNewEventsFromGoogle(lastSync) File "erminig-ng", line 291, in getNewEventsFromGoogle feed = gd_client.CalendarQuery(query) File "/usr/lib/python2.5/site-packages/gdata/calendar/service.py", line 126, in CalendarQuery converter=gdata.calendar.CalendarEventFeedFromString) File "/usr/lib/python2.5/site-packages/gdata/calendar/service.py", line 118, in Query result = self.Get(uri, converter=converter) File "/usr/lib/python2.5/site-packages/gdata/service.py", line 1050, in Get 'reason': server_response.reason, 'body': result_body} gdata.service.RequestError: {'status': 400, 'body': 'Invalid updated-min', 'reason': 'Bad Request'}
|
2010-02-03
, 12:26
|
Posts: 479 |
Thanked: 641 times |
Joined on Dec 2007
@ Switzerland
|
#110
|
Still using old version, but I believe the below isn't changed in the later release (correct me if my assumption is a mother). Until now, the thingy has been doing what it's supposed to do.
If you want the URL called or something, please inform me of what variables to print where.Code:~ $ cd erminig-ng-0.1.0/ ~/erminig-ng-0.1.0 $ python2.5 erminig-ng Traceback (most recent call last): File "erminig-ng", line 526, in <module> syncNewEvents() File "erminig-ng", line 505, in syncNewEvents getNewEventsFromGoogle(lastSync) File "erminig-ng", line 291, in getNewEventsFromGoogle feed = gd_client.CalendarQuery(query) File "/usr/lib/python2.5/site-packages/gdata/calendar/service.py", line 126, in CalendarQuery converter=gdata.calendar.CalendarEventFeedFromString) File "/usr/lib/python2.5/site-packages/gdata/calendar/service.py", line 118, in Query result = self.Get(uri, converter=converter) File "/usr/lib/python2.5/site-packages/gdata/service.py", line 1050, in Get 'reason': server_response.reason, 'body': result_body} gdata.service.RequestError: {'status': 400, 'body': 'Invalid updated-min', 'reason': 'Bad Request'}
/P
sqlite3 ~/.erminig.db
select * from config;
Tags |
erminig, erminig-ng, ernie nig, google calendar, google sync, synchronization |
|
For the bug you encountered: yes it is ignoring recurring events, and I just checked the code: the recurring event detection is done before ever manipulating the date, so the problem is not there.
In fact after re-reading the stack trace you posted above, the problem is located in the data feed we get from Google: for some reason the published date of the event is outside the allowed bounds of the time module of Python.
If you are willing to perform a little modification of the code and post here the result it would be great.
Essentially, edit the file ermini-ng and insert before line 302 (i.e. before the line that reads "cdate = iso8601ToTimestamp(e.published.text)" the following code snippet (respecting the proper indentation):
If you don't want to do that, no problem
thanks