-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mar 17, 2007, at 3:35 PM, [EMAIL PROTECTED] wrote:
> I successfully checked the code out via svn. I tried to do a cvs > diff in my > old repository to see if I had any pending changes and got this error: > > % cvs diff > ? python-mode-face-creation.patch > cvs diff: failed to create lock directory for `/cvsroot/python- > mode/python-mode' (/cvsroot/python-mode/python-mode/#cvs.lock): > Permission denied > cvs diff: failed to obtain dir lock in repository `/cvsroot/ > python-mode/python-mode' > cvs [diff aborted]: read lock failed - giving up > > I don't know if that's a side effect of the change or not. If not, we > should ask SF to fix the problem. If so, it would be nice if they > at least > retained read access to the repository for diffing. I'll just diff > my CVS > and SVN sandboxes. Can I assume r425 is the version at the point > where you > switched? It could very well be an artifact of my turning off write access. I'm just guess, but maybe you need write access if you have a writable checkout and try to do a diff (because CVS wants to create a lock in the repository in that case). You could try enabling your write access to do the diff and see if that helps. There's only a handful of us that have developer privs on the project, so I'm not /too/ concerned about accidental CVS commits. I just did it so an accidental commit would let you know to switch to svn, but I guess it messes up this case too. Yep r425 was the switch point. Cheers, - -Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iQCVAwUBRf0ojHEjvBPtnXfVAQLjYAP7BpSV9g3bqvefIpMEXrtAUIc54XtSsopX 6s6YPFdOwjVMHKbgkpx/3/RWF9cVv4aHT92h6pfL/q5Gj+vcztQAKOzaDISlC6lC o2eo50Wn6rJNyVG6l/CKbFikBj0ojF1dJn01fJk9COUY3Jy3vD8uaZHHeysOvdPk lmliw0b7RJY= =88N5 -----END PGP SIGNATURE----- _______________________________________________ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
