Re: Problem with first revision of file being checked in, then deployed
On 9/21/2010 1:22 PM, Bostjan Skufca wrote: For database up/downgrades you should look into dbdeploy. Also, my svn client (latest) nicely shows all files modified AND added. The letter M or A in front of filename signifies it. b. On 21 September 2010 21:08, David Bartmessdingod...@edingo.net wrote: I'm automating the deployment of our software, and came across a problem. In order to only pull the files changed for a specific revision, I do a diff -rPriorRev:CurrRev --summarize. I then parse the output through sed to get just the filename. All this works normally, but if the PriorRev of the file doesn't exist (it was added in the CurrRev revision), it gives me an error (below) and doesn't return anything. My question is, is there anything I can do besides having to parse the output from the command for that error message? I don't want to have to pull ALL the files in revision CurrRev, because some of these are SQL scripts and can't be re-run again, if they were from a prior revision. svn: Unable to find repository location for 'https://subversion.assembsnip' in revision 40851 I think the problem comes from the fact that the directory holding the file was added at the same time as the file itself, so SVN doesn't see that directory until after an update or export is done. -- Dingo Dave Bartmess Broomfield, CO. USA http://edingo.net
Re: Multiple Repositories under one subversion daemon
On 9/1/2010 4:46 PM, Tech Geek wrote: I may have totally misunderstood you. Are the above paths you show working copy paths, or are they existing svn repositories? Those are not existing svn repositories yet. Let's just say that those project folders should be at those locations only and I want to create SVN repositories at each of those locations. I am using a Windows XP Pro machine. Also by symlink do you mean Windows shortcuts? From what you said, you need to create the repository and import from those locations into the repository. For that, you don't need to put the repository in those locations, you just need to import from those locations, then do a clean checkout from the repository into those locations. -- Dingo Dave Bartmess Broomfield, CO. USA http://edingo.net
Re: SVN update question
On 8/11/2010 5:20 PM, Phil Pinkerton wrote: I'd like to be able to update a working copy after deleting a file from the Repository and have the file I removed from the Repository also removed from the working copy when I do an update. Is that possible ? Why would you want to remove a file from the repository? All you should have to do is do an svn delete and it would be deleted from the working copy on the update. But the deleted file will still be there, just not seen in the HEAD working revision -- Dingo Dave Bartmess Broomfield, CO. USA http://edingo.net
Re: Getting started with subversion
On 7/14/2010 1:33 PM, Thomas Garrod wrote: I'm sorry guys (and gals), I have a very basic question: How to you get files into your repository. I've got the O'Reilly book (2nd Edition), but I'm afraid is presumes too much of me. I looked at chapter 2, page 18, and it includes the following: ...typically use this when you have an existing tree of files that you want to begin tracking in your Subversion repository. For example: $ svnadmin create /ver/svn/newrepos $ svn import mytree file:///var/svn/newrepos/some/project \ For the first line: what part of this is variable? For the second line: how do I know what to enter for var/svn?newreos/ some/project? The path to my files on my computer is Macintosh HD/Users/TommyHome/ KeelWorks/Projects/GraphicArt. My command client is Path Finder is set to Macintosh: MyTaxes09 TommyHome$ This is wrong, but I don't know how to change the directory. All tips accepted, except get a brain (I tried that). When I typed 'svnadmin create /ver/svn/newrepos' I got the following response: svnadmin: Repository creation failed svnadmin: Could not create top-level directory svnadmin: Can't create directory '/var/svn/newrepos': No such file or directory Macintosh:GraphicArt TommyHome$ Does the /var/svn directory exist? It doesn't create the entire path if it doesn't exist... -- Dingo Dave Bartmess Broomfield, CO. USA http://edingo.net
Re: How to access local svnserve repository in Windows
On 7/8/2010 1:25 PM, Itamar O wrote: On Thu, Jul 8, 2010 at 8:07 PM, David Bartmess dingod...@edingo.net mailto:dingod...@edingo.net wrote: I've setup a local repository under C:\svn_repository\Test using svnadmin create c:\svn_repository\Test, and want to access it via the command line svn.exe. The svnserve is setup as a Windows service, and I can see that it's started. The binpath in the service entry is C:\Program Files\CollabNet\Subversion Server\svnserve.exe --server -r C:\svn_repository -listen-port 3690 the syntax seems incorrect. I think the --server switch should be --service, That was a typo caused by me having to type it in from another machine for the email. the argument for the -r switch needs to be a repository (e.g. C:\svn_repository\Test), and the --listen-port switch is missing a -. Another typo on the --listen-port, but the -r is supposed to be a parent directory that I want to limit the svn access to, not necessarily a repository itself, according to the docs... The question is, what is the correct syntax for accessing the svnserve service to import a new project? I've tried the following with no success: svn import -m Test import . svn://dingo.home/Test svn: Unknown hostname 'dingo.home' svn import -m Test import . svn://localhost/Test svn: No repository found in 'svn://localhost/Test' if you run svnserve as I explained above, you should be able to access the repository via http://localhost/ (drop the Test). I'm not using a web server, just svnserve. http://localhost/ wouldn't get me anywhere maybe if you use the --listen-host dingo.home switch you will also be able to access svn://dingo.home/ -- Dingo Dave Bartmess Broomfield, CO. USA http://edingo.net
Can we use relative paths in svn:externals propset?
I have two projects under a single repository, with A being dependent on B being checked out. To set the svn:externals propset, can I use a relative path for the checkout directory for the depending (B) directory? Such as : svn propset svn:externals ../buildsupport http://URL/buildsupport/trunk BuildScripts Will this work? I can't afford to try it on that repository since it's a live development repository... Thanks! -- Dingo Dave Bartmess Broomfield, CO. USA http://edingo.net
Re: Can we use relative paths in svn:externals propset?
On 4/29/2010 2:18 PM, Blair Zajac wrote: On 04/29/2010 01:09 PM, David Bartmess wrote: I have two projects under a single repository, with A being dependent on B being checked out. To set the svn:externals propset, can I use a relative path for the checkout directory for the depending (B) directory? Such as : svn propset svn:externals ../buildsupport http://URL/buildsupport/trunk BuildScripts Will this work? I can't afford to try it on that repository since it's a live development repository... You can always try setting up externals by modifying them in your working copy and running svn update and see if you get the desired result. You don't need to commit the change to test it. IIRC, you can't have a relative path to a directory outside the directory where the external is, as it doesn't know if it's a Subversion working copy or not. Blair Thanks, that explains what I needed to know... Relative paths using a parent (..) or absolute paths aren't handled. So it won't work with my system, since all the build files point to a parent sandbox directory, not the current directory, for the dependencies... -- Dingo Dave Bartmess Broomfield, CO. USA http://edingo.net
Re: Unable to checkout files: Can't open file: Permission denied
On 4/13/2010 3:27 PM, Disc Magnet wrote: I did that. I ran these two commands. chgrp -R www-data myrepository chown -R 770 myrepository Now, I get this error: $ svn commit -m Updating svn: Commit failed (details follow): svn: Could not open the requested SVN filesystem Please help. Probably your http server isn't pointing to the correct path. Check your Location in the httpd.conf i.e., Location /repos SVNPath /home/magnet/myrepository /Location -- Dingo Dave Bartmess Broomfield, CO. USA http://edingo.net
Can I not use svnadmin load with a remote repository?
My company has done a preliminary spec for moving from CVS to Subversion, using the python script cvs2svn. The cvs2svn script works fine, but when I try to do an svnadmin load of the dump file created, using the Assembla https URL, it complains that it can't find a format file. After quite a bit of web searching, I think I see the problem. The path for the destination of where to load the dumpfile contents seems to have to be a file path, not a URL. Is this right? Or am I missing something? Thanks! -- Dingo Dave Bartmess Broomfield, CO. USA http://edingo.net
Re: Can I not use svnadmin load with a remote repository?
On 4/1/2010 12:26 PM, Jon Foster wrote: Andy Levy wrote: David Bartmessdingod...@edingo.net wrote: My company has done a preliminary spec for moving from CVS to Subversion, using the python script cvs2svn. The cvs2svn script works fine, but when I try to do an svnadmin load of the dump file created, using the Assembla https URL, it complains that it can't find a format file. After quite a bit of web searching, I think I see the problem. The path for the destination of where to load the dumpfile contents seems to have to be a file path, not a URL. Is this right? Or am I missing something? svnadmin requires local filesystem access for everything it does. Yep. Your SVN host (Assembla) might be able to take your dump file and load it for you - try asking them or filing a support request. If they won't do that, then you can work around this by: 1) Create a new empty repository on your hard disk. 2) Use svnadmin load to load the dump file into your local repository. (Note: cvs2svn has the option to create a new repository for you, which would let you skip steps 1 and 2). 3) Use svnsync to sync from your local repository to the real one. Note that the target repository has to be completely empty to do this. 4) Delete your temporary local repository. Kind regards, Jon That sounds like a plan. Even though we have quite a few projects to be imported, and we're doing them one by one, I can remove the repository and create a clean one, then svnsync to it from the repository on my local machine. I'll check it out and try it. Thanks! -- Dingo Dave Bartmess Broomfield, CO. USA http://edingo.net
