opensync-users — The place to get help for the OpenSync project

[Opensync-users] Nokia 3110 Classic: "Member 2 of type syncml-obex-client had an error while getting changes: Request not successfull: 64"

[S. B. <ste...@gm...>]

After rigorous testing of alternative configuration an methods, I
still can't get SyncML over Bluetooth work with my Nokia 3110c.
Synchronization begins, then either hangs forever or fails with the
following error message:

[...]
Member 1 of type evo2-sync just sent all changes
Member 2 of type syncml-obex-client had an error while getting
changes: Request not successfull: 64
Member 1 of type evo2-sync just disconnected
Member 2 of type syncml-obex-client just disconnected
All clients have disconnected
The sync failed: Unable to read from one of the members
Error synchronizing: Unable to read from one of the members
Pipe closed! Exiting.

The phone spits out an error at the beginning of the synchronization
process, which makes me think that syncml-obex-client fails at the
beginning. Curiously, I have managed to synchronize all contacts,
calendar and tasks with Evolution -- but my phone seem unable to
synchronize with Evolution.

Anyway, what does this error code 64 mean?

Stefan

Re: [Opensync-users] Where to start?

[Martin O. <doc...@gm...>]

> It has already been decided that libopensync is a sync engine tying 
> format and connection plugins together. Other projects are free to
> implement upper layers and utilize libopensync as such engine.

The only problem I can see is one of position. If a project does not
expect to be used in a certain way it won't provide the required APIs or
be orientated in such a way as to make creating those other layers
impossible.

For instance the config files in 0.3x slaughter the possibility of
hardware detection and hal integration without having hackish glue.

While I can agree that small blocks are a good idea, if one of your
interfaces is expected to be hardware, you should at the very least
expect hal integration in other layers and understand what that means.
and at most lay groundwork for supporting it.

> Not sure. I do know that there are projects that somewhat overlap with this, implementing 
> their own sync engine and GUI, all those hw detection layers etc. 
> But imo it's good to have stuff in smaller chunks and keep simple 
> interfaces between those.

I'm going to be working on peer access, I believe it's more important
than syncing at the moment. An important divide into smaller blocks
would have been one project to provide data access another to do format
translation and yet another to provide syncing logic.

Providing a singular use case scenario from which developers/users can
build outwards may have been a better strategy than building as wide a
base of support without an end to end stack;

1) Hardware Detection (HAL)
2) Hardware Data Access (Unknown, Various, OpenSync)
3) Online Detection (Network Manager)
4) Online Services Access (Unknown, various, OpenSync)
5) Syncing (OpenSync, Conduit)
6) GUI Integration (Conduit Some)

We're no were near delivering something useful to users looking at end
to end stack.

Regards, Martin

Re: [Opensync-users] Where to start?

[Juha T. <Juh...@ik...>]

On Wednesday 19 November 2008 19:22:02 Martin Owens wrote:
> On Wed, 2008-11-19 at 17:15 +0000, Chris Carr wrote:
> > Just wanted to chime in and say to Dotan that you're not alone - I too have
> > just arrived that the conclusion that I'm fed up with Nokia's windows
> > bloat-suite and I want to get opensync working for me, and I too am not a
> > programmer. 
> 
> How goes integration work into the hardware layers? I haven't heard much
> about how opensync is going to work in the future when you plug in
> various devices or pair them up bluz wise.

It has already been decided that libopensync is a sync engine tying 
format and connection plugins together. Other projects are free to
implement upper layers and utilize libopensync as such engine.

Go to http://www.ohloh.net/ and compare opensync with for example Apache.
This is not a small project and community/manpower to develop is way
much smaller than other similar sized projects. 

Hopefully that will change somewhat once we have more polished product.

> Or are the systems not yet in place for this kind of integration? I've
> been trying to push libbarry (blackberry support) to getting HAL device
> capabilities listed.

Not sure. I do know that there are projects that somewhat overlap with this, implementing 
their own sync engine and GUI, all those hw detection layers etc. 
But imo it's good to have stuff in smaller chunks and keep simple 
interfaces between those.


Tuju

-- 
Varo hattupäisiä autoilijoita.

Re: [Opensync-users] Where to start?

[Martin O. <doc...@gm...>]

On Wed, 2008-11-19 at 17:15 +0000, Chris Carr wrote:
> Just wanted to chime in and say to Dotan that you're not alone - I too have
> just arrived that the conclusion that I'm fed up with Nokia's windows
> bloat-suite and I want to get opensync working for me, and I too am not a
> programmer. 

How goes integration work into the hardware layers? I haven't heard much
about how opensync is going to work in the future when you plug in
various devices or pair them up bluz wise.

Or are the systems not yet in place for this kind of integration? I've
been trying to push libbarry (blackberry support) to getting HAL device
capabilities listed.

Regards, Martin

Re: [Opensync-users] Where to start?

[Chris C. <ran...@gm...>]

Just wanted to chime in and say to Dotan that you're not alone - I too have
just arrived that the conclusion that I'm fed up with Nokia's windows
bloat-suite and I want to get opensync working for me, and I too am not a
programmer. 

> On Wednesday 19 November 2008 18:25:53 Dotan Cohen wrote:
> > > I've E71 too here. And i use KDE.
> > Excellent, this is encouraging.
> 
> actually i think the e71 is our libsyncml s60 dedicated 
> test device, so yes in that area we're in good shape.

I have an E90, which runs S60 3rd Edition, which I think is the same
platform as the E71.
 
> > > current opensync might work as 0.2x what you probably 
> > > find from your distro.
 
I run Debian Lenny, which has 0.22

I'm willing to install and test 0.22, but is there much point, since so much
development has taken place in 0.3x?

> > How do I test that? I have here a phone, a usb cable, a bluetooth
> > connection, and a laptop computer. What should I do first? Second?
> 
> Well, usb is quite easy to get working as you don't need to pair it.
> bt is probably more used/tested. There should be instructions below
> that docs/0.2x tree, find them from titleIndex. Yep, there are quite
> a lot pages, i know :-/
> 
> > I am willing to test SVN. I can backup both the phone 
> 
> Yes, e71/s60 has its own backuptoo inside.
> 
> > and the laptop. 
> 
> you could start from file-sync plugin, that needs just empty dir.
> 
> > How to build? 
> 
> that should be up to date in wiki. You just need to repeat every 
> step for each plugin. 
> 
>   http://opensync.org/wiki/docs/trunk
> 
> 
> note that it will install to /usr/local which is not under 
> package control
> and you need to remove it manually in case you want to get rid of it.

