[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

svn 1.1.0 rc 1 & shared working copies

From: Robert Guthrie <rguthrie_at_pobox.com>
Date: 2004-07-15 17:31:42 CEST

I've got an issue where I'm using a working copy with some people who
forget to chmod new files so that our group can read/write them. We're
not allowed to set the umask to make this automatic.

The relevant point here is that in my working copy, I have a directory
for temporary files (/tmp is on a tiny partition, so it unsuitable). I
want to keep the temp directory under revision control, so that when we
check the repository out somewhere else, the directory is already there.

But, with version 1.0.5, I get this error from running "svn stat -q" if
that directory contains files that I cannot read or write to:

$ svn stat -q
M some/file/I/changed.txt
M some/other/file/alsochanged.txt
svn: Can't read directory 'tempdir': Partial results are valid but
processing is incomplete

I've changed file & dirnames to protect the guilty, but everything else
is from a copy and a paste.

In "tempdir", there are files with rw------- permissions set. I do not
own the files.

I've tried setting "svn:ignore" to "*", but I still get the same error.

How is this relevant to 1.1.0 rc 1? I statically compiled the client,
and replaced the 1.0.5 version with the 1.1.0 rc 1 version. I was
hoping that just changing the client would aleviate the problem, but it
doesn't seem to. Is this issue linked to what version of the client
was used to check out the working copy?

And yes, I'm using the client I think I am:
$ svn --version
svn, version 1.1.0 (Release Candidate 1)
    compiled Jul 14 2004, 16:26:20

---snip ----


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 15 17:32:01 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.