# SVN Status - Newer Revisions not being reported

**URL:** https://www.finalbuilder.com/forums/t/svn-status-newer-revisions-not-being-reported/3170
**Category:** Bugs
**Created:** [October 26, 2009, 8:59am UTC](https://www.finalbuilder.com/forums/t/svn-status-newer-revisions-not-being-reported/3170 "2009-10-26T08:59:16Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![flowsoftware](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/f/91b2a8/32.png) [@flowsoftware](https://www.finalbuilder.com/forums/u/flowsoftware)
#### Post date: [October 26, 2009, 8:59am UTC](https://www.finalbuilder.com/forums/t/svn-status-newer-revisions-not-being-reported/3170/1 "2009-10-26T08:59:16Z")

</div>

I'm trying to configure an automated nightly build that will only produce a build if changes have been committed to the SVN repository since the previous nightly build. &nbsp;I am sure this was working at one point but now the SVN STATUS action seems to be failing to detect Newer Revisions.

Here's the log from an action where I've deliberately committed a new revision to a single file (Flow.dpr):

&nbsp;Executing external process: C:\Program Files\SlikSVN\bin\svn.exe

Starting Directory: c:\build\flow

Parameters: **status --non-interactive --show-updates &nbsp;alpha -u**

Output from C:\Program Files\SlikSVN\bin\svn.exe

**&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;\* &nbsp; &nbsp; &nbsp;939 &nbsp; alpha\Flow.dpr**

Status against revision: &nbsp; &nbsp;940

Total Items Modified : 0

**Total Items Unmodified : 1**

Total Items Added : 0

Total Items Delete : 0

Total Items in Conflict : 0

Total Items related to Externals Definition : 0

Total Items Ignored : 0

Total Items Not Under Version Control : 0

Total Items Missing : 0

Total Items with Type Mismatch : 0

Total Properties Modified : 0

Total Properties UnModified : 1

Total Properties in Conflict : 0

Total items Unlocked : 1

Total items Locked : 0

Total items with History with Commit : 0

Total items Switched : 0

**Total items with Newer Revisions : 0**

Action failed due to "Fail Action If" conditions

Subversion status failed with return code 0

Command line was : svn status --non-interactive --show-updates &nbsp;alpha -u

&nbsp;

&nbsp;

I've emboldened the lines that I think are of significance.

&nbsp;

The log seems to indicate that the action is correctly identifying the file as not having been modified (in the "working copy"), which is showing as "Unmodified = 1". &nbsp;But although the status report itself clearly shows that the file has a newer revision in the repository (the '\*' in the status report), the action is failing to acknowledge the Newer Revision.

&nbsp;

I'm reporting this as a bug. &nbsp;Is this right, or have I missed something in my setup?

---

<div class="post-metadata">

### Author: ![flowsoftware](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/f/91b2a8/32.png) [@flowsoftware](https://www.finalbuilder.com/forums/u/flowsoftware)
#### Post date: [October 27, 2009, 2:08am UTC](https://www.finalbuilder.com/forums/t/svn-status-newer-revisions-not-being-reported/3170/2 "2009-10-27T02:08:07Z")

</div>

According to this:   
  
 [http://www.red-bean.com/pipermail/svnbook-dev/2009-May/005158.html](http://www.red-bean.com/pipermail/svnbook-dev/2009-May/005158.html)   
  
 the “out of date” (newer revisions) marker moved to col 9 in the SVN STATUS output as of SVN 1.6… could this be why the FinalBuilder action is not correctly detecting the presence of Newer Revisions in our repository?   
  
 We are using Visual SVN Server 2.0.7 (Subversion 1.6.5) and the SlikSVN cmd line client (also svn version 1.6.5).

---

<div class="post-metadata">

### Author: ![Vincent](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/vincent/32/938_2.png) [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)
#### Post date: [October 27, 2009, 2:28am UTC](https://www.finalbuilder.com/forums/t/svn-status-newer-revisions-not-being-reported/3170/3 "2009-10-27T02:28:46Z")

</div>

Yes, that’s exactly what the problem is… good find. I will implement a fix for it and post here when a build is available. In the future we’ll be changing all the actions to use the xml output format where possible so this sort of issue shouldn’t occur again.

---

<div class="post-metadata">

### Author: ![Vincent](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/vincent/32/938_2.png) [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)
#### Post date: [October 27, 2009, 3:22am UTC](https://www.finalbuilder.com/forums/t/svn-status-newer-revisions-not-being-reported/3170/4 "2009-10-27T03:22:44Z")

</div>

Here's the new build. The action has a new option "Subversion 1.6 or higher", check that option and it should work as expected.

https://www.finalbuilder.com/downloads/finalbuilder/630/FB630\_1783.exe

---

<div class="post-metadata">

### Author: ![flowsoftware](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/f/91b2a8/32.png) [@flowsoftware](https://www.finalbuilder.com/forums/u/flowsoftware)
#### Post date: [November 2, 2009, 2:51am UTC](https://www.finalbuilder.com/forums/t/svn-status-newer-revisions-not-being-reported/3170/5 "2009-11-02T02:51:25Z")

</div>

&nbsp;Sorry Vincent, I should have replied sooner.

That's great and has fixed our issue nicely! &nbsp;