I have limited experience with SVN but I would be willing to experiment with
the development code. I tend to do my compiling on a different machine
(running Debian Sid), and then install the compiled binaries on my main
Lenny machine. I presume I could do that with 0.3x
 
> > I do contribute docs to some small opensource programs that 
> > I use (Zim
> > wiki, for example). However you do not want _me_ to write 
> > the docs for
> > opensync! If I do manage to get my E71 and KDE-PIM syncing, 
> > however, I
> > promise to document and publish the method.
> 
> Read existing trunk docs, comment them and we make them better. that's
> already a huge help.

It can often be very helpful for documentation to be written/edited by a
user rather than a developer, because a user is less likely to make
erroneous assumptions about what users need to know (or not). 
 
> > Nor can I code in C. I will join the IRC channel when I have some
> > time. Is there a preferable weekday / hour when knowledgable people
> > are on IRC?
> 
> Most of the people hang out there 24/7, we'll be waiting you.

See you there,

Chris ("Magnate" on IRC)

Re: [Opensync-users] Where to start?

[Juha T. <Juh...@ik...>]

On Wednesday 19 November 2008 18:25:53 Dotan Cohen wrote:
> > I've E71 too here. And i use KDE.
> Excellent, this is encouraging.

actually i think the e71 is our libsyncml s60 dedicated 
test device, so yes in that area we're in good shape.

> Other than that, there is a problem/solution page 
> that is so far over my head that I will not even begin to google the
> terms on the page at this stage.

yep, i remember seeing that too once. But cannot remember where.


> > current opensync might work as 0.2x what you probably find from your distro.
> 
> How do I test that? I have here a phone, a usb cable, a bluetooth
> connection, and a laptop computer. What should I do first? Second?

Well, usb is quite easy to get working as you don't need to pair it.
bt is probably more used/tested. There should be instructions below
that docs/0.2x tree, find them from titleIndex. Yep, there are quite
a lot pages, i know :-/


> I am willing to test SVN. I can backup both the phone 

Yes, e71/s60 has its own backuptoo inside.

> and the laptop. 

you could start from file-sync plugin, that needs just empty dir.

> How to build? 

that should be up to date in wiki. You just need to repeat every 
step for each plugin. 

  http://opensync.org/wiki/docs/trunk


note that it will install to /usr/local which is not under package control
and you need to remove it manually in case you want to get rid of it.

> I do contribute docs to some small opensource programs that I use (Zim
> wiki, for example). However you do not want _me_ to write the docs for
> opensync! If I do manage to get my E71 and KDE-PIM syncing, however, I
> promise to document and publish the method.

Read existing trunk docs, comment them and we make them better. that's
already a huge help.


> Nor can I code in C. I will join the IRC channel when I have some
> time. Is there a preferable weekday / hour when knowledgable people
> are on IRC?

Most of the people hang out there 24/7, we'll be waiting you.


Tuju

-- 
Varo hattupäisiä autoilijoita.

Re: [Opensync-users] Where to start?

[Dotan C. <dot...@gm...>]

2008/11/19 Juha Tuomala <Juh...@ik...>:
> On Wednesday 19 November 2008 17:34:48 Dotan Cohen wrote:
>> I need to sync my KDE-PIM calendar with either my Nokia E71 or my
>> Nokia 6288.
>
> I've E71 too here. And i use KDE.
>

Excellent, this is encouraging.

>> Opensync 0.22 is already installed on my Kubuntu 8.04 (KDE
>> 3.5.10) machine.
>
> Good news: 0.2x versions have kdepim plugin
> Bad news: 0.2x does not really work, that's why the big changes started for 0.40.
>

Which will not be ready for some time, I understand.

> Part of my last week meeting's action points were to make some
> kind of guidelines for wiki and it's due tomorrow so this will
> get better today evening.
>

Excellent, I will refer back to the docs next week when I have some
more time. Thanks.

>> So I then turned to Google and searched on the keywords "kde,
>> opensync, nokia". I did not get very far. Where to go from here? This
>> is not a troll but a real question: Is opensync meant to be used by
>> regular joes like me (mechanical engineers, not computer programmers)?
>
> Yes it is. Part of the goals for 0.40 release were to make it way much
> easier in many ways and it has already achived quite a few of them. One
> is to make configuration easier. We're already working with the installation
> docs. Once we get the 0.40 release out, all distros will pick it and you don't
> have to worry about the installation, which is somewhat laborious at the
> moment.
>

This is very encouraging. So long as the project is moving in that
direction. I am patient, and can scrape by today.

>> If so, where is the documentation?
>
>  http://www.opensync.org/wiki/TitleIndex
>

Regarding KDE, I see a message that Novel sponsored an opensync-kde
meeting in 2005. Other than that, there is a problem/solution page
that is so far over my head that I will not even begin to google the
terms on the page at this stage.

> is all wiki pages there are. that's autogenerated and like typical wiki, we
> have not had anyone really looking the big picture but everyone have scratched
> something where finds a suitable place and thus there is a lot of repeating,
> empty pages and outdated information as code has moved faster than docs.
>
> Short answer to your questions is:
>
> current opensync might work as 0.2x what you probably find from your distro.

How do I test that? I have here a phone, a usb cable, a bluetooth
connection, and a laptop computer. What should I do first? Second?

> if it doesn't, you need some hacking skills to install the current svn version
> which works better, but still has some annoying bugs. You might want to wait
> few weeks it to get better. See the roadmap for open tickets.
>

I am willing to test SVN. I can backup both the phone and the laptop.
How to build?

>> I thank you in advance and apologize for the provocative nature of
>> this post, but there is no better way to word it.
>
> Well, you're not the first one. This is one of the most annoying missing
> feature on opensource desktop. I was one of you, swearing it after wasting
> countless hours trying to make it work.
>

I do contribute docs to some small opensource programs that I use (Zim
wiki, for example). However you do not want _me_ to write the docs for
opensync! If I do manage to get my E71 and KDE-PIM syncing, however, I
promise to document and publish the method.

> I cannot code good c-code. But still, I came to irc channel, tried to help
> everywhere I can and belive me, there is more things to do than I've time.
> We welcome you to join to help us (which you already did by giving feedback
> about web/docs).
>

