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

Re: Corrupt .svn directory using Subversion 1.7

From: Thorsten Schöning <tschoening_at_am-soft.de>
Date: Mon, 20 Aug 2012 08:37:53 +0200

Guten Tag Steven Lee,
am Sonntag, 19. August 2012 um 17:08 schrieben Sie:

> I am using Subversion 1.7.0. I wanted to exclude a directory from my
> working copy so I entered "svn update --set-depth exclude foodir". In
> the middle, I decided to cancel this operation. Now I'm in a state
> where some files under foodir are missing but SVN thinks all of the
> files are there.

--set-depth exclude foodir should have prevented the whole folder from
being updated, so if it's there it's because of a former checkout and
it's contents will be ignored because you told the working copy to do
so. What are you really trying to achieve? Do you want foodir being
updated or not?

> I tried to do a 'svn revert' and 'svn checkout' but
> nothing happens because it thinks the files are already there.

svn checkout won't work in a already existing working copy and svn
revert --recursive . will revert only those files missing besides
those you excluded in foodir.

> 'svn
> status' thinks nothing has changed but 'svn ls' shows that some
> files/directories are missing from my working copy.

Please provide exact error messages as at least I don't seem to
understand what/where your problem is depending on what you actually
want to do.

> Prior to Subversion 1.7, I would have been able to simply remove the
> .svn directory /in that directory/ and check out the files again.

If you really did a checkout you created two distinct working copies,
which may or may not work as expected. You should have used at least
update and even with that if you just have deleted the .svn directory
you would have got conflicts with maybe already existing files and
directories. I doubt this was ever an supported use case.

> But
> now, I have to remove the .svn directory at the top level and check out
> all of the files again.

No, you can always update and provide a new value for --set-depth or
just use the --depth arg. See svn help update for details.

> The repository is huge so I want to avoid that,
> and plus all of my timestamps on the files/directories would be updated
> which is undesirable.

Backup the files including the timestamps, update your working copy
and copy the the backups over again.

> Is there a simpler workaround? Is it possible to
> just fix or just re-checkout the files for that directory?

svn update --set-depth inifinity will update your working copy and
foodir.

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning       E-Mail:Thorsten.Schoening_at_AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/
Telefon.............030-2 1001-310
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
Received on 2012-08-20 08:38:29 CEST

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.