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

problem with svnversion -n

From: Andrew McIntyre <mcintyre.a_at_gmail.com>
Date: 2005-10-31 09:10:52 CET

Hi subversion-users:

Recently Apache Derby hit an unusual problem with svnversion that I
think may be an svnversion bug. During Apache Gump's build of Derby,
which contains the Derby source code in a copied directory, Ant
records the output of 'svnversion -n .' to a file, which is later
read back in as an Ant property. Because this is not a checked-out
directory in the gump build, the version is reported as 'exported',
but with a newline attached.

Because this is later read back in as the version at which Derby was
built, and included in the manifest file for the Derby jar files,
this causes the generation of the Derby manifest file to fail because
the newline after 'exported' puts a newline into the manifest file in
an unacceptable location.

The problem appears to be in svnversion's main.c, line 287.
           SVN_INT_ERR (svn_cmdline_printf (pool, _("exported\n")));
should be:
           SVN_INT_ERR (svn_cmdline_printf (pool, _((no_newline ?
"exported" : "exported\n"))));

Similar problem at line 296. Comments? If there's a workaround to
suppress the extra newline for exported directories, let me know.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 31 09:13:00 2005

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.