Nicko, Which file are you talking about? The KEYS files should all be in SVN (at least, the master copies should be in SVN). You shouldn't have to update a KEYS file on the filesystem: instead update it in SVN, commit, and do an SVN update of the dist directory as needed...
Yoav (who's a bit confused about your question and may have misunderstood it) On 3/30/06, Nicko Cadell <[EMAIL PROTECTED]> wrote: > Curt, > > Just trying to add my public key to the dist/logging/KEYS file. > > It looks like you were the last person to edit the dist/logging/KEYS > file and I think that it has lost group write permission. > > -rw-r--r-- 1 carnold logging 10444 Jun 26 2005 KEYS > > Could you chomod g+w this file for me. > > Cheers, > Nicko > > > -----Original Message----- > > From: Curt Arnold [mailto:[EMAIL PROTECTED] > > Sent: 13 March 2006 20:35 > > To: Logging General > > Subject: Re: [VOTE] publish log4net 1.2.10 > > > > No tag for source, but did have an identified revision number > > (383994) for the source in the call for vote. Is the intent > > to create the tag only after the votes by the PMC and Incubator? > > > > MD5 checksum verified. > > > > Nicko's key is not present in http://www.apache.org/dist/logging/ > > KEYS, but was at pgp.mit.edu, > > people.apache.org:~nicko/.pgpkey and > > http://people.apache.org/~henkp/trust/apache.html. > > > > I'd like to hear from one of the other log4net committers > > that they were able to reproduce the build (with the > > exception of timestamps et al). > > > > > -- Yoav Shapira Nimalex LLC 1 Mifflin Place, Suite 310 Cambridge, MA, USA [EMAIL PROTECTED] / www.yoavshapira.com