Nor can I code in C. I will join the IRC channel when I have some
time. Is there a preferable weekday / hour when knowledgable people
are on IRC?

Thanks!

-- 
Dotan Cohen

http://what-is-what.com
http://gibberish.co.il
א-ב-ג-ד-ה-ו-ז-ח-ט-י-ך-כ-ל-ם-מ-ן-נ-ס-ע-ף-פ-ץ-צ-ק-ר-ש-ת

ä-ö-ü-ß-Ä-Ö-Ü

Re: [Opensync-users] Where to start?

[Juha T. <Juh...@ik...>]

On Wednesday 19 November 2008 17:34:48 Dotan Cohen wrote:
> I need to sync my KDE-PIM calendar with either my Nokia E71 or my
> Nokia 6288. 

I've E71 too here. And i use KDE.

> Opensync 0.22 is already installed on my Kubuntu 8.04 (KDE 
> 3.5.10) machine. 

Good news: 0.2x versions have kdepim plugin
Bad news: 0.2x does not really work, that's why the big changes started for 0.40.

> I go to opensync.org and try these links: 
> Help / Guide
> Wiki
> Documentation for 0 - 0.2x
> 
> "Help/Guide" is the Trac help system- no good for me. "Wiki" takes me
> back to the homepage. 

Yep, one of the few reasons I'm against this whole web wikialization. 
If you were a bricklayer and left from finished work, your tools would
be partly visible between the bricks you laid. Or if you were an electrician,
your meters would be part of the house electric circuits. Or for book writer,
you would find the instructions from book margins how to change the 
color cartridge for the typewriter. Wiki tries to solve a content problem by
changing the tools and way to access the content. You just have been confused
by the above.

> "Documentation for 0 - 0.2x" has these relevant 
> links:
> DeviceCompatibilityList
> Examples
> FAQ
> 
> "DeviceCompatibilityList" makes me confidant that the E71 is
> supported. All the links on the"Examples" return 404 errors. "FAQ" has
> a question 'How do I get started?' but the answer is literally to
> install then 'start tinkering'.

What we have, is a problem in docs that that was not versioned at all,
which started to be a problem when we had 0.3x development versions that
were not compatible with the docs anymore. Some people started to mix docs
but imo it's better to have releases that will also appear in documentation
space. So, I splitted the docs last weekend to

 http://www.opensync.org/wiki/docs

and unfortunately you cought me in middle of indexing them. Another problem 
is that i found out that we have other kind of stuff that needs versioning too
but is not part of docs, so the whole hierarchy is screwed and I need to re-do it.

Part of my last week meeting's action points were to make some 
kind of guidelines for wiki and it's due tomorrow so this will 
get better today evening.

> So I then turned to Google and searched on the keywords "kde,
> opensync, nokia". I did not get very far. Where to go from here? This
> is not a troll but a real question: Is opensync meant to be used by
> regular joes like me (mechanical engineers, not computer programmers)?

Yes it is. Part of the goals for 0.40 release were to make it way much
easier in many ways and it has already achived quite a few of them. One
is to make configuration easier. We're already working with the installation
docs. Once we get the 0.40 release out, all distros will pick it and you don't
have to worry about the installation, which is somewhat laborious at the
moment.

> If so, where is the documentation?

  http://www.opensync.org/wiki/TitleIndex

is all wiki pages there are. that's autogenerated and like typical wiki, we
have not had anyone really looking the big picture but everyone have scratched
something where finds a suitable place and thus there is a lot of repeating,
empty pages and outdated information as code has moved faster than docs.

Short answer to your questions is: 

current opensync might work as 0.2x what you probably find from your distro.
if it doesn't, you need some hacking skills to install the current svn version
which works better, but still has some annoying bugs. You might want to wait
few weeks it to get better. See the roadmap for open tickets.

> I thank you in advance and apologize for the provocative nature of
> this post, but there is no better way to word it.
 
Well, you're not the first one. This is one of the most annoying missing
feature on opensource desktop. I was one of you, swearing it after wasting
countless hours trying to make it work. 

I cannot code good c-code. But still, I came to irc channel, tried to help 
everywhere I can and belive me, there is more things to do than I've time. 
We welcome you to join to help us (which you already did by giving feedback 
about web/docs).


Tuju

-- 
Varo hattupäisiä autoilijoita.

[Opensync-users] Where to start?

[Dotan C. <dot...@gm...>]

I need to sync my KDE-PIM calendar with either my Nokia E71 or my
Nokia 6288. Opensync 0.22 is already installed on my Kubuntu 8.04 (KDE
3.5.10) machine. I go to opensync.org and try these links:
Help / Guide
Wiki
Documentation for 0 - 0.2x

"Help/Guide" is the Trac help system- no good for me. "Wiki" takes me
back to the homepage. "Documentation for 0 - 0.2x" has these relevant
links:
DeviceCompatibilityList
Examples
FAQ

"DeviceCompatibilityList" makes me confidant that the E71 is
supported. All the links on the"Examples" return 404 errors. "FAQ" has
a question 'How do I get started?' but the answer is literally to
install then 'start tinkering'.

So I then turned to Google and searched on the keywords "kde,
opensync, nokia". I did not get very far. Where to go from here? This
is not a troll but a real question: Is opensync meant to be used by
regular joes like me (mechanical engineers, not computer programmers)?
If so, where is the documentation?

I thank you in advance and apologize for the provocative nature of
this post, but there is no better way to word it.

-- 
Dotan Cohen

http://what-is-what.com
http://gibberish.co.il
א-ב-ג-ד-ה-ו-ז-ח-ט-י-ך-כ-ל-ם-מ-ן-נ-ס-ע-ף-פ-ץ-צ-ק-ר-ש-ת

ä-ö-ü-ß-Ä-Ö-Ü

[Opensync-users] Opie-sync discover

[Erik-Jan E. <e.e...@pl...>]

Tried opie-sync. 

1. Gives error message at discover:

