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

Re: Export then import

From: Dave Robinson <dave.robinson_at_kirkfreeport.net>
Date: Wed, 02 Jan 2008 10:25:37 -0500

hope your 'festive' season went well. Mine was sufficiently
party-flavoured for the exact sequence of the svn problem to be a little
hazy, but I'll recap as best I can, warning - this will be lengthy.

First the context:
The repository has five top-level folders including 'Libraries' and
'Projects'. 'Projects' had several workspaces under it. The workspaces
each represent a set of our source code modified for a different release
of the development language. Each developer keeps a complete copy in his
working folders.

There is a conversion utility that makes a new workspace when the
language is updated. This does a complete windows copy of the workspace
folder structure.
As we weren't using svn when the previous release was made, we didn't
pick up on the fact that the .svn folders were copied too. This release
was from version 12.0 to version 12.1 of our software, so according to
our practice we 'converted' the project in KApps120 to KApps121.

We discovered that svn 'knew' about Kapps121 when we tried to add the
new project under a 'new' repo folder.
That's possibly problem 1: The add seemed to work anyway, or at least to
go through the motions, a new repo folder KApps121 structure was
created. However no updates or commits were possible. Probably TSVN
should warn that the repo folder being checked in/added is a duplicate
and already exists as Kapps120.

We blew away the working copy Kapps121 using windows and then the
repository Kapps121 using the repobrowser.

As there are no changes from Kapps120 yet, we then tried an 'export'
from Kapps120 to a new working folder structure Kapps121 (note the
accidental capitalisation change).
Problem 2: the export included the .svn folders again.
Problem 3. After deleting the .svn folders, tried the 'import in place'
got 'Commit succeeded, but other errors follow'
Error: Error bumping revisions post-commit (details follow):
Error: Can't move 'C:\devwork\Projects\KApps121\Appsrc\.svn\tmp\entries'
to 'C:\devwork\Projects\KApps121\Appsrc\.svn\entries': Access is denied.
This is because the entries file is set to read-only.
Try a commit to see if it picks up anything it forgot last time:
Error: Commit failed (details follow): File already exists: filesystem
'M:/svnrepos/db', transaction '1228-1', path
about 50% of the files are marked committed, the rest are marked with a
plus sign but won't commit. A revert clears the condition, but as I
can't sort the windows explorer dialog in svn-status order I have to
cherry-pick my way through 1300+ files.
I had help from Stefan, Lasse, Andy and John that pointed out several
things I should try, but with the possibility of tsvn retaining some
knowledge of the blown-away older version of KApps121 I decided the XP
working copy was not safe.

Gave up. Everything was still working normally on the Vista laptop so
decided something else on the XP machine is at issue. Eventually killed
the entire working copy and checked out a whole new one. Then built a
temporary working folder and added it, then checked that out too. All
works normally now, except that I have one small folder under the
'Libraries' branch that exhibits similar problems, again only on XP.
That's third-party code so I'll never touch it, so I'm happy to get on
with some work.

Hope this helps. TSVN is a great product and I know much of the above is
my mis-operation.

Yes I'm aware of the Vista issues, but the Vista laptop is really just
my off-site copy. (and export is broken in XP as well imho)


>>> simon.tortoisesvn_at_googlemail.com 12/31/07 5:24 PM >>>
On 29/12/2007, Dave Robinson <dave.robinson_at_kirkfreeport.net> wrote:
> Nope. (Took long enough)
> I'm trying a complete fresh checkout to the vista laptop where the
> existing folders are okay. Surely if there is a dupe then that will
> fail.
> If it doesn't fail then I believe the repos is probably okay and it's
> just the client machine.
> My approach after that would be:
> - uninstall Tsvn on the 'bad machine' and restart
> - delete the old version of the working folders
> - re-checkout and try again....

Dave, can you give us a clear reproduction recipe for this problem.
You seem to be trying several different things but you need to tell us
*exactly* what you are doing. We don't have the benefit of being able
to see your screen ;-)

Some comments on the emails so far:

You said you copied an entire WC including the .svn folders and then
tried to SVN add it? If you copy a WC you end up with another WC
already checked out from the same repository, so that would only
change the original project, not create a new one.

You mention using Vista. Are you aware that there are various problems
with Vista which will not be solved in any 1.4.x release, in
particular the export feature?



  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net 
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org 
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org 
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-01-02 16:28:41 CET

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

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