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

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

From: David Bartmess <dingodave_at_edingo.net>
Date: Tue, 21 Sep 2010 13:50:10 -0600

  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 Bartmess<dingodave_at_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 -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
>>
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
Received on 2010-09-21 21:50:56 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.