~$ msynctool --discover evo-opie 2ERROR: Couldn't find Object Type
"contact".
EXIT_ERROR: opie_sync_initialize: Couldn't find Object Type "contact".
EXIT_ERROR: _osync_client_handle_initialize: Couldn't find Object Type
"contact".
EXIT_ERROR: _osync_client_message_handler: Couldn't find Object Type
"contact".
ERROR: Couldn't find Object Type "contact".
EXIT_ERROR: _osync_engine_initialize_member: Couldn't find Object Type
"contact".
EXIT_ERROR: osync_engine_discover: Couldn't find Object Type "contact".
EXIT_ERROR: osync_engine_discover_and_block: Couldn't find Object Type
"contact".
EXIT_ERROR: osync_engine_finalize: Couldn't find Object Type "contact".
EXIT_ERROR: msync_configure_discover: Couldn't find Object Type "contact".
ERROR: Couldn't find Object Type "contact".

Must have something to do with the new Opensync API. Can someone help me
out?

Thanks in advance
-- 
View this message in context: http://www.nabble.com/Opie-sync-discover-tp20480833p20480833.html
Sent from the Opensync - User mailing list archive at Nabble.com.

Re: [Opensync-users] Syncing one-way from KDE-PIM to Nokia E71

[Dotan C. <dot...@gm...>]

2008/11/12 Juha Tuomala <Juh...@ik...>:
> On Wednesday 12 November 2008 09:54:18 Dotan Cohen wrote:
>> Can OpenSync be used to sync one way from KDE-PIM to a Nokia E71?
>
> One-way, I doubt that not yet.
>

I _could_ live with two-way sync. That is not a shopstopper.

>> If so, is KDE-PIM with Akonadi supported, or only the KDE-PIM 3.x
>> version?
>
> akonadi and kde old resources should also be supported.
>

In that case I will look into KDE-PIM in KDE 4.1 and see if it is in a
usable state (it was not the last time I tried).

>> I have gone through the OpenSync.org wiki and I do see that
>> my phone is supported by version OpenSync 0.22
>
> In theory 0.22 supports syncml 1.1 like does the phone too.
> Though those 0.22 and older versions of libsyncml are buggy
> and you're better off by testing the trunk, as it will also
> help polishing the next stable version.
>

Is 0.38 considered reliable for everyday use? I understand that 0.22
was buggy but I prefer buggy to dataloss. The wiki states that the
0.3x branch is for developers, which I am not.

>> however I cannot find
>> information on KDE-PIM with or without Akonadi and I have been
>> unsuccessful at syncing via Kitchensync.
>
> You can already use KDE+Opensync trunk by defining kaddressbook
> and korganizer a Directory resource. Make a dir (like i did
> $HOME/.pim/contacts and $HOME/.pim/calendar) and assign those
> paths to new resources.
>
> Then configure the opensync group so that the file-sync plugin
> dir with correct object type points to that directory:
>
> [tuju@wasa]~/.opensync/group1/1% cat file-sync.conf
> <?xml version="1.0"?>
> <config version="1.0">
>  <Resources>
>    <Resource>
>      <Enabled>1</Enabled>
>      <Formats>
>        <Format>
>          <Name>file</Name>
>        </Format>
>      </Formats>
>      <ObjType>contact</ObjType>
>      <Path>/var/tuju/pim/contacts</Path>
>    </Resource>
>  </Resources>
> </config>
>
>

Sounds possible, but expect to see my whimpering with my tail between
my legs when I get stuck. I'm an engineer, not a software developer!

> Well, I had to move it under /var temporarily to see if
> my NFS $HOME is causing trouble, but it was not.
>
> I also have E71 and it syncs successfully with the current
> trunk - as long as it falls to slow-sync and I encounter
> these problems:
>
>  http://opensync.org/ticket/882
>  http://opensync.org/ticket/883
>

Those do not seem to be showstoppers, either.

> I think those are being worked on already so it would be
> good if you could join to the KDE+Trunk+E71 testers so that
> we can cross-confirm the problems we may still encounter
> later on.
>

I would like to help test trunk, but the last time that I tried to
install it was a two-day affair and did not end in success.

> I've installed Opensync to Fedora 9 with RPMS, you did not
> mention your distro but I think it would be good if we can
> get pkg repos running for few distros and focus on actual
> testing and not the installation which *is* laborious to do
> manually.
>

Currently I am using Kubuntu as Fedora >=6 would not install on my
Dell Inspiron. I do _not_ like OpenSuse (too many KDE mods), though if
it makes like easier I would have no problem giving Mandriva a whirl.

-- 
Dotan Cohen

http://what-is-what.com
http://gibberish.co.il
א-ב-ג-ד-ה-ו-ז-ח-ט-י-ך-כ-ל-ם-מ-ן-נ-ס-ע-ף-פ-ץ-צ-ק-ר-ש-ת

ä-ö-ü-ß-Ä-Ö-Ü

Re: [Opensync-users] Syncing one-way from KDE-PIM to Nokia E71

[Juha T. <Juh...@ik...>]

On Wednesday 12 November 2008 09:54:18 Dotan Cohen wrote:
> Can OpenSync be used to sync one way from KDE-PIM to a Nokia E71?

One-way, I doubt that not yet.

> If so, is KDE-PIM with Akonadi supported, or only the KDE-PIM 3.x
> version? 

akonadi and kde old resources should also be supported.

> I have gone through the OpenSync.org wiki and I do see that 
> my phone is supported by version OpenSync 0.22 

In theory 0.22 supports syncml 1.1 like does the phone too.
Though those 0.22 and older versions of libsyncml are buggy
and you're better off by testing the trunk, as it will also
help polishing the next stable version.


> however I cannot find 
> information on KDE-PIM with or without Akonadi and I have been
> unsuccessful at syncing via Kitchensync.

You can already use KDE+Opensync trunk by defining kaddressbook
and korganizer a Directory resource. Make a dir (like i did 
$HOME/.pim/contacts and $HOME/.pim/calendar) and assign those
paths to new resources.

Then configure the opensync group so that the file-sync plugin
dir with correct object type points to that directory:

[tuju@wasa]~/.opensync/group1/1% cat file-sync.conf
<?xml version="1.0"?>
<config version="1.0">
  <Resources>
    <Resource>
      <Enabled>1</Enabled>
      <Formats>
        <Format>
          <Name>file</Name>
        </Format>
      </Formats>
      <ObjType>contact</ObjType>
      <Path>/var/tuju/pim/contacts</Path>
    </Resource>
  </Resources>
</config>


Well, I had to move it under /var temporarily to see if
my NFS $HOME is causing trouble, but it was not.

