Status in ignored directory triggers "is not under version control" error
Hello, I have a directory dir1/dir2 in my SVN working copy that has depth=empty set, e.g. after "svn up --set-depth empty". Someone else deletes a file in that ignored directory. Now I do a "svn st -u" in my working copy and get an error: svn: 'dir1/dir2/file1' is not under version control What is the reason of the error? What can I do to get rid of the error? I thought directory dir1/dir2 is ignored, why does SVN care about a file in that directory? Is this a known bug? I use SVN version 1.6.15 (r1038135). Here is a script to show the error: - Script Start - #! /bin/sh ### inuvc.sh - Script to show the "is not under version control" error ###message that is seen if a resource in an empty ###directory is removed. repoRoot="`pwd`/repo" repoUrl="file://$repoRoot" wcRoot="wc" startDir=`pwd` ### Remove old repository and working copy. if [ -d $repoRoot ]; then rm -rf $repoRoot; fi if [ -d $wcRoot ]; then rm -rf $wcRoot; fi ### Create new repository. svnadmin create $repoRoot ### Create working copy and add some data. svn co $repoUrl $wcRoot cd $wcRoot svn mkdir dir1 svn mkdir dir1/dir2 touch dir1/dir2/file1 svn add dir1/dir2/file1 svn ci -m "Created some data." ### Switch dir2 to empty. svn up --set-depth empty dir1/dir2 ### Remove the file. svn rm -m "Removed the file." $repoUrl/dir1/dir2/file1 ### Do a status. This triggers the error: ### svn: 'dir1/dir2/file1' is not under version control svn st -u - Script End - Thanks, Holger -- Holger Schmidt Lead Design Engineer Methodology and Design Automation Zentrum Mikroelektronik Dresden AG Grenzstraße 28, 01109 Dresden, Germany Phone: +49.351.8822.9 0 3 holger.schm...@zmdi.com www.zmdi.com Executive Board: Thilo von Selchow (CEO), Steffen Wollek (CFO) Chairman of the Supervisory Board: Carl-Peter Forster Amtsgericht Dresden: HRB 19 166; Ust-Ident.-Nr.: DE151798300 This email is confidential. It may be read, copied and used only by the intended recipient. If you are not the intended recipient, you must not disclose or use the information contained in it. If you have received this mail in error, please tell us immediately by return email and delete this email.
Re: Status in ignored directory triggers "is not under version control" error
Holger Schmidt writes: > What can I do to get rid of the error? Upgrade to 1.7. $ svn1.6 st wc1 svn: 'wc/dir1/dir2/file1' is not under version control $ svn1.7 st wc2 Status against revision: 2 -- Philip
Re: Parallelising SVN Checkout
On Tue, Sep 4, 2012 at 10:26 AM, Jonathan Holloway < jonathan.hollo...@gmail.com> wrote: > > Has anybody had any success in parallelising Subversion checkouts in the > past on a subfolder level > to improve performance at all? > > By this I mean using svn sparse directories with --depth intermediates to > produce a skeleton structure, > such as: > > project > * subfoldera - handled by a checkout thread > * subfolderb - handled by a checkout thread > > http://svnbook.red-bean.com/en/1.5/svn.advanced.sparsedirs.html > > then forking a process/starting a thread to svn update the subfolders? > Does this make sense from a > performance point of view or is the bottleneck of disk I/O always > hit pretty early on by doing this? > > > http://stackoverflow.com/questions/4160070/can-an-svn-checkout-be-multi-threaded > > I've done this with a Python script and the multiprocessing module (and > daemon processes) so far. I > just wanted to check to see if there was an existing solution to this. > You will not be able to do this with SVN 1.7+ as there is a single working copy admin area that will be locked by the first process that obtains the lock. If you are using HTTP(S), you can switch to using the ra_serf library which opens multiple connections to the server and fetches multiple files at once. In 1.8, this will be the new HTTP client library. -- Thanks Mark Phippard http://markphip.blogspot.com/
Re: Parallelising SVN Checkout
On Tue, Sep 04, 2012 at 03:26:36PM +0100, Jonathan Holloway wrote: > then forking a process/starting a thread to svn update the subfolders? > Does this make sense from a > performance point of view or is the bottleneck of disk I/O always > hit pretty early on by doing this? Did you make any performance measurements? Checkout is mostly I/O bound, so I doubt doing this has much benefit unless you have an I/O system that is highly parallelized.
Re: Parallelising SVN Checkout
Hi Stefan, Well it's early on in the process, the script works, but I've not tested it on a local repository yet with a suitably sized project. The remote Tomcat Apache project (approx 64MB) that I did "checked out" slightly slower with the script. I haven't delved into i/o stats or network latency there yet. It was a simple proof of concept. I just wanted to check with everyone here as to whether it made sense to continue with the investigation, Judging by what Mark says above though, it sounds like this doesn't make sense with 1.7. Thanks for the info on the ra_serf library though. Many thanks, Jon. On 4 September 2012 15:37, Stefan Sperling wrote: > On Tue, Sep 04, 2012 at 03:26:36PM +0100, Jonathan Holloway wrote: > > then forking a process/starting a thread to svn update the subfolders? > > Does this make sense from a > > performance point of view or is the bottleneck of disk I/O always > > hit pretty early on by doing this? > > Did you make any performance measurements? > > Checkout is mostly I/O bound, so I doubt doing this has much benefit > unless you have an I/O system that is highly parallelized. >
Need Help : Purging very old (/unwanted) revisions
Hi My organization's svn repository size has grown too large and most of the old revisions of documents are never being used. Consider I have 4 documents in my repository, of which I have 10 revisions: 4 for document A 3 for document B 2 for document C 1 for document D. Now, I want to keep only the last 2 revisions of all documents i.e 2 for A, 2 for B, 2 for C and 1 for D.. Is there any way I can achieve this in my subversion repository? Thanks in Advance Regards Vinay
RE: Need Help : Purging very old (/unwanted) revisions
Hello, You can create a new repository then get the second to last revision and use that to create a new project in that new repository. Then create a working copy and replace it with the current revision. Then do a commit and you're done. JPM From: vinay modi [mailto:modivi...@gmail.com] Sent: Tuesday, September 04, 2012 4:04 PM To: users@subversion.apache.org Subject: Need Help : Purging very old (/unwanted) revisions Hi My organization's svn repository size has grown too large and most of the old revisions of documents are never being used. Consider I have 4 documents in my repository, of which I have 10 revisions: 4 for document A 3 for document B 2 for document C 1 for document D. Now, I want to keep only the last 2 revisions of all documents i.e 2 for A, 2 for B, 2 for C and 1 for D.. Is there any way I can achieve this in my subversion repository? Thanks in Advance Regards Vinay
Re: Need Help : Purging very old (/unwanted) revisions
vinay modi wrote: >My organization's svn repository size has grown too large and most of the >old revisions of documents are never being used. >[...] >Now, I want to keep only the last 2 revisions of all documents i.e 2 for A, >2 for B, 2 for C and 1 for D.. http://subversion.apache.org/faq.html#removal and http://subversion.tigris.org/issues/show_bug.cgi?id=516 -- Lorenz
