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

Correction -> Malformed XML output from svn status command

From: Joakim Birgerson <joakim_at_birgerson.com>
Date: Mon, 26 May 2008 13:36:55 +0200

Hi again,

sorry for not thinking of redirecting stderr when describing bug 2 below.
The purpose of this bug report is bug 1, nothing else.

Regards,
/Joakim

---
*Malformed XML output from svn status command*
Hi all,
Following the instruction on http://subversion.tigris.org/bugs.html, I'm
pretty sure I've found a bug. Hope you agree and please advise if I'm
expected to take additional actions.
*Svn version*
1.4.5 (r25188) compiled Sep 19 2007, 23:10:31
Cygwin running on Windows XP
*Summary*
Malformed XML output when requesting status on a specific file.
Suggested priority: P2
*Background*
I'm synchronizing a repository and a working copy. Periodically I'm
collecting file information in the working copy looking for changes that
automatically get synchronized with the repository. Since I'm using a file
name filter to select which files goes into the repository, I'm only
interested in status information on files that meet my filter criteria (i.e.
I want to avoid a general "svn status --xml -u").
*
Example*
Check out any repository (can be empty) and add (not 'svn add') a new
directory *directory1 *containing a new file *file1.c*. Now request status
on the file.
/- root_wc_directory
 /- directory1
/- file1.c
*Command*
svn status --xml -u directory1/file1.c
*Response*
<?xml version="1.0"?>
<status>
<target
  path="folder1/file1.c">
svn: warning: 'folder1/file1.c' is not a working copy
</status>
*Bug 1:*
The response doesn't contain a </target> termination tag
*Bug 2:*
Svn warning message appears within the xml message
Kindest Regards,
Joakim Birgerson
-- 
Södervångsvägen 149
246 36 Löddeköpinge
Sweden
Mobile: +46 709 672477
Received on 2008-05-26 19:44:11 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.