Mailing-List: contact users-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: local policy)
Date: Thu, 24 Feb 2011 21:13:23 +0100
From: Stefan Sperling <stsp@elego.de>
To: Gunnar Dalsnes <hardon@online.no>
Cc: users@subversion.apache.org
Subject: Re: TortoiseSVN 1.7 test drive
Message-ID: <20110224201323.GD27836@ted.stsp.name>
Mail-Followup-To: Gunnar Dalsnes <hardon@online.no>,
	users@subversion.apache.org
References: <4D66B8F6.3040905@online.no>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4D66B8F6.3040905@online.no>
User-Agent: Mutt/1.5.21 (2010-09-15)

On Thu, Feb 24, 2011 at 09:00:54PM +0100, Gunnar Dalsnes wrote:
> Hi,
> 
> I'm was taking TortoiseSVN-1.6.99.20920-dev-x64-svn-1.7.0-dev.msi
> for a test drive today, and here is my experience.
> 
> Converting my WC failed:
> Insufficient NODES rows for 'e:\svn\my app
> name\.svn\tmp\wcng\src\Tools\SomeProject\SomeFile.cs'. Try a
> 'Cleanup'. Cleanup did not help (as always).
> 
> No worries, did a clean checkout. Surprisingly, everything seems to
> work very well:-)

It generally works reasonably well (and has for most of the time since
1.6 was branched). However, if you poke around a lot you'll soon run
into edge cases that are broken.

A lot of them are already listed in the issue tracker:
http://subversion.tigris.org/issues/buglist.cgi?issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&target_milestone=1.7.0
http://subversion.tigris.org/issues/buglist.cgi?issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&target_milestone=1.7-consider

> 
> But I'm wondering, are there any plans in 1.7 for supporting sharing
> pristines between several WC's?

I'm not aware of such plans. It will probably come after 1.7.
See the above lists of issues. We have to concentrage on those before
adding more functionality, otherwise the release will never get done...

> I wish I could (in config file) specify a shared location for pristines.
> Ref-counts + deleting unrefed pristines would have to be ignored in
> this case I guess,
> since ref-counts can't easily be tracked back to the WC's from the
> shared pristine, since WC's can be moved or simply deleted.
> But I would not mind. Hard drive is cheap but network traffic is
> not, and I would easily trade:-)
> 
> If no one is looking into this, I'm considering adding such feature
> as I described.

Great! Help is always very welcome.
You might want to look at the recent threads on dev@ discussing
pristines to get an idea about the current state of things.

> BTW: For fun, I tried deleting all files in the pristine. Diff of a
> changed file did "work", but showed an empty before-file (strangely,
> I had expected a file not found error). Then I tried a revert of a
> changed file. This failed with file not found in pristine (as
> expected). The problem is, the file disappeared (maybe not a bug)
> but worse, the WC was no longer recognized as a WC, not even after
> restoring the pristine. Possibly, the wc.db became corrupt or
> locked, I don't know, at least it worked again when I restored a
> backup of wc.db. Scary bug me thinks. The WC should not become
> corrupt just because some file in pristine is missing. Ideally, it
> should ask to download the missing file, but I guess that's asking
> too much:-)

Can you write a small script that drives the svn command line client
to automate this process and trigger the problem? That would help a lot.
We could then log it into the issue tracker and someone will eventually
look at it closely.
 
> PS: These errors may be specific to TortoiseSVN, thou I have a
> feeling they are not.

Most likely not, no.