Bill Pringlemeir wrote: > > Quoting Bill Pringlemeir <[EMAIL PROTECTED]> from > >> It appears that GTKG is crashing when connecting with the recent > >> CVS copy.
> > My guess is that you don't have a complete consistent set of changes. This guess was just wrong. I put a clear and simple bug into sockets.c which caused the crashes. > > You must have at least: > > fileinfo.c,v 1.58 2005/08/30 > > sockets.c,v 1.54 2005/08/30 > Sorry, there are two/three fileinfo.c. One is in the ui/gtk/gtk2 and > the other is in src/core. Maybe the RCSID() should use $Header$ instead of $Id$ so that the duplicate filenames don't cause confusion. > Does the snapshot include the CVS with Entries, Repository, and Root? Yes, but you'd have to fix all Roots before you can use it as replacement for your checked out repository. > However, I think I was building the software correctly. The only real > problem I have had with "cvs update" was the recent addition of the > script directory. However, I figured this out by myself. You mean you don't use "cvs up -dP"? > I will use the snap shot if this saves you worries. The only problem with public CVS is that it's lagging. There are no inconsistencies. > I just like to > get a list of file changes; you guys change a lot of files quickly > ;-). The "cvs update" prints the file changes, it is not as apparent > with the tarball. You can also subscribe to the gtk-gnutella-cvs list. You'll see all diffs along with the commit comments. -- Christian
pgpLlYVnky1kq.pgp
Description: PGP signature