I also have E71 and it syncs successfully with the current
trunk - as long as it falls to slow-sync and I encounter 
these problems:

  http://opensync.org/ticket/882
  http://opensync.org/ticket/883


I think those are being worked on already so it would be 
good if you could join to the KDE+Trunk+E71 testers so that
we can cross-confirm the problems we may still encounter
later on.

I've installed Opensync to Fedora 9 with RPMS, you did not
mention your distro but I think it would be good if we can
get pkg repos running for few distros and focus on actual 
testing and not the installation which *is* laborious to do
manually.

Br,

Tuju


-- 
Varo hattupäisiä autoilijoita.

[Opensync-users] SetupGuide outdated, or 0.22 outdated?

[Dotan C. <dot...@gm...>]

I am trying to configure OpenSync via the SetupGuide on the wiki:
http://www.opensync.org/wiki/SetupGuide

However, I have a slightly different XML format than what is presented
on the wiki page. The wiki page shows this format:
<?xml version="1.0"?>
<config>
  <directory>
     <path></path>
    <objtype>data</objtype>
  </directory>

  [...]
</config>


However, this is what I have:
<?xml version="1.0"?>
<config>
  <!-- directory path for file-sync -->
  <path>/home/hardy2/sync1</path>

  <!-- should care of subdirectories (TRUE or FALSE) -->
  <recursive>FALSE</recursive>
</config>


For me, "path" is not in a "directory" tag, and there is no "objtype".
Should I simply add these? Will that cause unexpected results? Should
I update to OpenSync 0.38?

-- 
Dotan Cohen

http://what-is-what.com
http://gibberish.co.il
א-ב-ג-ד-ה-ו-ז-ח-ט-י-ך-כ-ל-ם-מ-ן-נ-ס-ע-ף-פ-ץ-צ-ק-ר-ש-ת

ä-ö-ü-ß-Ä-Ö-Ü

[Opensync-users] Syncing one-way from KDE-PIM to Nokia E71

[Dotan C. <dot...@gm...>]

Can OpenSync be used to sync one way from KDE-PIM to a Nokia E71? If
so, is KDE-PIM with Akonadi supported, or only the KDE-PIM 3.x
version? I have gone through the OpenSync.org wiki and I do see that
my phone is supported by version OpenSync 0.22 however I cannot find
information on KDE-PIM with or without Akonadi and I have been
unsuccessful at syncing via Kitchensync.

Thanks in advance.

-- 
Dotan Cohen

http://what-is-what.com
http://gibberish.co.il
א-ב-ג-ד-ה-ו-ז-ח-ט-י-ך-כ-ל-ם-מ-ן-נ-ס-ע-ף-פ-ץ-צ-ק-ר-ש-ת

ä-ö-ü-ß-Ä-Ö-Ü

[Opensync-users] OpenSync Release 0.38

[Bjoern R. <b....@fh...>]

Hi everyone,

we finally released OpenSync 0.38. To keep more people up-to-date we are 
planning to arrange IRC meetings every Thursday. You can find the 
details in the release notes.

Release Notes:

Yet another E.X.P.E.R.I.M.E.N.T.A.L. release of OpenSync. This release 
is intended for developers, testers and for packages. OpenSync 0.3x 
releases aren't intended to be stable. We don't recommend this release 
for productive use. We don't recommend this release to be packaged as 
part of a distribution.

--- end of sad/scary disclamer ---

Late but no too late. We are behind our roadmap again, but the next 
stable version 0.40  is getting much closer.

Changes since last release:
   
    - Many updates and fixes for the OSyncPluginConfig API
        - Introduced osync_plugin_advancedoption_get_minsize .. to set 
minsize and avoid min values e.g. 0
        - Added MinSize in plugin_config schema for AdvancedOption
        - Introduced osync_plugin_connection_set_type()
        - Introduce initial interface of OSyncPluginConfig "supported" 
flags. Details:
            - Purpose of those supported flags are to give the 
Frontend/UIs information which option are supported by the plugin and 
should be disabled.
            This allows to generate "smart" UIs which only show 
option/fields which are really supported by the plugin at all.
            For OSyncPluginConnection there are two supported status flags:
            1. ConnectionFlags - e.g. USB, Bluetooth, ... to generate 
bitmask of multiple supported connection types/transports.
            2. ConnectionOptionFlags - e.g. RFCommChannel, Port, URL, ...
        - Added a Preferred element to the Formats. Details: r3659
    - Updated example-plugin for current api
    - Reenabled plain to xmlformat-*-doc conversion
    - Made osync_assert public. Now plugin developers are able to use 
osync_assert instead of g_assert or assert.
    - Packaging with CPack
    - OpenSync raises an error message if a plugin cannot be loaded
    - Added sanity check for file-sync. file-sync only supports "file" 
format, which encapsulates the other formats.
    - Improved sorting of OSyncXMLFormat fields ( introduced 
osync_xmlformat_is_sorted(), ...)
    - Only active OSyncObjTypeSinks for Enbaled/Activated Resources: 
Ticket #817
    - Introduced Coverter Cache to cache already encountered format 
converter paths. This should accelerate the conversion.
    - Syncml-plugin ported to OSyncPluginConfig
    - Syncml migrated to new high level API of libsyncml (thanks a lot 
to Micheal Bell for his great work on syncml)
    - New initialize and finalize functions for format plugins to store 
format plugin related data, e.g. XML schemas.
    - Plugins which are migrated to 0.38:
        - file-sync
        - syncml (requires libsyncml 0.5.0)
        - google-calendar (beta)
        - tomboy-sync (beta)
        - opie-sync (?)

Project IRC Meetings
        - Start of regular IRC Meetings
        - every Thursday
        - even Calendar Weeks: 09:00 UTC
        - odd Calendar Weeks: 14:00 UTC
        - Duration: 1hour
        - Minutes get sent to opensync-devel@ mailing list (latest after 
24h)
        - First meeting: 2008-11-13T09:00:00Z
        - Next minutes: dgollub
        - Channel: #opensync

Next steps:
    - Bugfixing
        - OpenSync core
        - vformat plugin
    - Finalize the limited API
    - Schema freezes
    - Finishing !OpenSync Whitepaper
    - Generic XSLT format plugin
    - Porting other plugins to latest changes for 0.3X
    - Fixing python wrapper
        - We still need a python developer, who can fix it. If any 
