Menu
▾
▴
opensync-devel — The place to coordinate the development of OpenSync
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
(9) |
Apr
(84) |
May
(18) |
Jun
(12) |
Jul
(6) |
Aug
(7) |
Sep
(10) |
Oct
(31) |
Nov
(59) |
Dec
(14) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
(53) |
Feb
(15) |
Mar
(43) |
Apr
(40) |
May
(63) |
Jun
(142) |
Jul
(54) |
Aug
(31) |
Sep
(30) |
Oct
(39) |
Nov
(36) |
Dec
(64) |
| 2007 |
Jan
(128) |
Feb
(261) |
Mar
(156) |
Apr
(127) |
May
(76) |
Jun
(131) |
Jul
(83) |
Aug
(124) |
Sep
(83) |
Oct
(88) |
Nov
(180) |
Dec
(90) |
| 2008 |
Jan
(86) |
Feb
(93) |
Mar
(117) |
Apr
(104) |
May
(65) |
Jun
(35) |
Jul
(38) |
Aug
(111) |
Sep
(58) |
Oct
(33) |
Nov
(102) |
Dec
(194) |
| 2009 |
Jan
(193) |
Feb
(74) |
Mar
(111) |
Apr
(77) |
May
(31) |
Jun
(20) |
Jul
(1) |
Aug
(3) |
Sep
(57) |
Oct
(125) |
Nov
(50) |
Dec
(3) |
| 2010 |
Jan
(26) |
Feb
(5) |
Mar
(13) |
Apr
(3) |
May
(3) |
Jun
(12) |
Jul
(27) |
Aug
(47) |
Sep
(105) |
Oct
(53) |
Nov
(34) |
Dec
(21) |
| 2011 |
Jan
(115) |
Feb
(17) |
Mar
|
Apr
(6) |
May
(16) |
Jun
(15) |
Jul
(85) |
Aug
(21) |
Sep
(13) |
Oct
(12) |
Nov
(28) |
Dec
(23) |
| 2012 |
Jan
|
Feb
(13) |
Mar
(4) |
Apr
|
May
(1) |
Jun
(5) |
Jul
(5) |
Aug
(31) |
Sep
(8) |
Oct
|
Nov
|
Dec
(1) |
| 2013 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(33) |
Sep
(9) |
Oct
(10) |
Nov
(2) |
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
(4) |
| 2016 |
Jan
(2) |
Feb
|
Mar
(3) |
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: Daniel G. <go...@b1...> - 2010-12-18 09:33:01
|
Hello, this weekend we have to do some maintenance work for *.opensync.org infrastructure. In detail: *.opensync.org is moving to a new host. This affects, libwbxml, libsyncml, OpenSync and the relevant Subversion repositories and the CDash instance. Sorry for any inconvenience and for the very short notice. I'll let you know once the migration is done. Regards, Daniel -- Daniel Gollub Linux Consultant & Developer Mail: go...@b1... B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 |
|
From: Patrick O. <pat...@gm...> - 2010-12-17 20:14:59
|
On Fr, 2010-12-17 at 19:36 +0530, Dinesh wrote:
> Hi,
>
> On Fri, Dec 17, 2010 at 2:23 PM, Patrick Ohly <pat...@gm...>
> wrote:
> On Do, 2010-12-16 at 23:14 +0100, Quentin Denis wrote:
> > Well, it seems quite obvious for me that direct syncing
> between the phone and
> > another group-member should be possible. That is why OBEX
> seems necessary to
> > me, or how should I understand how libsynthesis is
> implemented in practice? A
> > contact of mine, called Dinesh, has quite a good knowledge
> about this,
> > especially since he wrote the syncml-plugin for
> syncevolution recently.
>
> I'm not sure what Dinesh really said about his involvement,
> but he did
> not write a SyncML plugin. SyncEvolution already supported
> direct
> synchronization with phones via SyncML/OBEX/Bluetooth before
> Dinesh got
> involved. He focused on adding Akonadi support (based on a
> prototype
> backend that I had written earlier) and a KDE GUI.
>
>
> I kind of dont understand what went on and really don't know what to
> say here, so, Firstly I totally I agree with what Patrick Just said.
I'm sure it was an entirely benign misunderstanding. Also don't
understate your own work. Without it, there won't be Akonadi and KDE
support anytime soon because I myself cannot cover everything.
I decided to keep the OpenSync list on CC. The question about OpenSync's
design and SyncML plugin came up, so perhaps people here are interested
in the status and internals of other projects in the area.
> I need to figure out on adapting the XML files to suite KDE's custom
> vCard fields - which i m not really sure how to tackle because as per
> Wikipedia, there are only 8 custom fields, but KAddressBook lets the
> user create his/her own custom fields per contact... which need to be
> taken care of. So what can be done here?
Interesting question. I need to research this a bit, but a here's a
rough outline:
* for known extensions which map to existing fields, define the
properties in the profile for KDE/Akonadi (spouse, ...)
* add two new array fields which hold a) name of the unknown
extension and b) its value, with a mapping to
X-KADDRESSBOOK-<name>=<value> in the profile
The second might be a bit tricky. There is a something similar where the
name of a parameter value is composed as
TYPE=X-Synthesis-Ref<something>, but we need that for a property name.
Might involve some coding in libsynthesis. I can do that.
> Also will there be a move to cmake, or how should the Qt/KDE GUI and
> the BlueDevil Plugin (currently using cmake) be integrated (It seems
> to be a really difficult task to move these to autotools) be
> integrated with the current syncevolution?
I would keep them as separate sources with their own build rules. There
are pros and cons for releasing just a single tarball. I think the
disadvantages (having to release an update of everything when just a
frontend used by a subset of the users is modified) outweighs the
advantages (single version number, single release).
The GTK sync-ui is included in the syncevolution source for historic
reasons; I wouldn't do it like that if I started from scratch. It's not
worth changing because it doesn't get modified much these days.
--
Bye, Patrick Ohly
--
Pat...@gm...
http://www.estamos.de/
|
|
From: Patrick O. <pat...@gm...> - 2010-12-17 08:54:01
|
On Do, 2010-12-16 at 23:14 +0100, Quentin Denis wrote: > Well, it seems quite obvious for me that direct syncing between the phone and > another group-member should be possible. That is why OBEX seems necessary to > me, or how should I understand how libsynthesis is implemented in practice? A > contact of mine, called Dinesh, has quite a good knowledge about this, > especially since he wrote the syncml-plugin for syncevolution recently. I'm not sure what Dinesh really said about his involvement, but he did not write a SyncML plugin. SyncEvolution already supported direct synchronization with phones via SyncML/OBEX/Bluetooth before Dinesh got involved. He focused on adding Akonadi support (based on a prototype backend that I had written earlier) and a KDE GUI. To answer your question about OBEX transport + libsynthesis: libsynthesis does not contain any kind of transport mechanism. It consumes and produces SyncML messages. The platform specific application on top of libsynthesis is responsible for sending/receiving these messages. SyncEvolution has these transports for HTTP and OBEX, both for initiating and accepting sessions (SyncML client and server). > He > gave me the following answer which might interest you: > > "Hey Quentin, [...] > Also, you might be interested to check this project called Buteo Sync(in > Meego's Website), which is the main synchronization framework for MeeGo... > and it replaced syncevolution for MeeGo.. > currently it includes open source sync framework for: > 1) Contacts > 2) Calender > 3) MPT (media transfer protocol: for music syncing) > > and a closed source sync framework for: > 1) SMS , MMS > 2) Bookmarks etc.. > > Today i ve talked to the Nokia engineers behind this and they said it would > be totally open sourced really soon, once after they make it quite stable. All components that Nokia intends to contribute are already open source, as far as I know. I'm involved in anything related to Buteo and MeeGo as part of my job at Intel. Some things that are missing for a complete solution for deployment on a phone are kept proprietary, see http://bugs.meego.com/show_bug.cgi?id=3868 > It > So you might want to look at this for the actual direction of > KMobileTools.(To enable KDE to ) > Its a quite good and interesting project for us since: > 1) it is Qt Based > 2) maintained by Nokia and Intel!!! Buteo was written and is maintained primarily by Nokia. It is also not currently tested with anything in MeeGo. Configurations for Mobical and Google Contacts finally exist, but no real interoperability testing with them was done in MeeGo (see http://bugs.meego.com/show_bug.cgi?id=3869). Direct syncing with phones is something that Nokia has demoed with Nokia phones, but it is not a feature that is planned for MeeGo. The current code does not work with non-Nokia phones (for example, phone must combine calendar+tasks, which Sony Ericsson phones don't). The biggest gap in Buteo (compared to SyncEvolution/Synthesis) is that it contains no code to handle conflicts and data conversion. Anyone writing a data plugin for it has to implement that part himself. See my LinuxCon 2010 presentation, which I created together with the Buteo developers: http://events.linuxfoundation.org/linuxcon2010/ohly -- Bye, Patrick Ohly -- Pat...@gm... http://www.estamos.de/ |
|
From: Quentin D. <que...@gm...> - 2010-12-16 22:15:06
|
Well, it seems quite obvious for me that direct syncing between the phone and another group-member should be possible. That is why OBEX seems necessary to me, or how should I understand how libsynthesis is implemented in practice? A contact of mine, called Dinesh, has quite a good knowledge about this, especially since he wrote the syncml-plugin for syncevolution recently. He gave me the following answer which might interest you: "Hey Quentin, libsynthesis is just the syncml engine(comparing the data, updating the right source etc...)... not the whole sync framework...SyncEvolution provides libsynthesis with the data sources, transport agents and a whole other stuff... Also, you might be interested to check this project called Buteo Sync(in Meego's Website), which is the main synchronization framework for MeeGo... and it replaced syncevolution for MeeGo.. currently it includes open source sync framework for: 1) Contacts 2) Calender 3) MPT (media transfer protocol: for music syncing) and a closed source sync framework for: 1) SMS , MMS 2) Bookmarks etc.. Today i ve talked to the Nokia engineers behind this and they said it would be totally open sourced really soon, once after they make it quite stable. It So you might want to look at this for the actual direction of KMobileTools.(To enable KDE to ) Its a quite good and interesting project for us since: 1) it is Qt Based 2) maintained by Nokia and Intel!!! If interested, i can let you know more about this :) Cheers Dinesh" It seems that there is quite a potential solutions out there. All I want is a working SyncML for my mobile phone. ;-) Kind regards, Quentin On Monday 13 December 2010 20:55:47 Emanoil Kotsev wrote: > Thank you for your statement and for taking your time to put forward your > standpoint. > > > the SyncML plugin heavily depends on libsyncml. So I think > > a rewrite and > > the use of a different library would be a possible way. The > > problem is > > that libsynthesis does not provide OBEX support. > > I read recently Nokia documentation that stated that not all OBEX features > are supported by their implementation, so probably this is not an issue > and perhaps it is better to get away from OBEX. > > > I did stop my work because I cannot work on the plugin > > during my work > > time and I have some general concerns on the design of > > SyncML and OpenSync. > > > > SyncML merging will always be a problem. If a device is out > > of sync and > > there are changed items on both sides there is always the > > risk of > > duplicated entries. I can just note here that this > > behaviour is just > > unacceptable for customers with many contacts and events. > > This leads to > > our (university's) decision for Active Sync. > > > > OpenSync introduces an additional problem for us. It syncs > > all devices > > at once and requires a slow sync if there was a problem > > with just one > > device. The following slow sync with an enabled merger can > > create a > > complexity which is simply too high. Just calculate the > > effort for a > > general merger and 5 devices with 100 items each. > > > > So I personally prefer peer-to-peer and clear unique > > identifier designs > > for synchronization. > > > > I hope somebody else has enough motivation to take over the > > maintenance. > > If you want to take over then you can expect that I am > > willing to help > > with informations. > > I can just tell that these are complex decisions and I'm wondering who's > going to take them. > > If I'm understanding you right you suggest that because of the slow sync it > is better to sync in pairs separately the desired types. In fact this was > the safe part of my testing. Contats - Contacts > Calendar - Calendar > etc > > About the syncml plugin it might be easier to write a libsynthesis based > plugin from scratch. > > But in the current situation I have just a minor problem with an entity not > being accepted by the parser as I documented in the bug. It might be > easier to fix this one instead of discussing and doing some unnecessary > work. > > Very sad, that you don't have the time and the motivation to work on it, > but you have my complete understanding about it. > > It would be nice if you can organize a hand over in some form - upload to > svn or whatever > > Thanks for the work so far > > Some questions: > > If I have write access to svn, can I update syncml code or do I need extra > permitions for it? > > Is there a way to emulate connected phone, because it is cumbersome when > testing. > > Documentation - also links and docs that you've used? > > regards > > > > > --------------------------------------------------------------------------- > --- Lotusphere 2011 > Register now for Lotusphere 2011 and learn how > to connect the dots, take your collaborative environment > to the next level, and enter the era of Social Business. > http://p.sf.net/sfu/lotusphere-d2d > _______________________________________________ > Opensync-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensync-devel |
|
From: Michael B. <mic...@cm...> - 2010-12-14 15:06:23
|
On 12/13/10 20:55, Emanoil Kotsev wrote: > > I can just tell that these are complex decisions and I'm wondering who's going to take them. Me too ;) > But in the current situation I have just a minor problem with an entity not being accepted by the parser as I documented in the bug. > It might be easier to fix this one instead of discussing and doing some unnecessary work. Please point me to the ticket directly via private mail. If there is only a missing tag then this should be no big issue. > It would be nice if you can organize a hand over in some form - upload to svn or whatever All stuff should be available via svn already. I just use the OpenSync infrastructure. I am only a developer. I am not an infrastructure maintainer. > If I have write access to svn, can I update syncml code or do I need extra permitions for it? If you have write access to SVN then you work directly on the source. There is no extra layer. > Is there a way to emulate connected phone, because it is cumbersome when testing. I always tested with the real hardware or implemented test code directly. Best regards Michael -- ___________________________________________________________________ Michael Bell Humboldt-Universitaet zu Berlin Tel.: +49 (0)30-2093 70143 ZE Computer- und Medienservice Fax: +49 (0)30-2093 2704 Unter den Linden 6 mic...@cm... D-10099 Berlin ___________________________________________________________________ PGP Fingerprint: 09E4 3D29 4156 2774 0F2C C643 D8BD 1918 2030 5AAB |
|
From: Michael B. <mic...@cm...> - 2010-12-14 14:58:21
|
Hi Patrick,
On 12/13/10 08:50, Patrick Ohly wrote:
>
> On So, 2010-12-12 at 21:03 +0100, Michael Bell wrote:
>> SyncML merging will always be a problem. If a device is out of sync and
>> there are changed items on both sides there is always the risk of
>> duplicated entries. I can just note here that this behaviour is just
>> unacceptable for customers with many contacts and events. This leads to
>> our (university's) decision for Active Sync.
>
> I agree that merging in a slow sync is difficult, and that involving
> unrelated devices just makes it harder. I have not looked at Active Sync
> in detail yet. Does it prescribe that all items must have a unique ID?
>
> What if someone has data in his phone and starts syncing with a server
> which also has data ("first time slow sync" in SyncML)? Does Active Sync
> require that one side is wiped clean before syncing can start? Otherwise
> I don't see how this use case can be supported without merging.
We have a very well defined workflow ;) First we have an empty mobile.
Second we synchronize it for the first time with our calendar server.
After this point all events have a GUID. So if a synchronization fails
(perhaps because of an UMTS problem) then even a "slow" sync in active
sync cannot create tons of duplicates. If you don't make changes on the
phone then you will have no problems with SyncML too but the most users
does not have this discipline ;)
> It's getting more off-topic, but can you say also a bit about what
> implementations of Active Sync the Humboldt university will support
> (client and server side)? This being a university, I would hope that
> such information can be shared (perhaps off-list).
Actually we just defined the client side which must be supported and we
begin to evaluate the server market. We don't make big statements to the
public even the university's employees. So I can give you some
informations but only on a "NDA" base like with libsynthesis in the past.
If there is a final decision then the decision will be public. Today we
use Oracle OCS with SyncML and clients from Synthesis.
Best regards
Michael
--
___________________________________________________________________
Michael Bell Humboldt-Universitaet zu Berlin
Tel.: +49 (0)30-2093 70143 ZE Computer- und Medienservice
Fax: +49 (0)30-2093 2704 Unter den Linden 6
mic...@cm... D-10099 Berlin
___________________________________________________________________
PGP Fingerprint: 09E4 3D29 4156 2774 0F2C C643 D8BD 1918 2030 5AAB
|
|
From: Emanoil K. <del...@ya...> - 2010-12-13 19:55:54
|
Thank you for your statement and for taking your time to put forward your standpoint.
>
> the SyncML plugin heavily depends on libsyncml. So I think
> a rewrite and
> the use of a different library would be a possible way. The
> problem is
> that libsynthesis does not provide OBEX support.
I read recently Nokia documentation that stated that not all OBEX features are supported by their implementation, so probably this is not an issue and perhaps it is better to get away from OBEX.
>
> I did stop my work because I cannot work on the plugin
> during my work
> time and I have some general concerns on the design of
> SyncML and OpenSync.
>
> SyncML merging will always be a problem. If a device is out
> of sync and
> there are changed items on both sides there is always the
> risk of
> duplicated entries. I can just note here that this
> behaviour is just
> unacceptable for customers with many contacts and events.
> This leads to
> our (university's) decision for Active Sync.
>
> OpenSync introduces an additional problem for us. It syncs
> all devices
> at once and requires a slow sync if there was a problem
> with just one
> device. The following slow sync with an enabled merger can
> create a
> complexity which is simply too high. Just calculate the
> effort for a
> general merger and 5 devices with 100 items each.
>
> So I personally prefer peer-to-peer and clear unique
> identifier designs
> for synchronization.
>
> I hope somebody else has enough motivation to take over the
> maintenance.
> If you want to take over then you can expect that I am
> willing to help
> with informations.
>
I can just tell that these are complex decisions and I'm wondering who's going to take them.
If I'm understanding you right you suggest that because of the slow sync it is better to sync in pairs separately the desired types. In fact this was the safe part of my testing.
Contats - Contacts
Calendar - Calendar
etc
About the syncml plugin it might be easier to write a libsynthesis based plugin from scratch.
But in the current situation I have just a minor problem with an entity not being accepted by the parser as I documented in the bug.
It might be easier to fix this one instead of discussing and doing some unnecessary work.
Very sad, that you don't have the time and the motivation to work on it, but you have my complete understanding about it.
It would be nice if you can organize a hand over in some form - upload to svn or whatever
Thanks for the work so far
Some questions:
If I have write access to svn, can I update syncml code or do I need extra permitions for it?
Is there a way to emulate connected phone, because it is cumbersome when testing.
Documentation - also links and docs that you've used?
regards
|
|
From: Emanoil K. <del...@ya...> - 2010-12-13 19:18:20
|
Hi,
just to mention
>
> the libwbxml stack is the base layer under libsyncml if you
> use WBXML.
> libwbxml is used by several other software vendors. These
> software
> vendors need a working library too. Therefore I have a
> motivation to
> take care about this library. Especially because I see no
> alternative
> for this C library.
libwbxml is working well with the current ds stack. From the testing I've done it seems to be working for Contacts, Calendar and Notes, but probably for the rest too
regards
|
|
From: Patrick O. <pat...@gm...> - 2010-12-13 07:50:31
|
Hello Michael!
Thanks for your emails and all the work that you invested over the
years.
On So, 2010-12-12 at 21:03 +0100, Michael Bell wrote:
> SyncML merging will always be a problem. If a device is out of sync and
> there are changed items on both sides there is always the risk of
> duplicated entries. I can just note here that this behaviour is just
> unacceptable for customers with many contacts and events. This leads to
> our (university's) decision for Active Sync.
I agree that merging in a slow sync is difficult, and that involving
unrelated devices just makes it harder. I have not looked at Active Sync
in detail yet. Does it prescribe that all items must have a unique ID?
What if someone has data in his phone and starts syncing with a server
which also has data ("first time slow sync" in SyncML)? Does Active Sync
require that one side is wiped clean before syncing can start? Otherwise
I don't see how this use case can be supported without merging.
It's getting more off-topic, but can you say also a bit about what
implementations of Active Sync the Humboldt university will support
(client and server side)? This being a university, I would hope that
such information can be shared (perhaps off-list).
--
Bye, Patrick Ohly
--
Pat...@gm...
http://www.estamos.de/
|
|
From: Michael B. <mic...@cm...> - 2010-12-12 20:27:20
|
Hi, I actually write a bunch of mails to eplain my behaviour. Please accept my apologies for any inconvenience caused. Best regards Michael On 12/02/10 12:16, Emanoil Kotsev wrote: > Hi, > > I'm a bit disappointed, because no one is paying attentioin to what we are doing. There are many questions that can be answered in couple of minutes, but it takes weeks and months. > > I've raized few tickets in libsyncml and libopensync because I finally managed to get the magic set of options for syncml-ds-tool to access Contacts, Calendar and Notes in the nokia 5530, which is S60 (not sure which revision). > > Unfortunately Calendar does not work with syncml-ds-tool and Contacts break osynctool. > > The wbxmls for Calendar are OK, but parser breaks (I think as I stated that this is because of DESCRIPTION field present). > > Someone needs to look into this issue to help me improve the library. > > This guy 'bellmich' seems to be dead. Could you kick his ass to be cooperative and get working the bugs out or let us discuss and seek someone who can take over. > > The situation ATM is UNACCEPTABLE! > > thanks in advance and regards > > > > > > ------------------------------------------------------------------------------ > Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! > Tap into the largest installed PC base & get more eyes on your game by > optimizing for Intel(R) Graphics Technology. Get started today with the > Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. > http://p.sf.net/sfu/intelisp-dev2dev > _______________________________________________ > Opensync-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensync-devel -- ___________________________________________________________________ Michael Bell Humboldt-Universitaet zu Berlin Tel.: +49 (0)30-2093 70143 ZE Computer- und Medienservice Fax: +49 (0)30-2093 2704 Unter den Linden 6 mic...@cm... D-10099 Berlin ___________________________________________________________________ PGP Fingerprint: 09E4 3D29 4156 2774 0F2C C643 D8BD 1918 2030 5AAB |
|
From: Michael B. <mic...@cm...> - 2010-12-12 20:24:14
|
Hi, I actually maintain or do not maintain the SyncML stack of OpenSync. The problem is, that the stack is quite too big for one person and I have not the time and motivation to do this in the future. The time has to do with my job and the motivation has to do with general concerns about the design of OpenSync and libsyncml plus a decision towards Active Sync in my university. This decision is not an anonymous decision. It was made in a working group which I lead. I will send three additional mails to make clear what's going on. I split it to make the discussion easier. 1. libwbxml maintenace 2. libsyncml maintenance 3. SyncML plugin Please do not see any of these mails as an offence against OpenSync. It is just my personal opinion to explain my behaviour. Best regards Michael -- ___________________________________________________________________ Michael Bell Humboldt-Universitaet zu Berlin Tel.: +49 (0)30-2093 70143 ZE Computer- und Medienservice Fax: +49 (0)30-2093 2704 Unter den Linden 6 mic...@cm... D-10099 Berlin ___________________________________________________________________ PGP Fingerprint: 09E4 3D29 4156 2774 0F2C C643 D8BD 1918 2030 5AAB |
|
From: Michael B. <mic...@cm...> - 2010-12-12 20:06:23
|
Hi, the libwbxml stack is the base layer under libsyncml if you use WBXML. libwbxml is used by several other software vendors. These software vendors need a working library too. Therefore I have a motivation to take care about this library. Especially because I see no alternative for this C library. So yes I am the maintainer and will be the maintainer in the future. If somebody wants to take over or like to be a maintainer too then he or she is of course very welcome because this makes the process more robust. Best regards Michael -- ___________________________________________________________________ Michael Bell Humboldt-Universitaet zu Berlin Tel.: +49 (0)30-2093 70143 ZE Computer- und Medienservice Fax: +49 (0)30-2093 2704 Unter den Linden 6 mic...@cm... D-10099 Berlin ___________________________________________________________________ PGP Fingerprint: 09E4 3D29 4156 2774 0F2C C643 D8BD 1918 2030 5AAB |
|
From: Michael B. <mic...@cm...> - 2010-12-12 20:05:42
|
Hi, libsyncml is actually a difficult thing for me. There are five issues which influence my actual "non-behaviour": 1. The design/quality of libsyncml 2. The man power behind libsyncml 3. The situation in the Open Source scene 4. Active Sync 5. Time 1.) Libsyncml was not designed by me and there is no up-to-date design documentation. The basic design idea to make things parallel is very good but the first thing which should be designed is the API. The problem is that the robustness of libsyncml depends in the past one the behaviour of the API consumer which must understand the SyncML protocol details very well. I tried to fix this by introduction the DS API but this is more a bug fix for a design problem. So we have in fact two APIs which makes the library not more robust. I write here as programmer and not as a manager. So libsyncml is no fun. The basic ideas are good but we need a second try to get a future ready, robust library. Even the heavily optimized 0.6.0 in svn is just a fix in my eyes. 2.) Libsyncml and even SyncML is complicated. The basic design is not documented. So it is very difficult to find people who want to maintain it. A library like libsyncml needs at minimum 2-3 developers which understand it. Otherwise it is not ready for the future. Actually there is just one pseudo maintainer. 3.) There are two SyncML client implementations available as C libraries - libsynthesis and libsyncml. I know the guys behind libsynthesis and there is definitely more manpower and motivation behind the maintenance especially because libsynthesis is the base for a commercial product. 4.) My university will use Active Sync in the future. I do not want to discuss here why we come to this decision. The result is that I have now only a private motivation to get a working SyncML library. 5.) I have no time any longer to work on the library during my job because I changed the position. The summary is that I will no longer maintain libsyncml. I can provide a potential new developer with all requested informations. I personally would prefer an adaption of libsynthesis to OpenSync because this would cut the costs in terms of man power. Nevertheless it is noteworthy that libsynthesis has no OBEX support today. Best regards Michael -- ___________________________________________________________________ Michael Bell Humboldt-Universitaet zu Berlin Tel.: +49 (0)30-2093 70143 ZE Computer- und Medienservice Fax: +49 (0)30-2093 2704 Unter den Linden 6 mic...@cm... D-10099 Berlin ___________________________________________________________________ PGP Fingerprint: 09E4 3D29 4156 2774 0F2C C643 D8BD 1918 2030 5AAB |
|
From: Michael B. <mic...@cm...> - 2010-12-12 20:05:17
|
Hi, the SyncML plugin heavily depends on libsyncml. So I think a rewrite and the use of a different library would be a possible way. The problem is that libsynthesis does not provide OBEX support. I did stop my work because I cannot work on the plugin during my work time and I have some general concerns on the design of SyncML and OpenSync. SyncML merging will always be a problem. If a device is out of sync and there are changed items on both sides there is always the risk of duplicated entries. I can just note here that this behaviour is just unacceptable for customers with many contacts and events. This leads to our (university's) decision for Active Sync. OpenSync introduces an additional problem for us. It syncs all devices at once and requires a slow sync if there was a problem with just one device. The following slow sync with an enabled merger can create a complexity which is simply too high. Just calculate the effort for a general merger and 5 devices with 100 items each. So I personally prefer peer-to-peer and clear unique identifier designs for synchronization. I hope somebody else has enough motivation to take over the maintenance. If you want to take over then you can expect that I am willing to help with informations. Best regards Michael -- ___________________________________________________________________ Michael Bell Humboldt-Universitaet zu Berlin Tel.: +49 (0)30-2093 70143 ZE Computer- und Medienservice Fax: +49 (0)30-2093 2704 Unter den Linden 6 mic...@cm... D-10099 Berlin ___________________________________________________________________ PGP Fingerprint: 09E4 3D29 4156 2774 0F2C C643 D8BD 1918 2030 5AAB |
|
From: Emanoil K. <del...@ya...> - 2010-12-02 14:17:00
|
Hi, Thanks for replying
--- On Thu, 12/2/10, Chris Frey <cd...@fo...> wrote:
>
> I've been busy with higher priority projects over the last
> months or so,
> and just now trying to finish off a few items pending on
> Barry.
> I'm about 122 messages behind on the opensync-devel mailing
> list, and
> that's not how I intended things to go.
>
> There'll be no "kicking of asses" from my end, though.
> :-) Everyone can
> only code as much as they are able.
Personal issues
*) That guy 'bellmich' - I think is Michael- has pending tickets for more then 8 months now that are not assessed. There has been no activity on the libsyncml code since a long time and the code is not working
*) No one is answering our questions in the dev list.
how are we supposed to help development if no docs and infos are provided.
The code issues
*) libsyncml is not working for Calendar (snycml v1.2) and
*) libopensync is not working for Contacts (seems that there are no issues with parsing the xml provided by syncml)
tickets on libsyncml side
#269 invalid utf8 passed to VFormat. Limping along. ( syncml issues ) Parser 0.5.4 libsyncml 0.6.0 defect blocker bellmich new 12/01/10
#270 invalid character found in attribute group/name: "41" String so far: ( syncml issues ) libsyncml 0.5.4 libsyncml 0.6.0 defect blocker bellmich new 12/01/10
#271 osync_converter_invoke: XMLFormat validation failed. ( syncml issues ) libsyncml 0.5.4 libsyncml 0.6.0 defect blocker bellmich new 12/01/10
#272 "DESCRIPTION:" in calendar items breaks parser libsyncml 0.5.4 libsyncml 0.6.0 defect blocker bellmich new 12/02/10
The syncml is definitely unstable and even worse than libopensync itself and tehn I've expected. We need rapid improvement here as nokia phones will probably fail syncing. I have 5530 with recent OS updated, but the issue is trivial - I guess may be change some xsd will fix it.
In opensync I have problem understanding ref/unref changes in akonadi-sync ... and no one answered what needs to be done and why other plugins have different implementation
I don't want to waste your time - I just need hints of people that know the api, so that I don't reinvent the wheel and spend time working on solving the issues then analysing and hacking the api.
It would be great if you let us focus on syncml together, so that I may (help to) debug and get some satisfying results before christmas this year.
For now akonadi-sync is doing really fine, so what I need is just to get the data out of the phone and even this is possible, but it gets stuck in libsyncml or libopensync.
thanks in advance and regards
regards
|
|
From: Chris F. <cd...@fo...> - 2010-12-02 13:57:32
|
Hi Emanoil, I've been busy with higher priority projects over the last months or so, and just now trying to finish off a few items pending on Barry. I'm about 122 messages behind on the opensync-devel mailing list, and that's not how I intended things to go. There'll be no "kicking of asses" from my end, though. :-) Everyone can only code as much as they are able. I hope to take a closer look at this today. Since I'm 122 messages behind, I'm quite out of the loop... if you can forward me your most important email or bug ticket that you would like help with, I can start from there. Thanks, - Chris On Thu, Dec 02, 2010 at 03:16:05AM -0800, Emanoil Kotsev wrote: > Hi, > > I'm a bit disappointed, because no one is paying attentioin to what we are doing. There are many questions that can be answered in couple of minutes, but it takes weeks and months. > > I've raized few tickets in libsyncml and libopensync because I finally managed to get the magic set of options for syncml-ds-tool to access Contacts, Calendar and Notes in the nokia 5530, which is S60 (not sure which revision). > > Unfortunately Calendar does not work with syncml-ds-tool and Contacts break osynctool. > > The wbxmls for Calendar are OK, but parser breaks (I think as I stated that this is because of DESCRIPTION field present). > > Someone needs to look into this issue to help me improve the library. > > This guy 'bellmich' seems to be dead. Could you kick his ass to be cooperative and get working the bugs out or let us discuss and seek someone who can take over. > > The situation ATM is UNACCEPTABLE! > > thanks in advance and regards > > > > |
|
From: Emanoil K. <del...@ya...> - 2010-12-02 11:16:11
|
Hi,
I'm a bit disappointed, because no one is paying attentioin to what we are doing. There are many questions that can be answered in couple of minutes, but it takes weeks and months.
I've raized few tickets in libsyncml and libopensync because I finally managed to get the magic set of options for syncml-ds-tool to access Contacts, Calendar and Notes in the nokia 5530, which is S60 (not sure which revision).
Unfortunately Calendar does not work with syncml-ds-tool and Contacts break osynctool.
The wbxmls for Calendar are OK, but parser breaks (I think as I stated that this is because of DESCRIPTION field present).
Someone needs to look into this issue to help me improve the library.
This guy 'bellmich' seems to be dead. Could you kick his ass to be cooperative and get working the bugs out or let us discuss and seek someone who can take over.
The situation ATM is UNACCEPTABLE!
thanks in advance and regards
|
|
From: deloptes <del...@ya...> - 2010-12-01 16:04:10
|
I have created tickets for all those problems with syncml regards deloptes wrote: > Can someone please help on understanding following messages > > thanks in advance > > > [1291157933.453789] Dispatching 0x7f24fc001b10:1 > (OSYNC_MESSAGE_NEW_CHANGE), timeout=0, id=0 > [1291157933.453801] >>>>>>> > _osync_client_proxy_message_handler(0x7f24fc001b10, 0x1893e20) > [1291157933.453821] proxy received command 10 > [1291157933.453835] Data is: 0x1bc0750, 132 > [1291157933.453848] >>>>>>> > _osync_engine_receive_change(0x1893e20, 0x16cffd0, 0x1bbc150) > [1291157933.453861] Received change > [GoEvA3ndrX, > changetype 1, format vcard30, objtype contact from member 2 > [1291157933.453874] >>>>>>> > osync_format_env_detect_objformat_full(0x16d26b0, 0x1bc04d0, > 0x7f250bdf7c28, 0x7f250bdf7c30) > [1291157933.453887] We cannot copy the > change, falling back to memcpy > [1291157933.453901] <<<<<<< > osync_format_env_detect_objformat_full: (nil) > [1291157933.453953] common format 0x16d33f0 > [for > objtype contact > [1291157933.453965] converting to format > xmlformat-contact > [1291157933.453978] >>>>>>> > osync_format_env_convert(0x16d26b0, 0x7f2504002f50, 0x1bc04d0, > 0x7f250bdf7c30) > [1291157933.453992] >>>>>>> > osync_converter_invoke(0x16d45b0, 0x1bc04d0, , 0x7f250bdf7c30) > [1291157933.454005] Converter > [of > type 1, from 0x16d2ca0(vcard30) to 0x16d33f0(xmlformat-contact) > [1291157933.454018] >>>>>>> > Converter function from "vcard30" to "xmlformat-contact" - input_data: > 0x1bc0750 input_size: 132 > [1291157933.454033] >>>>>>>> conv_vcard_to_xmlformat(BEGIN:VCARD > FN:Ambulance > N:;Ambulance;;; > REV:2008-11-11T05:29:51Z > TEL;TYPE=VOICE:150 > UID:GoEvA3ndrX > VERSION:3.0 > END:VCARD > > �, 132, 0x7f250bdf7b10, 0x7f250bdf7b28, 0x7f250bdf7b24, , (nil), > 0x7f250bdf7c30) > [1291157933.454047] >>>>>>>> init_vcard_to_xmlformat > [1291157933.454064] > <<<<<<< init_vcard_to_xmlformat: 0x1bbf890 > [1291157933.454076] > [SENSITIVE CONTENT HIDDEN] > [1291157933.454089] > invalid utf8 passed to VFormat. Limping along. > [1291157933.454123] > Creating xmlformat object > [1291157933.454135] >>>>>>>> osync_xmlformat_new(0x7f251ed17230, 0x7f250bdf7c30) > [1291157933.454148] > <<<<<<< osync_xmlformat_new: 0x1bbf570 > [1291157933.454160] > parsing attributes > [1291157933.454173] >>>>>>>> handle_attribute(0x7f250400e320, 0x7f250400e370, 0x1bbf570, > 0x1bbef70:FN, 0x7f250bdf7c30) > > > or > > > [1291157933.536848] >>>>>>>> init_vcard_to_xmlformat > [1291157933.536865] > <<<<<<< init_vcard_to_xmlformat: 0x7f2504043160 > [1291157933.536877] > [SENSITIVE CONTENT HIDDEN] > [1291157933.536912] > invalid character found in attribute group/name: "41" String so far: > [1291157933.536925] > Creating xmlformat object > [1291157933.536937] >>>>>>>> osync_xmlformat_new(0x7f251ed17230, 0x7f250bdf7c30) > [1291157933.536951] > <<<<<<< osync_xmlformat_new: 0x7f25040456c0 > [1291157933.536963] > parsing attributes > > > but > > [1291157933.554215] >>>>>>>> init_vcard_to_xmlformat > [1291157933.554232] > <<<<<<< init_vcard_to_xmlformat: 0x7f250405d660 > [1291157933.554245] > [SENSITIVE CONTENT HIDDEN] > [1291157933.554291] > Creating xmlformat object > [1291157933.554303] >>>>>>>> osync_xmlformat_new(0x7f251ed17230, 0x7f250bdf7c30) > [1291157933.554316] > <<<<<<< osync_xmlformat_new: 0x7f250405b430 > [1291157933.554328] > parsing attributes > > > also > > > [1291157938.561816] >>>>>>>> conv_vcard_to_xmlformat(BEGIN:VCARD > VERSION:2.1 > REV:20100725T123728Z > N:XXXXXXXXXX;XXXXXXX;;; > FN:XXXXXXXX XXXXXXXXXX > ADR;HOME;ENCODING=QUOTED-PRINTABLE;CHARSET=utf-8:= > x/x/x;;xxxxxxxx=0D=0ANr.=207=0D=0AStiege=202=0D=0AT=C3=BCr=208;Wien;;= > 1070;=C3=96sterreich > ORG:;4 Semester > BDAY:19840423 > EMAIL;INTERNET;ENCODING=QUOTED-PRINTABLE:ich=40xxxxxxxxxxxxxxx > GEO:48.150002\;17.116667 > KEY;PGP;ENCODING=BASE64: > mQGiBEUgu50RBAC9i47QyffjcdSrtDya1kzDeMULtmuzA2N7KqOgeLm70tvpEYkl > KAzEi0Whhf4C5uKeEnusdDiE71cBL9X5eiv5boWbk4XeoOJT+IehZmFLeTkFvg3w > Uf9pvmTNGJJGLa80KTpKE8KpbmKhfgXmsyzAE+nXEg3p8Qss9MHDvPrXnwCgpaMy > 0LBpXGqA3C5KtwWkMJTFcx0EAI3/e17yStTlZ3QBYC7XlEvlPQznhNSncdcLlquI > > ... > ... > [1291157938.563697] > <<<<<<< conv_vcard_to_xmlformat: TRUE > [1291157938.563711] <<<<<<< > Converter function. output_size: 56, output_data: 0x7f24fc114bf0 > [1291157938.563723] >>>>>>> > validate_xmlformat(0x7f24fc114bf0, 56, 0x16d4010, 0x7f250bdf7c30) > [1291157938.563797] ERROR: > XMLFormat validation failed. > [1291157938.563814] <<<<<<< > validate_xmlformat: FALSE > [1291157938.563826] <--- ERROR --- > osync_converter_invoke: XMLFormat validation failed. > [1291157938.563844] <--- ERROR --- > osync_format_env_convert: XMLFormat validation failed. > [1291157938.563859] >>>>>>> > osync_status_update_member(0x16cffd0, 0x19305e0, 3, (null), > 0x7f24fc112bd0) > [1291157938.563873] >>>>>>> > member_status(0x7f24fc1136e0, (nil)) > [1291157938.563891] <<<<<<< > member_status > [1291157938.563903] <<<<<<< > osync_status_update_member > [1291157938.563915] <--- ERROR --- > _osync_engine_receive_change: XMLFormat validation failed. > [1291157938.563930] <<<<<<< > [_osync_client_proxy_message_handler > [1291157938.563943] Dispatching 0x1c7eac0:1 > (OSYNC_MESSAGE_NEW_CHANGE), timeout=0, id=0 > [1291157938.563955] >>>>>>> > _osync_client_proxy_message_handler(0x1c7eac0, 0x7f250400a550) > > > [1291157941.485932] >>>>>>> > osync_format_env_convert(0x16d26b0, 0x1c29ab0, 0x7f25040a7b20, > 0x7f250bdf7c30) > [1291157941.485946] >>>>>>> > osync_converter_invoke(0x16d4510, 0x7f25040a7b20, , 0x7f250bdf7c30) > [1291157941.485960] Converter > [of > type 1, from 0x16d2b60(vcard21) to 0x16d33f0(xmlformat-contact) > [1291157941.485974] >>>>>>> > Converter function from "vcard21" to "xmlformat-contact" - input_data: > 0x7f250411d5c0 input_size: 519 > [1291157941.485990] >>>>>>>> conv_vcard_to_xmlformat(BEGIN:VCARD > VERSION:2.1 > REV:20101003T031714Z > N;ENCODING=QUOTED-PRINTABLE;CHARSET=utf-8:Zubeh=C3=B6r;;;; > ORG:Palm Computing, Inc.; > NOTE;ENCODING=QUOTED-PRINTABLE;CHARSET=utf-8:= > Hinweis:=20Mehr=20Infos=20=C3=BCber=20Zubeh=C3=B6r,=20n=C3=BCtzliche=20= > Add-On-Software=20und=20Ersatzteile=20finden=20Sie=20auf=20unserer=20We= > bsite=20unter=20www.palm.com.=20Au=C3=9Ferhalb=20der=20USA=20rufen=20Si= > e=20bitte=20eine=20der=20InfoLine-Nummern=20auf=20der=20internationalen= > =20Kundenunterst=C3=BCtzungskarte=20an. > END:VCARD > , 519, 0x7f250bdf7b10, 0x7f250bdf7b28, 0x7f250bdf7b24, , (nil), > 0x7f250bdf7c30) > [1291157941.486004] >>>>>>>> init_vcard_to_xmlformat > [1291157941.486022] > <<<<<<< init_vcard_to_xmlformat: 0x7f25040a5650 > [1291157941.486036] > [SENSITIVE CONTENT HIDDEN] > [1291157941.486096] > invalid character found in attribute group/name: "61" String so far: > Add-On-Software > [1291157941.486111] > invalid character found in attribute group/name: "61" String so far: bsite > [1291157941.486124] > invalid character found in attribute group/name: "61" String so far: e > [1291157941.486138] > invalid character found in attribute group/name: "61" String so far: > [1291157941.486153] > Creating xmlformat object > [1291157941.486166] >>>>>>>> osync_xmlformat_new(0x7f251ed17230, 0x7f250bdf7c30) > [1291157941.486181] > <<<<<<< osync_xmlformat_new: 0x7f25041073b0 > [1291157941.486193] > parsing attributes > > > > ------------------------------------------------------------------------------ > Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! > Tap into the largest installed PC base & get more eyes on your game by > optimizing for Intel(R) Graphics Technology. Get started today with the > Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. > http://p.sf.net/sfu/intelisp-dev2dev > _______________________________________________ > Opensync-devel mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opensync-devel |
|
From: deloptes <del...@ya...> - 2010-12-01 01:00:40
|
when trying to sync Calendar syncml-ds-tool -b XX:XX:XX:XX:XX:XX 7 --wbxml --read-only --identifier "PC Suite" --version "1.2" --wbxml --sync text/x-vcalendar Calendar /tmp/testdir/ [1291164984.666626] smlSessionReceiveBody: command iteration. [1291164984.666641] >>>>>>> smlParserGetCommand(0x7f42f8001c80, 0x7f42fd5e86f8, 0x7f42fd5e8838) [1291164984.666656] >>>>>>> smlXmlParserGetCommand(0x7f42f8000cd0, 0x7f42fd5e86f8, 0x7f42fd5e8838) [1291164984.666672] >>>>>>> _smlChangeParse(0x7f42f8000cd0, 5, Add, 0x7f42fd5e8838) [1291164984.666687] >>>>>>> smlCommandNew(5, 0x7f42fd5e8838) [1291164984.666701] <<<<<<< smlCommandNew: 0xe6d5a0 [1291164984.666717] >>>>>>> _smlItemParse(0x7f42f8000cd0, 0xe6d5a0, 5, 0x7f42fd5e8838) [1291164984.666733] >>>>>>> smlItemNew(0, 0x7f42fd5e8838) [1291164984.666747] <<<<<<< smlItemNew: 0xe6d960 [1291164984.666762] >>>>>>> _smlLocationParse(0x7f42fd5e8530, 0x7f42f8000cd0, 0x7f42fd5e8838) [1291164984.666782] <<<<<<< _smlLocationParse [1291164984.666799] >>>>>>> _smlCommandMetaParse(0x7f42f8000cd0, (nil), 0xe6d990, (nil), 0xe6d608, (nil), 0x7f42fd5e8838) [1291164984.666840] <--- ERROR --- _smlCommandMetaParse: No node at all [1291164984.666856] >>>>>>> smlItemUnref(0xe6d960) [1291164984.666870] smlItemUnref: Refcount == 0! [1291164984.666887] <<<<<<< smlItemUnref: 0 [1291164984.666902] <--- ERROR --- _smlItemParse: No node at all [1291164984.666916] >>>>>>> smlCommandUnref(0xe6d5a0) [1291164984.666931] smlCommandUnref: Refcount == 0! [1291164984.666945] <<<<<<< smlCommandUnref [1291164984.666960] <--- ERROR --- _smlChangeParse: No node at all [1291164984.666974] <--- ERROR --- smlXmlParserGetCommand: No node at all [1291164984.666989] <--- ERROR --- smlParserGetCommand: No node at all [1291164984.667003] <--- ERROR --- smlSessionReceiveBody: No node at all [1291164984.667018] >>>>>>> smlParserFree(0x7f42f8001c80) [1291164984.667032] >>>>>>> smlXmlParserFree(0x7f42f8000cd0) [1291164984.667061] <<<<<<< smlXmlParserFree [1291164984.667076] <<<<<<< smlParserFree [1291164984.667090] >>>>>>> smlSessionUnlock [1291164984.667104] <<<<<<< smlSessionUnlock |
|
From: deloptes <del...@ya...> - 2010-12-01 00:33:36
|
Can someone please help on understanding following messages
thanks in advance
[1291157933.453789] Dispatching 0x7f24fc001b10:1
(OSYNC_MESSAGE_NEW_CHANGE), timeout=0, id=0
[1291157933.453801] >>>>>>>
_osync_client_proxy_message_handler(0x7f24fc001b10, 0x1893e20)
[1291157933.453821] proxy received command 10
[1291157933.453835] Data is: 0x1bc0750, 132
[1291157933.453848] >>>>>>>
_osync_engine_receive_change(0x1893e20, 0x16cffd0, 0x1bbc150)
[1291157933.453861] Received change GoEvA3ndrX,
changetype 1, format vcard30, objtype contact from member 2
[1291157933.453874] >>>>>>>
osync_format_env_detect_objformat_full(0x16d26b0, 0x1bc04d0,
0x7f250bdf7c28, 0x7f250bdf7c30)
[1291157933.453887] We cannot copy the
change, falling back to memcpy
[1291157933.453901] <<<<<<<
osync_format_env_detect_objformat_full: (nil)
[1291157933.453953] common format 0x16d33f0 for
objtype contact
[1291157933.453965] converting to format
xmlformat-contact
[1291157933.453978] >>>>>>>
osync_format_env_convert(0x16d26b0, 0x7f2504002f50, 0x1bc04d0,
0x7f250bdf7c30)
[1291157933.453992] >>>>>>>
osync_converter_invoke(0x16d45b0, 0x1bc04d0, , 0x7f250bdf7c30)
[1291157933.454005] Converter of
type 1, from 0x16d2ca0(vcard30) to 0x16d33f0(xmlformat-contact)
[1291157933.454018] >>>>>>>
Converter function from "vcard30" to "xmlformat-contact" - input_data:
0x1bc0750 input_size: 132
[1291157933.454033]
>>>>>>> conv_vcard_to_xmlformat(BEGIN:VCARD
FN:Ambulance
N:;Ambulance;;;
REV:2008-11-11T05:29:51Z
TEL;TYPE=VOICE:150
UID:GoEvA3ndrX
VERSION:3.0
END:VCARD
�, 132, 0x7f250bdf7b10, 0x7f250bdf7b28, 0x7f250bdf7b24, , (nil),
0x7f250bdf7c30)
[1291157933.454047]
>>>>>>> init_vcard_to_xmlformat
[1291157933.454064]
<<<<<<< init_vcard_to_xmlformat: 0x1bbf890
[1291157933.454076]
[SENSITIVE CONTENT HIDDEN]
[1291157933.454089]
invalid utf8 passed to VFormat. Limping along.
[1291157933.454123]
Creating xmlformat object
[1291157933.454135]
>>>>>>> osync_xmlformat_new(0x7f251ed17230, 0x7f250bdf7c30)
[1291157933.454148]
<<<<<<< osync_xmlformat_new: 0x1bbf570
[1291157933.454160]
parsing attributes
[1291157933.454173]
>>>>>>> handle_attribute(0x7f250400e320, 0x7f250400e370, 0x1bbf570,
0x1bbef70:FN, 0x7f250bdf7c30)
or
[1291157933.536848]
>>>>>>> init_vcard_to_xmlformat
[1291157933.536865]
<<<<<<< init_vcard_to_xmlformat: 0x7f2504043160
[1291157933.536877]
[SENSITIVE CONTENT HIDDEN]
[1291157933.536912]
invalid character found in attribute group/name: "41" String so far:
[1291157933.536925]
Creating xmlformat object
[1291157933.536937]
>>>>>>> osync_xmlformat_new(0x7f251ed17230, 0x7f250bdf7c30)
[1291157933.536951]
<<<<<<< osync_xmlformat_new: 0x7f25040456c0
[1291157933.536963]
parsing attributes
but
[1291157933.554215]
>>>>>>> init_vcard_to_xmlformat
[1291157933.554232]
<<<<<<< init_vcard_to_xmlformat: 0x7f250405d660
[1291157933.554245]
[SENSITIVE CONTENT HIDDEN]
[1291157933.554291]
Creating xmlformat object
[1291157933.554303]
>>>>>>> osync_xmlformat_new(0x7f251ed17230, 0x7f250bdf7c30)
[1291157933.554316]
<<<<<<< osync_xmlformat_new: 0x7f250405b430
[1291157933.554328]
parsing attributes
also
[1291157938.561816]
>>>>>>> conv_vcard_to_xmlformat(BEGIN:VCARD
VERSION:2.1
REV:20100725T123728Z
N:XXXXXXXXXX;XXXXXXX;;;
FN:XXXXXXXX XXXXXXXXXX
ADR;HOME;ENCODING=QUOTED-PRINTABLE;CHARSET=utf-8:=
x/x/x;;xxxxxxxx=0D=0ANr.=207=0D=0AStiege=202=0D=0AT=C3=BCr=208;Wien;;=
1070;=C3=96sterreich
ORG:;4 Semester
BDAY:19840423
EMAIL;INTERNET;ENCODING=QUOTED-PRINTABLE:ich=40xxxxxxxxxxxxxxx
GEO:48.150002\;17.116667
KEY;PGP;ENCODING=BASE64:
mQGiBEUgu50RBAC9i47QyffjcdSrtDya1kzDeMULtmuzA2N7KqOgeLm70tvpEYkl
KAzEi0Whhf4C5uKeEnusdDiE71cBL9X5eiv5boWbk4XeoOJT+IehZmFLeTkFvg3w
Uf9pvmTNGJJGLa80KTpKE8KpbmKhfgXmsyzAE+nXEg3p8Qss9MHDvPrXnwCgpaMy
0LBpXGqA3C5KtwWkMJTFcx0EAI3/e17yStTlZ3QBYC7XlEvlPQznhNSncdcLlquI
...
...
[1291157938.563697]
<<<<<<< conv_vcard_to_xmlformat: TRUE
[1291157938.563711] <<<<<<<
Converter function. output_size: 56, output_data: 0x7f24fc114bf0
[1291157938.563723] >>>>>>>
validate_xmlformat(0x7f24fc114bf0, 56, 0x16d4010, 0x7f250bdf7c30)
[1291157938.563797] ERROR:
XMLFormat validation failed.
[1291157938.563814] <<<<<<<
validate_xmlformat: FALSE
[1291157938.563826] <--- ERROR ---
osync_converter_invoke: XMLFormat validation failed.
[1291157938.563844] <--- ERROR ---
osync_format_env_convert: XMLFormat validation failed.
[1291157938.563859] >>>>>>>
osync_status_update_member(0x16cffd0, 0x19305e0, 3, (null), 0x7f24fc112bd0)
[1291157938.563873] >>>>>>>
member_status(0x7f24fc1136e0, (nil))
[1291157938.563891] <<<<<<<
member_status
[1291157938.563903] <<<<<<<
osync_status_update_member
[1291157938.563915] <--- ERROR ---
_osync_engine_receive_change: XMLFormat validation failed.
[1291157938.563930] <<<<<<< _osync_client_proxy_message_handler
[1291157938.563943] Dispatching 0x1c7eac0:1
(OSYNC_MESSAGE_NEW_CHANGE), timeout=0, id=0
[1291157938.563955] >>>>>>>
_osync_client_proxy_message_handler(0x1c7eac0, 0x7f250400a550)
[1291157941.485932] >>>>>>>
osync_format_env_convert(0x16d26b0, 0x1c29ab0, 0x7f25040a7b20,
0x7f250bdf7c30)
[1291157941.485946] >>>>>>>
osync_converter_invoke(0x16d4510, 0x7f25040a7b20, , 0x7f250bdf7c30)
[1291157941.485960] Converter of
type 1, from 0x16d2b60(vcard21) to 0x16d33f0(xmlformat-contact)
[1291157941.485974] >>>>>>>
Converter function from "vcard21" to "xmlformat-contact" - input_data:
0x7f250411d5c0 input_size: 519
[1291157941.485990]
>>>>>>> conv_vcard_to_xmlformat(BEGIN:VCARD
VERSION:2.1
REV:20101003T031714Z
N;ENCODING=QUOTED-PRINTABLE;CHARSET=utf-8:Zubeh=C3=B6r;;;;
ORG:Palm Computing, Inc.;
NOTE;ENCODING=QUOTED-PRINTABLE;CHARSET=utf-8:=
Hinweis:=20Mehr=20Infos=20=C3=BCber=20Zubeh=C3=B6r,=20n=C3=BCtzliche=20=
Add-On-Software=20und=20Ersatzteile=20finden=20Sie=20auf=20unserer=20We=
bsite=20unter=20www.palm.com.=20Au=C3=9Ferhalb=20der=20USA=20rufen=20Si=
e=20bitte=20eine=20der=20InfoLine-Nummern=20auf=20der=20internationalen=
=20Kundenunterst=C3=BCtzungskarte=20an.
END:VCARD
, 519, 0x7f250bdf7b10, 0x7f250bdf7b28, 0x7f250bdf7b24, , (nil),
0x7f250bdf7c30)
[1291157941.486004]
>>>>>>> init_vcard_to_xmlformat
[1291157941.486022]
<<<<<<< init_vcard_to_xmlformat: 0x7f25040a5650
[1291157941.486036]
[SENSITIVE CONTENT HIDDEN]
[1291157941.486096]
invalid character found in attribute group/name: "61" String so far:
Add-On-Software
[1291157941.486111]
invalid character found in attribute group/name: "61" String so far: bsite
[1291157941.486124]
invalid character found in attribute group/name: "61" String so far: e
[1291157941.486138]
invalid character found in attribute group/name: "61" String so far:
[1291157941.486153]
Creating xmlformat object
[1291157941.486166]
>>>>>>> osync_xmlformat_new(0x7f251ed17230, 0x7f250bdf7c30)
[1291157941.486181]
<<<<<<< osync_xmlformat_new: 0x7f25041073b0
[1291157941.486193]
parsing attributes
|
|
From: deloptes <del...@ya...> - 2010-11-30 08:12:41
|
Mark Ellis wrote: > Hi All > > I noticed akonadi-sync makes a hardcoded assumption about where the > build directory is, in this case in the source dir. > > Attached a patch to fix this, would have committed it myself but I know > there is work going on there. > > Mark I've applied the proposed patch i svn rev 6162 regards |
|
From: deloptes <del...@ya...> - 2010-11-30 00:28:21
|
There is a proress but it seems something is not transformed properly. I'll try to debug in near feature and see if Calendar would work too. Received an entry 536 (xmlformat-contact) from member 1 (syncml-obex-client). Changetype ADDED Received an entry 538 (xmlformat-contact) from member 1 (syncml-obex-client). Changetype ADDED element Location: Schemas validity error : Element 'Location': Missing child element(s). Expected is ( Longitude ). ERROR: XMLFormat validation failed. EXIT_ERROR: osync_converter_invoke: XMLFormat validation failed. EXIT_ERROR: osync_format_env_convert: XMLFormat validation failed. Main sink of member 1 of type syncml-obex-client had an error: XMLFormat validation failed. EXIT_ERROR: _osync_engine_receive_change: XMLFormat validation failed. Received an entry 541 (xmlformat-contact) from member 1 (syncml-obex-client). Changetype ADDED Received an entry 547 (xmlformat-contact) from member 1 (syncml-obex-client). Changetype ADDED ... ... Received an entry 884 (xmlformat-contact) from member 1 (syncml-obex-client). Changetype ADDED Received an entry 885 (xmlformat-contact) from member 1 (syncml-obex-client). Changetype ADDED contact sink of member 1 of type syncml-obex-client just sent all changes All clients sent changes or error EXIT_ERROR: osync_status_conflict: Engine has an error. Sync got abortd?! EXIT_ERROR: osync_mapping_engine_check_conflict ERROR: Error while resolving conflicts ERROR: At least one object engine failed while mapping changes. Aborting ERROR: At least one object engine failed while mapping changes. Aborting The sync failed: At least one object engine failed while mapping changes. Aborting ERROR: Engine aborting due to an error: At least one object engine failed while mapping changes. Aborting contact sink of member 1 of type syncml-obex-client just disconnected contact sink of member 2 of type akonadi-sync just disconnected Main sink of member 2 of type akonadi-sync just disconnected regards |
|
From: deloptes <del...@ya...> - 2010-11-29 23:37:27
|
Mark Ellis wrote: > Hi All > > I noticed akonadi-sync makes a hardcoded assumption about where the > build directory is, in this case in the source dir. > > Attached a patch to fix this, would have committed it myself but I know > there is work going on there. > > Mark Thanks, but unfortanately I can not update the code at the moment. Could you make a ticket to keep it listed until access is possible svn: Übertragen schlug fehl (Details folgen): svn: MKACTIVITY von »/!svn/act/ea96a919-7937-4016-8559-8718c995ab7d«: Autorisierung schlug fehl: Could not authenticate to server: rejected Basic challenge (http://svn.opensync.org) svn: Ihre Logmeldung wurde in einer Temporärdatei abgelegt: svn: '/tmp/trunk/svn-commit.tmp' regards |
|
From: deloptes <del...@ya...> - 2010-11-29 23:27:05
|
I have nokia 5530 to test sycml syncml-ds-tool -b XX:XX:07:94:XX:XX 7 --wbxml --read-only --identifier "PC Suite" --version "1.2" --sync text/x-vcard Contacts --wbxml produces output but nothing I can do for Calendar Could someone give an example, please. |
|
From: Mark E. <ma...@mp...> - 2010-11-29 16:13:49
|
Hi All I noticed akonadi-sync makes a hardcoded assumption about where the build directory is, in this case in the source dir. Attached a patch to fix this, would have committed it myself but I know there is work going on there. Mark |
90 messages has been excluded from this view by a project administrator.
