Re: Problem with first revision of file being checked in, then deployed

On Sep 21, 2010, at 14:08, David Bartmess 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 -r<PriorRev>:<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.assemb<snip>' in revision 40851

diff summarize works fine for me in Subversion 1.6.12 even when the file doesn't exist in the prior rev. Are you using the latest Subversion?

Another possibility would be to use "svn log -q -v -r<PriorRev>:<CurrRev>" instead of diff summarize.
Received on 2010-09-21 23:29:01 CEST