volunteer read this. please send a mail to the mailing list!

Release tarballs:
http://opensync.org/download/releases/0.38/

Thanks to everyone for actively contributing to the OpenSync project by 
testing, writing code, updating tickets (special thanks to Felix 
Moeller) and keeping the project alive!

-- 
/Bjoern Ricks

Re: [Opensync-users] SyncML plugin (SVN trunk): Schemas validity error

[Mathew C. <ko...@gm...>]

stavallo wrote:
> [snip]
> stefano@trouville:/usr/local/src/opensync/src$ msynctool --configure test 1
> /usr/local/src/opensync/share/libopensync1/defaults/syncml-http-client:177: element Name: Schemas validity error : Element 'Name': This element is not expected. Expected is ( Enabled ).
> /usr/local/src/opensync/share/libopensync1/defaults/syncml-http-client:187: element Name: Schemas validity error : Element 'Name': This element is not expected. Expected is ( Enabled ).
> /usr/local/src/opensync/share/libopensync1/defaults/syncml-http-client:197: element Name: Schemas validity error : Element 'Name': This element is not expected. Expected is ( Enabled ).
> ERROR: Plugin configuration file is not valid! /usr/local/src/opensync/share/libopensync1/schemas/plugin_config.xsd
> EXIT_ERROR: osync_plugin_config_file_load: Plugin configuration file is not valid! /usr/local/src/opensync/share/libopensync1/schemas/plugin_config.xsd
> EXIT_ERROR: osync_member_get_config_or_default: Plugin configuration file is not valid! /usr/local/src/opensync/share/libopensync1/schemas/plugin_config.xsd
> EXIT_ERROR: msync_configure_member: Plugin configuration file is not valid! /usr/local/src/opensync/share/libopensync1/schemas/plugin_config.xsd
> ERROR: Plugin configuration file is not valid! /usr/local/src/opensync/share/libopensync1/schemas/plugin_config.xsd

I'm having a similar problem following the procedure in the
devel-branch-0.3 [1] page, under the "Simple file-to-file
syncing" example.

  msynctool --addgroup file2file
  msynctool --addmember file2file file-sync
  msynctool --addmember file2file file-sync
  msynctool --configure file2file 1

I tried using the XML from the wiki page added to or replacing the
default XML that comes up from the --configure. Either way gives a
similar error. I would be happy to fix the wiki page if someone can
point me in the right direction. I'm guessing the default scheme has
changed since this page was written. The exact error is:

  |=|=mat==- msynctool --configure file2file 1
  /tmp/msynctooltmp-XXXXXX:1: element directory: Schemas validity
error : Element 'directory': This element is not expected. Expected is
one of ( AdvancedOptions, Authentication, Connection, Localization,
Resources ).
  ERROR: Plugin configuration file is not valid!
/home/mat/nsrc/all_opensync/root/share/libopensync1/schemas/plugin_config.xsd
  EXIT_ERROR: osync_plugin_config_file_load: Plugin configuration file
is not valid! /home/mat/nsrc/all_opensync/root/share/libopensync1/schemas/plugin_config.xsd
  EXIT_ERROR: edit_config: Plugin configuration file is not valid!
/home/mat/nsrc/all_opensync/root/share/libopensync1/schemas/plugin_config.xsd
  EXIT_ERROR: msync_configure_member: Plugin configuration file is not
valid! /home/mat/nsrc/all_opensync/root/share/libopensync1/schemas/plugin_config.xsd
  ERROR: Plugin configuration file is not valid!
/home/mat/nsrc/all_opensync/root/share/libopensync1/schemas/plugin_config.xsd

[1] - http://www.opensync.org/wiki/devel-branch-0.30

[Opensync-users] SyncML plugin (SVN trunk): Schemas validity error

[Stefano A. <sta...@un...>]

Hi all,

I successfully built opensync, msynctool, file-sync, vformat, libsyncml,
syncml from SVN trunk (revision 3710). Indeed,

stefano@trouville:/usr/local/src/opensync$ msynctool --listplugins
Available plugins:
file-sync
syncml-http-server
syncml-http-client
syncml-obex-client

Then, I created a group and added two members, syncml-http-client and
file-sync. However, I get:

stefano@trouville:/usr/local/src/opensync/src$ msynctool --configure test 1
/usr/local/src/opensync/share/libopensync1/defaults/syncml-http-client:177:
element Name: Schemas validity error : Element 'Name': This element is not
expected. Expected is ( Enabled ).
/usr/local/src/opensync/share/libopensync1/defaults/syncml-http-client:187:
element Name: Schemas validity error : Element 'Name': This element is not
expected. Expected is ( Enabled ).
/usr/local/src/opensync/share/libopensync1/defaults/syncml-http-client:197:
element Name: Schemas validity error : Element 'Name': This element is not
expected. Expected is ( Enabled ).
ERROR: Plugin configuration file is not valid!
/usr/local/src/opensync/share/libopensync1/schemas/plugin_config.xsd
EXIT_ERROR: osync_plugin_config_file_load: Plugin configuration file is not
valid! /usr/local/src/opensync/share/libopensync1/schemas/plugin_config.xsd
EXIT_ERROR: osync_member_get_config_or_default: Plugin configuration file is
not valid!
/usr/local/src/opensync/share/libopensync1/schemas/plugin_config.xsd
EXIT_ERROR: msync_configure_member: Plugin configuration file is not valid!
/usr/local/src/opensync/share/libopensync1/schemas/plugin_config.xsd
ERROR: Plugin configuration file is not valid!
/usr/local/src/opensync/share/libopensync1/schemas/plugin_config.xsd

Any hint how to solve this problem?

Many thanks,
Stefano

[Opensync-users] is smlDataSyncRun synchronous

[Michael B. <mic...@cm...>]

Hi,

I send the answer to a user question on IRC after the user disconnected
and I killed the direct chat room. So atom_, here is your answer and
sorry for the abort.

BTW direct question means you should prefix your question/message with
bellmich: on IRC so that it is highlighted for me.

