Re: [SyncEvolution] Problem with Syncevolution
by Suyog
Patrick,
I just saw that you have released new update, syncevolution 1.0 Beta 2. This is having GUI for BT sync.
I tried it and just could not do sync with my Nokia N82 over Bluetooth, I am using syncevolution 1.0 Beta 2 with Ubuntu 9.04. Please check attached message screenshot and log file.
Also I found that it automatically creates peer as Nokia_7210c , is this default for Nokia? I think 7210c is non smartphone S40, and N82 S60 version smartphone. so is this issue here?
Can you help here? May be I need to make change in config.ini file? I tried few things but it didnt work.
Also now since Moblin is merged with Maemo to form MeeGo, how Syncevolution will fit in ?
Do you expect more progress with syncevolution , especially better compatibility with Nokia Phones, OVI service? I will be really interested to know and get syncevolution working. I know many users who are facing issues with Phone PIM sync in Ubuntu over Bluetooth.This will be really useful for them.
Let me know if you want me to try/test something.
Thanks in advance.
Best Regards,
Suyog
> ----- Original message -----
> From: "Patrick Ohly" <patrick.ohly(a)intel.com>
> To: "Suyog" <suyog(a)ovi.com>
> Subject: Re: [SyncEvolution] Problem with Syncevolution
> Date: Sat, 30 Jan 2010 17:04:43 +0100
>
>
>On Sa, 2010-01-30 at 14:00 +0000, Suyog wrote:
> > Patrick,
> >
> > I got it working after installing libbluetooth2 which was available in
> > Ubuntu Hardy packages, I read that it will work without any issues
> > along with libbluetooth3. I got it from following location.
> > http://packages.ubuntu.com/hardy/i386/libbluetooth2/download
>
> Glad you got it working. I also just uploaded the promised recompiled
> binaries which no longer depend on libbluetooth. As an extra bonus, they
> also don't depend on libpcre.so.3 (without loss of functionality), which
> was a problem on Fedora 11.
>
> > Now I am getting various kind of issues while doing sync from GUI, i
> > tried google and OVI and both failed.
> >
> > I will try to play more with this and report issues to you later.
>
> Yes, please. When you report them via the bug tracker (see
> http://syncevolution.org/support) it'll be easier to ensure that all
> issues get resolved.
>
> > Also I did try 0.9.2 but still getting same issue which i have send to
> > Congwu, i.e I do not see addressbook in GUI. I did everything from
> > clean uninstall and install but still problem continues, Also I have
> > ensured in config file that addressbook sync is enabled.Seems very
> > strange issue. Can you help here?
>
> What is the output of "syncevolution --print-config <config name>
> addressbook"?
>
> > One good thing is that more people have tried and used syncevolution
> > successfully by following how-to which i posted on my blog, comments
> > have been encouraging.I wish you could add local bluetooth sync with
> > phones to GUI soon.That's really pain area right now with opensync.
>
> We do what we can - perhaps not enough yet, but we'll continue ;-}
>
> --
> 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.
>
--------------------------------------------------------------
Ovi Mail: Get mail on your mobile or the web
http://mail.ovi.com
12 years, 2 months
[SyncEvolution] N900, GPE, Google, Notes, Tasks?
by Robin Powell
I'm a Linux sysadmin by trade; I'm willing to do arbitrarily complicated
configuration. I'm not interested in writing code for this (too many projects
already, sorry).
Given that, is it possible to:
- sync GPE to google calendar on the N900? if so, what intermediary service
would I have to use?
- sync notes/memos, to anywhere web-based at all?
- ditto tasks?
Thanks.
-Robin
12 years, 2 months
Re: [SyncEvolution] Trying to sync with a Nokia E63 over bluetooth
by oscar＠valdez-bicard.com.sv
> Oscar Valdez wrote:
>>I'm unable to sync with a Nokia E63 over bluetooth.
>>
>>Using syncevolution 1.0beta1 with the following config:
> [...]
>>Syncs always fail with this message:
>>"unsupported transport type is specified in the configuration"
>>
> That's because bluetooth support was not enabled in 1.0beta1
> binary (because libbluetooth2 and libbluetooth3 incompatibilities),
> That have been solved in 1.0beta2a, so please update your installation.
>
Thanks. I've upgraded, and now get segfaults. Please follow up to my other
posting.
---
Oscar Valdez
12 years, 2 months
[SyncEvolution] SyncEvolution 1.0 beta 2 released
by Patrick Ohly
SyncEvolution 1.0 beta 2 is available. Binary packages are provided,
including Bluetooth support this time. Major improvements:
* easier setup of a phone with the sync-ui and GNOME Bluetooth
plugin
* prevention of slow sync enabled by default and integrated into
sync-ui
* recovery dialog and restore from backup in sync-ui
* database dumps and comparisons more efficient
Despite some open issues (see below), this release is ready for getting
packaged in staging areas of distros as replacement for 0.9.2 and for
day-to-day use. If you find issues, please report them:
http://syncevolution.org/support
SyncEvolution synchronizes personal information management (PIM) data like
contacts, calenders, tasks, and memos using the SyncML information
synchronization standard. Up to and including 0.9.x, a third-party
SyncML server is required. In the 1.0 beta, SyncEvolution itself is
already able to act as a SyncML server, both via HTTP and Bluetooth
(direct sync with phones).
As before, documentation for 1.0 is only available in the
"Development" section of syncevolution.org, including HOWTOs for
setting up the HTTP SyncML server and phones manually.
Details
=======
Setting up a phone became a bit easier with beta 2, because
SyncEvolution is now integrated with the GNOME Bluetooth panel: once a
device with SyncML client support is paired, a button offers to bring
up the sync-UI and configure or synchronize with that device. We do a
fuzzy match against the Bluetooth device name to find a suitable
template (not manufacturer/model, because that is not readily
available). Still not many (read: hardly any) templates available,
though.
The binaries on syncevolution.org are compiled with Bluetooth support.
libbluetooth2 or libbluetooth3 should be installed, but are not
essential. If there is no suitable version of it, the Bluetooth
channel has to be selected manually as part of the syncURL.
Unexpected slow syncs are prevented by default, in contrast to beta 1
where this feature was available but turned off. When an unexpected
slow sync is detected in a client, users have to follow the
instructions provided by the command line or sync-ui and choose how to
proceed (explicitly request slow sync, refresh from server or client,
restore from backup). SyncEvolution as server currently cannot prevent
slow syncs, even when initiating the sync with a phone.
In preparation for syncing automatically, logdir and database handling
was improved considerably. Backups use less disk space because
identical files share the same file content via hard links. This also
speeds up the synccompare Perl script. Database dumps and the
corresponding comparison are delayed until the session really runs,
which avoids doing needless work a) when the server a client tries to
contact is unreachable or down and b) by only including sources that
are really in use during a sync on the server side.
The Synthesis XML configuration was split up into different parts
which are assembled from /usr/share/syncevolution/xml. Files in
~/.config/syncevolution-xml override and extend the default files,
which my be useful when adding support for a new phone.
Summary of changes since 1.0 beta 1:
* sync-ui: recovery dialog (MB #8050), device setup, config usable with
long strings (MB #9278), fixed displaying of source phases during sync
(MB #9320)
* sync-ui + syncevo-dbus-server: integration with Bluez to detect paired
devices (MB #9216, MB #7089), select template based on device name (MB #7838),
detect network and Bluetooth connectivity (only with ConnMan, MB #7700),
passwords stored in GNOME keyring by syncevo-dbus-server are shown with
dots in sync-ui (MB #9169)
* Evolution addressbook backend: avoid picking CouchDB, second try (MB #7877)
* Evolution calendar backend: minor fix for change tracking when deleting
a single instance of a recurring event
* build fixes: Bluetooth compatibility (MB #9289), use libical _r variant
of calls because 0.43 has issues in the normal version, conflict with
system libsynthesis and libsmltk (MB #9811)
* Horde: avoid confusing the server with a deviceId that starts like the
ones used in old Funambol clients, helps with calendar sync (MB #9347)
* better reporting when SyncEvolution dies during a sync (only happend once
when it wasn't installed properly, but still... MB #9844)
* performance improvements: synccompare much faster/database dumps consume
less disk space/more intelligent about expiring obsolete session directories
and backups/database accesses are reduced in several backends (MB #7708),
shorter logs (MB #8092)
* slow sync detection: now also works in the case where the client detects
an anchor mismatch and enabled by default (MB #2416)
* OBEX transport: some error handling changes and removal of polling, now
also possible via sync-ui + syncevo-dbus-server (MB #9436)
* API changes: SyncSource introduces an "isEmpty" operation which is
needed for the slow sync detection
* SyncML: split up configuration (MB #7712), increased default message size
because the old one might have been too small for large DevInf structures
* several fixes for virtual data sources ("calendar+todo"): now works
on client side, fixed naming on server (MB #9664), fixed error message
for slow sync detection, supported in combination with sync-UI (MB #9535)
* fixes for shared configuration layout: finding sessions of peers in
non-default context, adding sources affected peers in the same context
(MB #9329), wrong context during --configure when using shortcut for peers
in non-default context (MB #9338)
Known gaps for 1.0 final and beyond:
Redesigned and reimplemented D-Bus API, required by sync-UI:
- 'syncevolution' command line tool bypasses D-Bus server and runs
sync sessions itself (MB #5043)
- availability of peers not detected when using NetworkManager
(connected for HTTP, paired for Bluetooth; MB #7700)
SyncML server in general:
- suspend/resume support is untested (MB #2425)
- the progress events and statistics reported for a SyncML client
are not generated when running as SyncML server, will require
a fair amount of refactoring in the Synthesis engine (MB #7709)
HTTP SyncML server:
- a configuration must be created for each peer manually, including
a remoteDeviceId value that contains the peer's SyncML device ID
(MB #7838)
OBEX SyncML server ("sync with phones"):
- does not support phones which require a SAN 1.0 message (MB #9312)
- determining a working configuration for an unknown phone requires
a bit of experimenting, which should be automated (MB #9862)
OBEX SyncML client:
- parsing of SAN message is rudimentary and depends on an existing local
configuration, needs to be refined depending on which SyncML server software
it is meant to work with (MB #6175)
Automatic sync (MB #6378):
- no support for the various server push notification mechanisms
- no intelligent detection of local changes
- no regular background sync, development is in progress
Upgrading from 1.0 beta 1: moving back and forth should work seamlessly
Upgrading from 0.9.x:
* Upgrading and downgrading should work seamlessly when using existing
configurations. But this being an beta, better ensure that you have
backups of both your data and your configurations in
~/.config/syncevolution.
* The new configuration layout is only used when creating new
configurations or explicitly invoking "syncevolution --migrate" (see
above). Such configs cannot be used by older SyncEvolution releases.
Source, Installation, Further information
=========================================
http://syncevolution.org/blogs/pohly/2010/syncevolution-10beta2-released
Source snapshots are in
http://downloads.syncevolution.org/syncevolution/sources
i386, amd64 and lpia binaries of 1.0 beta 2 for Debian-based distributions are
available via the "unstable" syncevolution.org repository. Add the
following entry to your /apt/source.list, then install
"syncevolution-evolution":
deb http://downloads.syncevolution.org/apt unstable main
These binaries include the new "sync-ui" GTK GUI and were compiled for
Ubuntu 8.04 LTS (Hardy). Older distributions like Debian 4.0 (Etch) can
no longer be supported with precompiled binaries because of missing
libraries, but the source still compiles when not enabling the GUI (the
default).
The same binaries are also available as .tar.gz and .rpm archives in
http://downloads.syncevolution.org/syncevolution/evolution. In contrast
to 0.8.x archives, the 0.9 .tar.gz archives have to be unpacked and the
content must be moved to /usr, because several files would not be found
otherwise.
After installation, follow the getting started steps:
http://syncevolution.org/documentation/getting-started
--
Patrick Ohly, on behalf of everyone who has helped
to make SyncEvolution possible:
http://syncevolution.org/about/contributors
12 years, 2 months
[SyncEvolution] getting started info for N900 <-> evolution over bluetooth
by Stefano Zacchiroli
Hi all,
I'm new to syncevolution and I'm trying to use it to synchronize my
N900 with Evolution (on a Debian/unstable box).
I've found quite a lot of "getting started" page on syncevolution and on
the maemo wiki, as well as very exciting announcements on the support
for synchronization over bluetooth without needing an external SyncML
sever. Still, I haven't found a "getting started" page describing how to
synchronize over bluetooth, I keep on finding references on how to setup
sync via external SyncML server.
Have I been looking in the wrong places?
In short, how can I sync evolution <-> N900 over bluetooth?
I'm using syncevolution 1.0 pre release on the Debian box [1] and
syncevolution from the "extras-devel" Maemo 5 repository.
[ Cc-ing the Debian syncevolution package maintainer, in case I'm making
some wrong assumptions on what is packaged and what is not. ]
Thanks to all of you for providing syncevolution!
Cheers.
[1] http://packages.debian.org/experimental/syncevolution
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
zack(a){upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...........| ..: |.... Je dis tu à tous ceux que j'aime
12 years, 2 months
[SyncEvolution] Limit calendar items synch by date range ?
by Christof Sulzer
Hello
is there a way to limit synchronized calendar items by date range (i.e. minus 60days / plus 90days from today) in order to reduce/speedup sync time ? I have calendar items a few years back in my main calendar but no need to see them all on my N900.
Thanks a lot,
Christof
12 years, 2 months
[SyncEvolution] Trying to sync with a Nokia E63 over bluetooth
by oscar＠valdez-bicard.com.sv
I'm unable to sync with a Nokia E63 over bluetooth.
Using syncevolution 1.0beta1 with the following config:
syncURL = obex-bt://00:23:B4:21:41:D8
loglevel = 5
PeerIsClient = 1
deviceId = sc-pim-50c37c43-11b5-475e-9f46-4bb645b3b80b
enableWBXML = 1
WebURL = http://www.scheduleworld.com
ConsumerReady = 1
defaultPeer = nokiae63
[addressbook]
sync = two-way
type = addressbook:text/x-vcard
uri = addressbook
[calendar]
sync = two-way
type = calendar:text/x-vcalendar
uri = calendar
[memo]
sync = two-way
type = memo
uri = memo
[todo]
sync = two-way
type = calendar:text/x-vcalendar
uri = todo
Syncs always fail with this message:
"unsupported transport type is specified in the configuration"
I'll appreciate tips and suggestions.
---
Oscar Valdez
12 years, 2 months
[SyncEvolution] sync failure
by Xavier Bestel
Hi,
I've installed syncevolution on my N900, configuring it to sync to an
egroupware server.
I think I've correctly setup the config (I started from a Funambol
config, changed the uris and types for the calendar/contacts/memo/todo
and a few other tidbits).
The starting state was:
- a calendar on the server with just 1 test appointment.
- the N900's addressbook rather full of contacts
Now the addressbook contacts have correctly been copied from the N900 to
the server, but the server's calendar didn't sync with the N900.
Syncevolution reports failure for the sync, but I don't know why.
Is that a known problem ? Is there some special config for that setup ?
I saw that there are a bunch of files generated under /home/user/.cache,
I may send them to you if it can help (and if they don't contain
sensitive information).
Thanks,
Xav
12 years, 2 months
[SyncEvolution] IM issues with n900 and MyFunambol
by Guillaume Lanquepin-chesnais
Hello,
I installed syncevolution from maemo extra-repository and configured for
myfunambol. I'm able to sync contacts, however, it does not take in
count of non-standard vcard fields as X-MSN (I don't get them in
evolution with syncevolution on ubuntu karmic). Especially, it seems
that maemo vcard format use even more strange staff:
X-MSN;TYPE="msn-pecan";X-OSSO-VALID=yes:foo@bar.com
So my question is the following: does myfunambol support X-MSN/JABBER
flied or maemo's vcard format is not standard (and syncevolution does
not handle it)?
Regards,
Guillaume
12 years, 2 months
[SyncEvolution] code review request
by Patrick Ohly
Hello Congu, Yongsheng!
Can you review my "pohly" branch? I've accumulated various fixes there
that both of you may have some thoughts on. I'm too lazy (and tired) to
ask for code reviews in the different Bugzilla entries.
--
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.
12 years, 2 months
