Re: Initial sync pickup



On Fri, 2004-05-28 at 09:27, Nigel Metheringham wrote:

> Have you any description as to what patches are doing?
> 
> I don't recognise what the first one (marshalls) is doing at all - looks
> like maybe a gnome version update thing?, the second touches the memo
> file conduit - looks like API fixes - maybe that fixes the memo file
> louse ups, and the last one doubles the size of a buffer....

See
http://bugzilla.gnome.org/show_bug.cgi?id=114361

The marshalls patch updates for gtk api changes.  Without it, a junk
callback pointer is retrieved from the stack, leading to a subsequent
segfault.  There were compiler warnings when compiling gpilot that were
being ignored.  There are still others.

As it turns out, the memo-conduit appears to be the only conduit that
calls into this code.

The memo-file patch reverses change that was put in to prevent the
(unidentified) marshals problem from causing a segfault.  As a
byproduct, it broke memo-file syncing except where the memo-file
directory already existed or was created by hand.

> On Fri, 2004-05-28 at 08:05, Victor Gregorio wrote: 
> > Does the memo conduit work OK on FC2?  
> 
> Not on vanilla FC2.   Maybe that patch fixes it.  I can push these to
> Fedora if I can understand what they are doing...

That would be great, if you have lines of communication open!  Robert
Locke raised a fedora bugzilla ticket #113230 back in January, with a
pointer towards the gnome-pilot bugzilla ticket I've linked to above. 
We both mailed the redhat maintainer/packager but heard nothing back.

Matt
-- 
Matt Davey      You will become one with the Universe next week, incurring
matt corvil com 	    the wrath of all the Universe's old boyfriends.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]