-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Peter Toft <[EMAIL PROTECTED]> writes:
> I just wanted to verify my latest CVS error > <http://savannah.nongnu.org/bugs/?18743> with the trunk CVS version, > so I checked out CVS from ... CVS, and compiled it. A very adventurous thing to do. Be advised that the trunk CVS does not work on all hosts yet. Feel free to submit patches to get it working under additional hosts. > When using the trunk CVS and running "cvs init" I then got errors about > needing gpg secret key. I cannot find documentation about this or know how > to disable this binding to GPG. Can anyone comment and help me there? Well, the point of the new OpenPGP (initially only looking for GnuPG support) is to ensure that all commits are signed. So, you probably want to generate a GnuPG key-pair and start using them for your commits. That said, you could tell your client not to bother about such things as signing by doing this: cvs --no-sign init but you are probably going to be unhappy about most cvs operations that modify or verify things if you do not have a GnuPG key-pair. You will probably also find it highly desirable to look at the gpg-agent program which is a part of the GnuPG 2.x series of GnuPG programs. Documentation is present in the ccvs/doc/cvs.texinfo file under the 'OpenPGP Signatures' section. Enjoy! -- Mark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFpwKbCg7APGsDnFERAsLAAJ4j795TbdntqMmVxMQ9d+osfe8CcQCgmr96 7Vgl5cUFS4DS4ip/W4zVoxk= =fz2i -----END PGP SIGNATURE----- _______________________________________________ info-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/info-cvs
