Re: [Mailman-Developers] Alert to the cvs maintainer: another case of permission denial
-----Original Message----- From: Ken Manheimer <klm@cnri.reston.va.us> To: Tomas Fasth <tomas@euronetics.se> Cc: Mailman-Developers@python.org <Mailman-Developers@python.org> Date: den 14 oktober 1998 20:52 Subject: Re: [Mailman-Developers] Alert to the cvs maintainer: another case of permission denial
On Wed, 14 Oct 1998, Tomas Fasth wrote:
I'm using :pserver:mailmancvs@cvs.python.org:/projects/cvsroot as root. Issuing a cvs update resulted in the following complaint:
cvs server: failed to create lock directory in repository
/projects/cvsroot/mailman/doc/IPC7': >Permission denied cvs server: failed to obtain dir lock in repository/projects/cvsroot/mailman/doc/IPC7' cvs [server aborted]: read lock failed - giving upDo you need some assistance in hunting this problem down?
The CVS guy is snagged by meetings during the day today - but he should be able to tackle this one soon.
Is the CVS guy on this list?
Just got another complaint: U templates/help.txt cvs server: cannot open /projects/cvsroot/mailman/templates/reenable.txt,v: Permission denied cvs server: cannot open /projects/cvsroot/mailman/templates/reenable.txt,v: Permission denied cvs server: templates/reenable.txt is no longer in the repository
The problem seems to occur when active developers add new files to the repository, possibly in combination with repository mirroring. The "cvs [server aborted]: read lock failed - giving up" have the potential of leaving the mailman source tree in an inconsistent state.
--Tomas
We've implemented a temporary fix which should eliminate the problems checking out new files from the public CVS tree. Ken and I agree it's a bit of a hack and the real problem is most likely in the behavior of rsync. Tracking that down is on our list of things to do, but will take more time.
-Barry
participants (2)
-
Barry A. Warsaw -
Tomas Fasth