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

Re: FEATURE: Something like a 'svn rebuild'

From: Listman <listman_at_burble.net>
Date: Sun, 25 May 2008 22:03:52 -0700

On May 25, 2008, at 9:12 PM- May 25, 2008, Karl Fogel wrote:

> Talden <talden_at_gmail.com> writes:
>> To me, this feels like something that should be available to every
>> user should they need to repair their WC though.
>> Requiring that all users must have scripting engine X installed in
>> addition to Subversion doesn't seem ideal.
> We have no data on how often this comes up, and IIRC have received few
> posts about it. It's hard to justify a new core feature based on
> that.
> If we try to make as many of our contrib scripts be in (say) Python as
> possible, then at least once a user installs Python for any script,
> it'll be installed for many other scripts they might need in the
> future.

my company experiences this a lot. working copies get broken
regularly, usually by some other misbehaving tool writing into the
managed dir and corrupting the .svn metadata. a way to rebuild the
broken meta-data (without losing any local modifications) would really
help in this situation.

the kinds of issues we see regularly are:

- orphaned locks - a file not locked in the WC but locked in the depot
(with only 1 WC)

- trashed .svn dirs - we find the .svn dir gets set to zerolength file
by certain unsociable tools..

To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-05-26 07:04:28 CEST

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

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