bug-cvs
[Top][All Lists]
Advanced

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

Re: CVS 1.12.13 hangs when getting gnulib


From: Mark D. Baushke
Subject: Re: CVS 1.12.13 hangs when getting gnulib
Date: Fri, 24 Nov 2006 12:53:22 -0800

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Yves Dorfsman <address@hidden> writes:

> > I was able to reproduce the problem when I used a
> > stock unmodified cvs 1.12.13.
> >
> > Your problem is the same problem as was reported
> > in [bug #14840]. I include a copy of the patch as
> > applied to the CVS FEATURE branch sources after my
> > .signature.
> 
> When, and where will this patch be in the tree ?

It has already been committed to the CVS sources... you could cherry
pick the change using something like this:

cvs -z3 -d:pserver:address@hidden:/sources/cvs \
  co -r cvs-1-12-13a ccvs
cd ccvs/src
cvs update -r1.32 zlib.c
cvs log -N -r1.32 zlib.c

(The 1.32 revision was added to the sources on 2005-10-28 14:10:59 +0000).

> When I look on http://ftp.gnu.org/non-gnu/cvs/source, I can find
> cvs-1.12.13 (from October 2005), and cvs-1.12.13a (from July 2006) in
> feature, and cvs-1.12.13.1 in nightly build, but from July 2006.

The windows build for cvs 1.12.13 was totally broken, so I believe that
1.12.13a was created as a fork of 1.12.13 to get that working. However,
the majority of the 1.12.13 sources date from October 3, 2005 and do not
contain the zlib.c patch you want.

> Since this email is from September, I am assuming this patch is not
> in any of the above version ? I also check at
> http://cvs.savannah.gnu.org/viewcvs/cvs/ccvs/src/zlib.c
> and it says this file is from September 2nd, so before this patch surfaced.

Yes, the patch is not a part of any officially released version of CVS.

> I want to build cvs with this patch in it, as well as all the latest ones,
> but I want to be able to put a reference in my documentations saying
> "grabbed version x of CVS from here", so that the exact same version can
> be recreated later if needed, without having to search for patches in the
> mailing list...

Well, see the above recipe for how to checkout a copy of the sources for
1.12.13a plus that one fix to zlib.c

The last change to the FEATURE (main trunk) branch of CVS was made on
2006-11-17 20:34:16 to contrib/log_accum.pl, so you could use a
timestamp between that date and now when you checked out the top-of-tree
'cvs 1.12.13.1' release which is how the trunk is presently labeled as
to revision.

> > This patch will be a part of cvs 1.12.14 when it
> > is eventually released.
> 
> Any idea when this is going to happen ?

I have no idea when that will happen. 

I believe that Derek is planning a change he needs to apply before the
new release will not confuse folks who may have old checked out trees
and no configured set of digital signatures.

You might want to do this and report if your platform has any problems:

cvs -z3 -d:pserver:address@hidden:/sources/cvs co ccvs
cd ccvs
./configure
make && make check

You will probably want to install GnuPG on your system before you do
this in order to support OpenPGP signatures.

If you DO NOT want to have the OpenPGP support (which may cause problems
using a newer client with an older server or older checked out tree),
you could alwasy remove the '#define HAVE_OPENPGP 1' line from the
config.h file before doing the build.

perl -i.bak -pane '$_= "/* $_ */" if /define\sHAVE_OPENPGP/;' config.h

If you do this, you should expect the 'make check' to fail as none of
the tests which check that there is a valid OpenPGP signature will work.

        Good luck,
        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (FreeBSD)

iD8DBQFFZ1vBCg7APGsDnFERAmlAAJ49EXaOQeo5ztznWRXOB9khvnPdXACgj6+i
NZzGTA1OP2HNeF2c6Kvai5g=
=vP4B
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]