On Thu, 11 Jan 2007, Mark D. Baushke wrote: > -----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
Yep - If you can give me at resonable tag I can easily try... > work on all hosts yet. Feel free to submit patches to get it working > under additional hosts. on my Linux box it compiles fine at least. > > > 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. Exactly - I hope that I can disable this in one of the CVSROOT files per module of per repository. I understand the idea, but want at least to be able to select when to use this feature. > > 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. Thanx - excellent mail Mark! Peter Toft, Ph.D. [EMAIL PROTECTED] http://petertoft.dk Følg min Linux-blog på http://www.version2.dk/blogs/petertoft
_______________________________________________ info-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/info-cvs
