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

Re: Unix and a commit by a different user.

From: John Peacock <jpeacock_at_rowman.com>
Date: 2004-04-24 13:08:13 CEST

Gleason, James D wrote:
> We had a working view owned by one user.

We call them Working Copies here (WC). Are you used to ClearCase?

> Another user did a commit from that view.
> He got an error that said something about text-base. [We don't have the
> error recorded]

You are probably talking about this issue:


Update your server and clients to Subversion 1.0.2 and it should work for you now.

> Now we get
> svn: Checksum mismatch for
> 'common/mcap/.svn/text-base/coe.mux.mcapx.rt_bm.2.ada.svn-base';
> expected: 'b9cfa97357c4e3b06c476fd344214dcb', actual:
> '2238a24ae1dedb84d171193cd497bf3c'
> So I have two questions ...
> Is this working view permanently corrupted?

Probably the easiest way to resolve this part is to check out the WC anew. If
you have pending local changes, copy them into the new checkout before deleting
the old WC (i.e. mv the existing WC out of the way, check out a new WC, then
selectively copy back the changed files).

> Is it possible for one user to commit from a working view owned by
> someone else?

In general, shared working copies are not usually the right mode of operation,
but in some situations they are preferably to the alternative (two WC's with
multi-GB storage requirements). If your files are not huge, you should probably
enforce a single user per WC, just for simplicity purposes.



John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Apr 24 13:08:30 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.