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

1.9.1 bug in svnversion?

From: Asa Packer <apacker_at_biosonicsinc.com>
Date: Wed, 9 Sep 2015 16:32:44 -0700

Hello,

 

I just upgraded from TortoiseSVN 1.9.0 x64 to 1.9.1 x64 and noticed what I
think is a bug in the behavior of the command-line svnversion utility
included with TortoiseSVN. The bug is only noticeable when redirecting the
output of svnversion to a file, which some of my build scripts do.

 

Suppose I have a working copy at C:\foo where svnversion should return
"9141M". Here's the behavior I see in the Windows command shell:

 

If TortoiseSVN 1.9.0 x64 is installed:

C:\foo>svnversion

9141M

 

C:\foo>svnversion > out.txt

 

The file out.txt contains "9141M<CR><LF>", as expected.

 

If TortoiseSVN 1.9.1 x64 is installed:

C:\foo>svnversion

9141M

 

C:\foo>svnversion > out.txt

 

The file out.txt contains "M<CR><LF>9141"!

 

I see this behavior on two different machines, one running Windows 10 Pro
x64 and the other running Windows 7 Pro SP1 x64.

 

I was wondering if this was an issue with the upstream svnversion code, but
I installed the SlikSVN 1.9.1 x64 command-line binaries and there 1.9.1
behaves just like 1.9.0.

 

Is this something that is affecting other folks, or is it maybe just
something about my setup?

 

Thanks,

 

Asa

 

 

Asa Packer | Lead Systems Engineer

BioSonics, Inc. | 4027 Leary Way NW, Seattle WA 98107 USA
tel 206.782.2211 | fax 206.782.2244 | <http://www.biosonicsinc.com>
biosonicsinc.com

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=3136762

To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2015-09-10 15:53:10 CEST

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