Re: [SyncEvolution] 1.1.99.5a in Debian experimental - testers wanted
by Ross Vandegrift
On Mon, 2011-07-25 at 07:37 +0200, Tino Keitel wrote:
> Thanks. This looks more evolution related than bluetooth related. Did you
> try other sync methods on that computer, like HTTP(S)? Did you explicitly
> set the calendar name in your syncevolution config? If not, did you set a
> default calendar in evolution?
On Mon, 2011-07-25 at 11:53 +0200, Patrick Ohly wrote:
> Which Evolution calendar is this?
>
> Run "syncevolution" (without parameters) and it'll tell you what it uses
> by default.
Aha - that's the key difference. My desktop default calendar is set to
a CalDAV calendar. My laptop is still set to the local copy.
I'm guessing (based on the thread about caldav/syncml) that issues here
are expected?
Ross
--
Ross Vandegrift
ross(a)kallisti.us
9 years, 5 months
[SyncEvolution] dbus-server-reorganization progress
by Chris Kühl
Hi,
I've been working on getting my dbus-server-reorganization branch on
par with master and I think I've almost achieved that. Currently they
are both seeing 3 failures and 2 errors. I see that the 2 errors are
probably addressed in bug #20990 as they start to appear only after
the recent autosync changes. The 3 failures seem to be due to issues
with the password property in temporary configs. I've pastebin'ed my
output in case it's helpful: http://pastebin.com/kRe0sPBK
I said "almost" on par because I've been having issues when building
with --disable-shared and --enable-static. When trying this I get an
error telling me to add -ldl to the LDFLAGS which I've done and it
does in fact seem to build correctly. However, with this, the backends
don't get registered and I, of course, get tons of problems when
running the tests. This issue exists in the first commit on my branch
which moved the dbus-server over to its own directory. However,
everything does seem to build and work fine with only --enable-static
specified which is what I've been using for running the tests.
Cheers,
Chris
9 years, 5 months
[SyncEvolution] SyncEvolution on Harmattan
by Roman Morawek
Hello,
I have been using SyncEvolution intensively on a Maemo N900.
Right now I have a Nokia N950 with MeeGo Harmattan and the wish to
continue using SyncEvolution with my private Funambol server.
I spent some time on searching for ways to achieve this but did not succeed.
This is my understanding:
SyncEvolution supports MeeGo and is preinstalled on the Netbook images
but seems to be not available on Harmattan?
Are there plans to support Harmattan?
Or is it just a matter of proper installation or compiling the package?
Thanks a lot for your support,
Roman
9 years, 5 months
Re: [SyncEvolution] SyncEvolution on Harmattan
by Roman Morawek
>>> Although, like I said, I have no device to test on, I could probably try
>>> to compile it on the Harmattan SDK if you like. If it's like the
>>> Fremantle SDK, then it should have an emulator, at least.
>>
>> Of course, I'd appreciate this!
>
> Well, I've installed what I found on harmattan-dev.nokia.com, which was
> scratchbox, it seems.
>
> It looks like I can't compile SyncEvolution on this yet, because there's
> some build dependencies missing, Boost in particular. If you know of a
> libboost package for Harmattan, let me know. (There's also no libneon,
> but that's only needed for CardDAV/CalDAV, and I think you were only
> interested in SyncML.)
>
> And the simulator seems to have no contacts or calendar application, so
> even if I could build the SyncEvolution package, I would not be able to
> check how well it would work and interoperate with the native PIM
> applications. So I'd also need someone with a device to test some stuff
> for me, in order to know what options and patches to use when building
> Harmattan packages. (Things to figure out might include: Where are SSL
> CA certificates stored on Harmattan? Does mkcal support ical UIDs and
> stuff properly? Is optification still useful on Harmattan? Is IPv6
> supported on Harmattan?)
Ove, thanks for your efforts!
I'm looking forward for you to get an N9 and try again then. Hopefully
also the build dependencies are ported until then.
Regards,
Roman
9 years, 5 months
[SyncEvolution] 1.1.99.5a in Debian experimental - testers wanted
by Tino Keitel
Hi,
syncevolution 1.1.99.5a is now in Debian experimental. If there are
Debian users who want to test these packages, I'd be glad to hear
some feedback. Bluetooth and CalDAV/CardDAV are untested so far, so I'd
be really excited if someone can give this a shot and report back.
Regards,
Tino
9 years, 5 months
Re: [SyncEvolution] More syncevolution issues
by Patrick Ohly
On Sun, 2011-06-26 at 04:26 +0200, Ove Kåven wrote:
> OK, first, I've noticed the http://syncevolution.org/about page where
> somehow the Maemo backend is listed with "unknown". I could perhaps clarify:
>
> Maemo 5 Calendar Backend
> Data types: events, tasks, memos
> Storage: calendar-backend internal storage (SQLite)
> Change tracking: modification time
>
> (The calendar-backend storage is not icalendar, there's just a class to
> convert from/to ical/vcal, and that converter implementation is not all
> that great.)
Thanks for the update, applied.
> So, anyway, I've built that syncevolution snapshot. I've noted that now,
> --disable-ssl-certificate-check doesn't do anything anymore.
True. It used to insert SSLVerifyServer=0 into the configuration
templates. When these templates were moved out of the source code (where
a simple ifdef was enough) into files (where a more complicated patching
during "make install" would be needed), I dropped support for the
configure option. I didn't know that the Maemo 5 port depends on it.
> Maybe I can
> find the correct Maemo certificate path and give its path to configure
> --with-ca-certificates,
That would be the better solution, if it solves the problem.
Alternatively you could add the SSLVerify=0 in your frontend when
creating configs.
> but it also seems to me that webdav/NeonCXX.cpp
> probably wouldn't honor those paths if I did.
ne_ssl_trust_default_ca() is called by SyncEvolution. If libeon itself
was compiled correctly, then it should find and use the default
certificates. Overriding the path is indeed not supported. Disabling SSL
verification is, so that would be the low road that you could take.
> But more serious, maybe, is a problem with WebDAV sync. I did an initial
> sync against google calendar, which downloaded a lot of events. Right
> after that, I tried a normal sync, and that failed.
> "updating item: real luid 1014.ics does not match old luid
> pnark49mmvqjnnfbr0btstlpp8(a)google.com.ics"
Can you send me the logs of downloading an event and updating it? Run
with loglevel=4 and send the "source-config" logs, those are the ones
showing the communication with the CalDAV server.
> Perhaps it is of relevance that calendar-backend claims the ical "UID"
> field for its own purposes. It is generated when a calendar entry is
> inserted. You can't override the UID without hacks (any existing UID in
> the ical text is ignored), and there probably wouldn't be much point in
> trying anyway, since it is just an integer in the SQLite database, not a
> text field.
That might indeed be a problem. It might be possible to fix it, I need
to look at the logs and think a bit about where the right UID can be
inserted again.
> All this doesn't seem to have been much of a problem with
> normal SyncML sync, though...?
SyncML doesn't care about the UID at all whereas in CalDAV, iCalendar
2.0 including the UID semantic (globally unique and preserved) is
mandatory. It would be SyncEvolution's job to fix that for local
backends which don't support it.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
9 years, 5 months
[SyncEvolution] website: Introductory text and front page
by Murray Cumming
The introductory text on the main page is a little verbose and tries to
cram too many good features in to a first impression.
I don't see how to change that page (or maybe I don't have the right
access), but I'd like to change it to this:
"
SyncEvolution synchronizes personal information management (PIM) data
via the SyncML protocol. It syncs contacts, appointments, tasks and
memos. It syncs to web services via HTTP or to SyncML-capable phones via
Bluetooth.
<a href="http://downloads.syncevolution.org/">Binaries</a> are available
for Linux desktops (using GNOME Evolution, or KDE's Akonadi), for MeeGo
or for Maemo 5 (Nokia N900).
"
I would also like to move the "Recent Blog Posts" and "About the web
site" blocks to the right, putting some secondary introductory text at
the left (moved from About), along with a screenshot.
The "Featured Posts" is just a verbose duplicate of "Recent Blog Posts".
The reader is drawn to those blocks of text, but that time-specific
information is not the most informative for new visitors.
--
murrayc(a)murrayc.com
www.murrayc.com
www.openismus.com
9 years, 5 months
[SyncEvolution] field merging + parameters
by Patrick Ohly
Hello!
I am adding support for PHOTO;VALUE=uri to SyncEvolution. A
straight-forward solution is this:
<field name="PHOTO" type="blob" compare="never" merge="fillempty"/>
<field name="PHOTO_TYPE" type="integer" compare="never" merge="fillempty"/>
<field name="PHOTO_VALUE" type="string" compare="never" merge="fillempty"/>
But... what if one contact has PHOTO:<binary data> and gets merged with
a contact that has PHOTO;VALUE=uri:http://foo.bar?
My fear is that I'll end up with PHOTO;VALUE=uri:<binary data>, because
of the "fillempty" merge mode for PHOTO_VALUE. A similar problem also
exists for PHOTO_TYPE.
What I would need is a "fillempty" for PHOTO and a
"copy-if-photo-was-copied" for the other two fields.
I don't think that exists, so my current approach is to have an incoming
script which ensures that the PHOTO_VALUE is never empty (sets "binary"
if unset) and an outgoing script which strips it again (to emulate
current behavior). It's not working 100% correctly because for field
lists populated with PARSETEXTWITHPROFILE() the incoming script is not
executed.
Am I on the right track or should I simply ignore the problem?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
9 years, 5 months