(06:21:16 PM) atom_: is smlDataSyncRun() synchronous?
(06:21:26 PM) azeem: there's absolutely no problem with asking questions
(06:21:50 PM) azeem: better address bellmich directly, I doubt anybody
else knows off-hand
(06:22:00 PM) atom_: ok
(06:32:10 PM) atom_ left the room (quit: "http://www.mibbit.com ajax IRC
Client").
(06:33:11 PM) bellmich: atom_: No.
(06:38:39 PM) azeem: that was only 4 minutes!
(06:38:46 PM) bellmich: The syncml-ds-tool main function is a bit tricky
here.
(06:39:10 PM) bellmich: The first mutex lock really locks the mutex
after smlDataSyncRun.
(06:39:24 PM) bellmich: The second call blocks until the mutex is unlocked.
(06:39:32 PM) bellmich: Where is the mutex lock unlocked?
(06:40:03 PM) bellmich: It is unlocked in the event callback
recvEventCallback.
(06:40:36 PM) bellmich: The unlock happens if the event
SML_DATA_SYNC_EVENT_FINISHED is received.
(06:40:56 PM) bellmich: I use the mutex lock to block the main function.
(06:41:30 PM) bellmich: The complete stuff is asynchron but main is
synchron. So I must block the main function until the synchronization is
over.
-- 
_______________________________________________________________

Michael Bell                    Humboldt-Universitaet zu Berlin

Tel.: +49 (0)30-2093 2482       ZE Computer- und Medienservice
Fax:  +49 (0)30-2093 2704       Unter den Linden 6
mic...@cm...   D-10099 Berlin
_______________________________________________________________

X.509 CA Certificates / Wurzelzertifikate

https://pki.pca.dfn.de/hu-berlin-ca/cgi-bin/pub/pki?cmd=getStaticPage;name=index;id=2&RA_ID=0

Re: [Opensync-users] Porting the examples to 0.3x

[Erik-Jan E. <e.e...@pl...>]

Hi,
The whitepaper 
http://cryptomilch.de/~dgollub/OpenSync/OpenSync-0.40-DRAFT-20080118.pdf
http://cryptomilch.de/~dgollub/OpenSync/OpenSync-0.40-DRAFT-20080118.pdf ,
msynctool.c, and vconvert.c are very useful. It's quite straight forward to
make the other examples.

Still, one more question.


Bjoern Ricks wrote:
> 
> Hi,
>> 2. Is there a list of translations of the OpensSync internals?  I mean 
>> a list  in which I can find the internals of 0.22 and see what they 
>> have to be in the new architecture. The page 
>> http://www.opensync.org/wiki/PluginPortingGuide-0.30 gives some 
>> information, but not enough.
> I don't think so. Because both pages itself are outdated. E.g. we 
> changed the way to get the configuration of a plugin. We introduced in 
> 0.37 a new api which is common and usable for all sync plugins. It is 
> hard to understand how to use the api of opensync but if you want to get 
> familiar with the code take a look at file-sync or start to write a 
> plugin (sync or format) or try some code from msynctool. In my opinion 
> that's the best way to get into opensync. By the way I started with 
> opensync not even a year ago.
> 

Also found  http://www.opensync.org/docs/index.html doxygen output . Why is
the opensync_engine not in the list of modules? How can I get the module in
the list? Just running doxygen over the source code doesn't do the trick. 


Bjoern Ricks wrote:
> 
> But in excuse of the delay of the development and unfinished/outdated 
> documentation all few opensync developers work on opensync in their rare 
> free time. There is no developer who is working full time on opensync.
> 

It is in no way my intention to offend or criticize the developers.  I have
to respect mailing list etiquette, so I can't say the do a great job, but
they do!

Erik-Jan Elfferich

-- 
View this message in context: http://www.nabble.com/Porting-the-examples-to-0.3x-tp20189344p20224130.html
Sent from the Opensync - User mailing list archive at Nabble.com.

Re: [Opensync-users] nokia e50, opensync 0.22 synchronisation hang

[Łukasz N. <lk...@ni...>]

Hello,

On Mon, 2008-10-27 at 11:28 +0100, Bjoern Ricks wrote:
> Sorry, but Opensync 0.22 has a lot of bugs and because we are only a few 
> developers we can't support the old version any longer. Maybe you
> can try a newer version of the development branch 
> http://www.opensync.org/wiki/devel-branch-0.30 .

I've used opensync 0.37, built from source:

libopensync-0.37
libopensync-plugin-file-0.37
libopensync-plugin-syncml-0.37
libopensync-plugin-vformat-0.37
libsyncml-0.4.7
msynctool-0.37

Right now I have attached output message. My configuration and
OSYNC_TRACE with OSYCN_PRIVACY attached.

On my phone there is "Synchronisation finished" message only.

Directory /home/shufla/msync/ exists, and it is empty.

Do I have something wrong in my configuration?

Regards,
Luke

PS. Trace output is here: http://lnowak.com/msynctrace-20081028.tar.gz

-- 
Łukasz Nowak IT Specialist
Skype: Shufla lk...@ni... jid: sh...@ja...
``Use the Source, Luke...''

[Opensync-users] libsyncml 0.5.0

[Michael B. <mic...@cm...>]

libsyncml 0.5.0 release notes

Download: http://libsyncml.opensync.org/download/releases/0.5.0/

Major Changes
=============

* introduction of a new high level data synchronization API
* replaced syncml-obex-client with syncml-ds-tool which supports all
  transports and synchronization modes
* introduction of mobile specific test on base of WBXML
* tests are only executed if the necessary environment is available
  (a failed test always means that there is a problem)

Minor Changes
=============

* introduced BLUETOOTH_ADDRESS and BLUETOOTH_CHANNEL configuration
  parameters because URL and PORT always cause confusion
* introduced defines for all configuration options to detect typos at
  compile time
* OMA DS server now supports full standard compliant authentication
* OMA DS server can now be used without authentication
* more generic OBEX server code (Bluetooth and IRDA are supported now)
* username and password was centralized and so authentication for
  OMA DS clients over OBEX server transport is available
* new cmake option ENABLE_OPENOBEX_TCP
* new cmake option BUILD_DOCUMENTATION
* new cmake option RELEASE_CANDIDATE
* http server supports ResponseURI for more security
* CPack support was added
* library version numbers are now in the correct order
  (Please note that no libraries with wrong SO versions were released.)

Internal Changes
================

* license migrated from "LGPL 2.1" to "LGPL 2.1 or higher"
* added several missing header file inclusions
* fixed state management in smlTransportStop and smlTransportFinalize
* smlTransportRunAsync was integarted into smlTransportIntialize
* OMA DS server ignores now authentication status codes (SECURITY)
* cleaned up the build environment
* never use one port for more than one test case
* Size changed to MaxSize in OMA DS 1.2 DevInf (requires up-to-date
  libwbxml)
* fixes for libsoup 2.4 and the according cmake module
* introduced sml_fail_unless as replacement for fail_unless
* x86_64 compiles without warnings

Special thanks goes to the authors of cmake/ctest and of course the
owners of the build hosts whom support us with a lot of valuable
feedback: Bjoern, Christian and Daniel.

Best regards

Michael

Re: [Opensync-users] Porting the examples to 0.3x

[Bjoern R. <b....@fh...>]

Hi,
> Hi,
>
> In my search to understand OpenSync 0.3 internals I ported the first 
> example of the page http://www.opensync.org/wiki/Examples. Attached 
> source: test.c. Don't know if it is really correct, but it produces a 
> output that seems fairly right.
Your code seems to be right. If you need more examples please look at 
the source of msynctool.
>
> I have two and a half questions:
> 1. Does the OSyncPluginEnv not to be initialized anymore?
No. Only call osync_plugin_env_new and afterwards osync_plugin_env_load. 
If you want to load the sync plugins from a different directory pass a 
path to to osync_plugin_env_load. Instead if you want to use the default 
dir pass NULL as second parameter. (In your file you used a variable 
plugindir which was initialized with NULL ;-) )
> 2. Is there a list of translations of the OpensSync internals?  I mean 
> a list  in which I can find the internals of 0.22 and see what they 
> have to be in the new architecture. The page 
> http://www.opensync.org/wiki/PluginPortingGuide-0.30 gives some 
> information, but not enough.
I don't think so. Because both pages itself are outdated. E.g. we 
changed the way to get the configuration of a plugin. We introduced in 
0.37 a new api which is common and usable for all sync plugins. It is 
hard to understand how to use the api of opensync but if you want to get 
familiar with the code take a look at file-sync or start to write a 
plugin (sync or format) or try some code from msynctool. In my opinion 
that's the best way to get into opensync. By the way I started with 
opensync not even a year ago.
>
> 2.5 The white paper that i found included in the opensync source code 
> (opensync/docs/whitepaper) is not finished yet. Still it is very 
> useful to get the picture even in this stage. It took me some time to 
> get the .tex  in a .pdf. Is it possible to put a link to a PDF of the 
> latest version on the page 
> http://www.opensync.org/wiki/devel-branch-0.30.
Daniel (after asking him about some annoying internals ;-) ) advised me 
to this document. He has a pdf version on 
http://cryptomilch.de/~dgollub/OpenSync/OpenSync-0.40-DRAFT-20080118.pdf 
. It is planned to finish this document together with the 0.40 release. 
But in excuse of the delay of the development and unfinished/outdated 
documentation all few opensync developers work on opensync in their rare 
free time. There is no developer who is working full time on opensync.
>
> Thanks,
> Erik-Jan
>

