Re: evolution sync problem with newest pilot-link
Okay, I just used bugreport to file a bug for this against gnome-pilot.
As I mentioned in the report, I've also tried to recompile gnome-pilot
0.1.65 against libpisock8, but get the below errors and am unable to
continue....
./.libs/libgpilotdconduit.so: undefined reference to `sync_CopyToPilot'
./.libs/libgpilotdconduit.so: undefined reference to `sync_Synchronize'
./.libs/libgpilotdconduit.so: undefined reference to `sync_CopyFromPilot'
./.libs/libgpilotdconduit.so: undefined reference to `sync_MergeToPilot'
./.libs/libgpilotdconduit.so: undefined reference to `sync_MergeFromPilot'
collect2: ld returned 1 exit status
make[2]: *** [gpilotd] Error 1
make[2]: Leaving directory `/home/gideon/builds/gnome-pilot-0.1.65/gpilotd'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/gideon/builds/gnome-pilot-0.1.65'
make: *** [all-recursive-am] Error 2
I also mentioned this in the bugreport, but the same thing happened with
evolution 1.0.7 and gnome-pilot 0.1.64. Data loss in calendar sync,
since evolution was linked to libpisock5 and gnome-pilot was linked
against libpisock4, if memory serves. I was able to recompile
gnome-pilot 0.1.64 against libpisock5 with a patch from JPR (ximian) to
fix it that time. This time, however, gnome-pilot 0.1.65 won't compile
against libpisock8.
ARrrrgh!!
On Tue, 2002-08-20 at 11:38, Ben Darnell wrote:
> On Tue, Aug 20, 2002 at 10:36:59AM -0400, Jason 'vanRijn' Kasper wrote:
> > 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...
>
> Hmm, I've tried to make the different versions of libpisock able to
> peacefully coexist, but it sounds like that's not working. If anyone
> knows what I need to do to get upgrades to work smoothly, please let me
> know.
>
> >
> > - if a bug report has been filed for this?
>
> According to bugs.debian.org/gnome-pilot, no.
>
> > - who to talk to to make sure this doesn't happen again?
>
> Mike Markley (mike@markley.org) is the maintainer of gnome-pilot and
> therefore the one to talk to when this happens. That doesn't keep it
> from happening again though; I'm not sure what needs to be done to
> prevent it.
>
> > - what the correct mailing list is for this?
>
> debian-pilot is probably best; debian-gtk-gnome might be better
> for gnome/evolution related issues
>
> > - where to file a bug report?
>
> It sounds like gnome-pilot is the package you want to file a bug report
> against. If you're new to filing bug reports (or even if you're not
> new), I recommend that you install the reportbug package and use it to
> help generated the report.
>
> 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: