[Evolution] Syncing Palm w/Evo 2.x

[Greg Macek]

Well, here's the issue I think I'm having.

I went back to red-carpet and found a package called evolution1.5-pilot.
I tried to install it (on SUSE 8.2) and here's the message I receive:

-------------------------
Unresolved dependencies:

Installing
evolution1.5-pilot-2.0.1.0.200410120356-0.snap.ximian.7.1[Evolution
Development Snapshot]

There are no installable providers of
=evolution1.5-2.0.1.0.200410120356-0.snap.ximian.7.1 for
evolution1.5-pilot-2.0.1.0.200410120356-0.snap.ximian.7.1[Evolution
Development Snapshot]

evolution1.5-pilot-2.0.1.0.200410120356-0.snap.ximian.7.1 is scheduled
to be installed, but this is not possible because of dependency
problems.

Marking this resolution attempt as invalid.
-------------------------

This is probably part of my issue. Is it just needing an updated
package? 

I don't mind if it only syncs up one list/calendar for now. But the
thing is that the Palm thinks it's syncing up to something, but it
isn't.

On Mon, 2004-11-01 at 17:26 +0000, Nigel Metheringham wrote:
> On Mon, 2004-11-01 at 12:03 -0500, Jeffrey Stedfast wrote:
> > Works for me (or did when I was testing it prior to release).
> 
> 
> I think I'd limit that a little...
> 
> Evolution 2.0 will sync *one* addressbook/calendar/task-list to a palm.
> The one chosen is, I think, the first one you see in the
> contacts/calendar/tasks folder list.
> 
> This is fine for most people.  If you are using exchange connector
> several bets are probably off.  To make matters worse, if it does work
> with exchange, it has problems deciding whats changed...
> 
> Private/public data within calendar stuff appears to be handled
> correctly.
> 
> Palm and Evolution categories are completely ignored.
> 
> However, for basic use it works very well - for example I do sync my
> calendar and contacts data and use that all the time very reliably (I
> don't normally use the tasks stuff which is why I am not mentioning it).
> I gave up using exchange-connector at all after I started upsetting MIS
> by apparently corrupting stuff on the exchange server (which I don't
> care about anyway).
> 
> 	Nigel.
>