-- 
/Bjoern Ricks

[Opensync-users] Porting the examples to 0.3x

[Erik-Jan E. <e.e...@pl...>]

Hi,

In my search to understand OpenSync 0.3 internals I ported the first 
example of the page http://www.opensync.org/wiki/Examples. Attached 
source: test.c. Don't know if it is really correct, but it produces a 
output that seems fairly right.

I have two and a half questions:
1. Does the OSyncPluginEnv not to be initialized anymore?
2. Is there a list of translations of the OpensSync internals?  I mean a 
list  in which I can find the internals of 0.22 and see what they have 
to be in the new architecture. The page 
http://www.opensync.org/wiki/PluginPortingGuide-0.30 gives some 
information, but not enough.

2.5 The white paper that i found included in the opensync source code 
(opensync/docs/whitepaper) is not finished yet. Still it is very useful 
to get the picture even in this stage. It took me some time to get the 
.tex  in a .pdf. Is it possible to put a link to a PDF of the latest 
version on the page http://www.opensync.org/wiki/devel-branch-0.30.

Thanks,
Erik-Jan

Re: [Opensync-users] nokia e50, opensync 0.22 synchronisation hang

[Bjoern R. <b....@fh...>]

Sorry, but Opensync 0.22 has a lot of bugs and because we are only a few 
developers we can't support the old version any longer. Maybe you
can try a newer version of the development branch 
http://www.opensync.org/wiki/devel-branch-0.30 .
> Hello,
>
> While running msynctool --sync nokia2f it stays forever on last line of
> nokia2f-syncprint.txt
>
> My cell prints "Synchronisation finished" and that's all (no errors).
>
> What is wrong? I read about problems with synchronising notes, but I'm
> starting with synchronising contacts only.
>
> Attached OSYNC_TRACE with OSYNC_PRIVACY.
>
> Used packages:
>
> libopensync0-0.22-9mdv2008.1
> libopensync-0.22-9mdv2008.1
> libopensync-plugin-evolution2-0.22-2mdv2008.1
> libopensync-plugin-file-0.22-2mdv2008.1
> libopensync-plugin-gnokii-0.22-1mdv2008.1
> libopensync-plugin-syncml-0.22-2mdv2008.1
> msynctool-0.22-7mdv2008.1
>
> Regards,
> Luke
>
>   
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Opensync-users mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-users

-- 
/Bjoern Ricks

[Opensync-users] nokia e50, opensync 0.22 synchronisation hang

[Łukasz N. <lk...@ni...>]

Hello,

While running msynctool --sync nokia2f it stays forever on last line of
nokia2f-syncprint.txt

My cell prints "Synchronisation finished" and that's all (no errors).

What is wrong? I read about problems with synchronising notes, but I'm
starting with synchronising contacts only.

Attached OSYNC_TRACE with OSYNC_PRIVACY.

Used packages:

libopensync0-0.22-9mdv2008.1
libopensync-0.22-9mdv2008.1
libopensync-plugin-evolution2-0.22-2mdv2008.1
libopensync-plugin-file-0.22-2mdv2008.1
libopensync-plugin-gnokii-0.22-1mdv2008.1
libopensync-plugin-syncml-0.22-2mdv2008.1
msynctool-0.22-7mdv2008.1

Regards,
Luke

-- 
Łukasz Nowak IT Specialist
Skype: Shufla lk...@ni... jid: sh...@ja...
``Use the Source, Luke...''