Re: evolution sync problem with newest pilot-link
Okay, this just bit me again. Evolution 1.0.8 is compiled against
libpisock8, while gnome-pilot 0.1.65 is compiled against libpisock5. I
am unable to sync until gnome-pilot is recompiled against libpisock8
(which I tried to do myself and can't, due to API changes). How can I
tell...
- if a bug report has been filed for this?
- who to talk to to make sure this doesn't happen again?
- what the correct mailing list is for this?
- where to file a bug report?
Thanks.
grrrrrrrr, this is annoying.
On Sat, 2002-07-06 at 14:44, Ben Darnell wrote:
> On Sat, Jul 06, 2002 at 02:21:20PM -0400, Jason 'vanRijn' Kasper wrote:
> > The version of pilot-link that gpilotd is compiled against is 0.9.5,
> > while the pilot-link version on my system is 0.10.99. Any ideas as to a
> > cause or a solution, or even a "hey, weird, I'm seeing that too"?
>
> I don't use gnome, but I am the maintainer of the debian pilot-link
> packages and can explain what has happened with the 0.10.99 upgrade. If
> gpilotd only uses the libpisock library, it should be fine - libpisock4
> (0.9.5) and libpisock5 (0.10.99) can both be installed at the same time,
> and gpilotd will continue using libpisock4 until it is recompiled
> against libpisock5.
>
> If, on the other hand, evolution uses any of the pilot-link executables
> (such as read-ical or install-datebook), it's possible that it may be
> falling victim to changes in command-line parameters in those utilities.
>
> HTH,
> -Ben
> --
> Ben Darnell ben@thoughtstream.org
> http://thoughtstream.org
> Finger bgdarnel@debian.org for PGP/GPG key 1024D/1F06E509
>
>
> --
> To UNSUBSCRIBE, email to debian-pilot-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>
--
,-----------------------------------------------------------------//
| Jason 'vanRijn' Kasper :: Numbers 6:22-26
`
| All brontosauruses are thin at one end, much MUCH thicker
| in the middle, and then thin again at the far end. That is
| the theory that I have and which is mine, and what it is too.
,
| bash$ :(){ :|:&};:
`----------------------//
Reply to: