Date: Sun, 28 Sep 1997 21:27:12 -0700 From: John Polstra <jdp@polstra.com> To: ccsanady@bob.scl.ameslab.gov Cc: hackers@freebsd.org Subject: Re: CVS permissions after checkout Message-ID: <199709290427.VAA22383@austin.polstra.com> In-Reply-To: <199709260008.TAA10113@bob.scl.ameslab.gov> References: <199709260008.TAA10113@bob.scl.ameslab.gov>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <199709260008.TAA10113@bob.scl.ameslab.gov>, Chris Csanady <ccsanady@bob.scl.ameslab.gov> wrote: > I have recently cvsuped a cvs tree, but am experiencing some interesting > problems. I am not sure why, but after I cvsup, my entire repository is > marked as executable. This happened because the execute permissions in the repository were all screwed up on the mirror site from which you did your update. I just found out about it myself, and it's fixed now. The new version 15.2 of CVSup (by coincidence released today) corrects any bad permissions on each update. Until version 15.2, the permissions were set correctly on the first creation of a file, but ignored after that. This was a design decision which I subsequently decided was wrong. Bottom line: Upgrade your CVSup client, and then do an update from a server which is also running the latest version. All of them should be upgraded soon. I know for a fact that cvsup.freebsd.org and cvsup2.freebsd.org are already upgraded. (Freefall is too.) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709290427.VAA22383>