You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Steenveld, Andre" <A....@marin.nl> on 2016/02/10 16:09:25 UTC
svnversion output changed when redirecting the output. Why?
Hi,
I’m working with svn (via TortoiseSVN) versions 1.7, 1.8 and 1.9 and due to external factors I cannot bring it up to the same version.
Also, I’m using svn via the TortoiseSVN package but I believe that my question is related to svn and not to TortoseSVN, please correct me it this is not the case.
I use the svnversion command to keep track of versions in my sandboxes. For this I redirect the output from svnversion to a file and use that file in other parts.
For versions 1.7 and 1.8 the command line output from svnversion is identical to the redirected output. But for version 1.9 it is not and there is no command line option to get it to the `old style’ output.
Here is an example for 1.8
C:\…> svnversion .
22923:22924M
C:\...>svnversion . > output.txt
C:\...>type output.txt
22923:22924M
And here is the same example but now for 1.9
C:\…> svnversion .
22923:22924M
C:\...>svnversion . > output.txt
C:\...>type output.txt
M
22923:22924
Note that if the sandbox is not modified the first line is an empty one.
Question:
Why is the M (sandbox modified) on a separate line?
How do I get ‘1.8’ behavior back for this 1.9 version of svnversion?
Kind regards.
André Steenveld | Software Engineer | Production Onderhoud, Ontwikkeling & Support
MARIN | T +31 317 49 34 30 | A.H.M.Steenveld@marin.nl<ma...@marin.nl> | www.marin.nl<http://www.marin.nl>
[LinkedIn]<https://www.linkedin.com/company/marin> [YouTube] <http://www.youtube.com/marinmultimedia> [Twitter] <https://twitter.com/MARIN_nieuws> [Facebook] <https://www.facebook.com/marin.wageningen>
MARIN news: Viscous free-surface power predictions for self-propulsion using a hybrid RANS-BEM coupling procedure<http://www.marin.nl/web/News/News-items/Viscous-freesurface-power-predictions-for-selfpropulsion-using-a-hybrid-RANSBEM-coupling-procedure.htm>
RE: svnversion output changed when redirecting the output. Why?
Posted by Bert Huijben <be...@qqmail.nl>.
This is a known issue with some slightly older builds of TortoiseSVN.
Please upgrade and otherwise (re-)report the issue at the TortoiseSVN project as this is (was) caused by their specific build scripts.
This issue is (was) caused by linking and using multiple CRT instances inside the same program, causing undefined behavior inside Visual C++ code.
Bert
From: Steenveld, Andre [mailto:A.H.M.Steenveld@marin.nl]
Sent: woensdag 10 februari 2016 16:09
To: users@subversion.apache.org
Subject: svnversion output changed when redirecting the output. Why?
Hi,
I’m working with svn (via TortoiseSVN) versions 1.7, 1.8 and 1.9 and due to external factors I cannot bring it up to the same version.
Also, I’m using svn via the TortoiseSVN package but I believe that my question is related to svn and not to TortoseSVN, please correct me it this is not the case.
I use the svnversion command to keep track of versions in my sandboxes. For this I redirect the output from svnversion to a file and use that file in other parts.
For versions 1.7 and 1.8 the command line output from svnversion is identical to the redirected output. But for version 1.9 it is not and there is no command line option to get it to the `old style’ output.
Here is an example for 1.8
C:\…> svnversion .
22923:22924M
C:\...>svnversion . > output.txt
C:\...>type output.txt
22923:22924M
And here is the same example but now for 1.9
C:\…> svnversion .
22923:22924M
C:\...>svnversion . > output.txt
C:\...>type output.txt
M
22923:22924
Note that if the sandbox is not modified the first line is an empty one.
Question:
Why is the M (sandbox modified) on a separate line?
How do I get ‘1.8’ behavior back for this 1.9 version of svnversion?
Kind regards.
André Steenveld | Software Engineer | Production Onderhoud, Ontwikkeling & Support
MARIN | T +31 317 49 34 30 | A.H.M.Steenveld@marin.nl <ma...@marin.nl> | www.marin.nl <http://www.marin.nl>
<https://www.linkedin.com/company/marin> <http://www.youtube.com/marinmultimedia> <https://twitter.com/MARIN_nieuws> <https://www.facebook.com/marin.wageningen>
MARIN news: Viscous free-surface power predictions for self-propulsion using a hybrid RANS-BEM coupling procedure <http://www.marin.nl/web/News/News-items/Viscous-freesurface-power-predictions-for-selfpropulsion-using-a-hybrid-RANSBEM-coupling-procedure.htm>
RE: svnversion output changed when redirecting the output. Why?
Posted by "Steenveld, Andre" <A....@marin.nl>.
The version I use:
c:\...>svn --version
svn, version 1.9.1 (r1698128)
compiled Sep 1 2015, 19:50:43 on x86-microsoft-windows
This version is having the documented behaviour.
I checked for an update now I've 1.9.3 installed.
C:...>svn --version
svn, version 1.9.3 (r1718519)
compiled Dec 13 2015, 15:47:16 on x86-microsoft-windows
svnversion behaves as expected in this version.
Problem solved, thanks.
Kind regards,
Andre Steenveld.
André Steenveld | Software Engineer | Production Onderhoud, Ontwikkeling & Support
MARIN | T +31 317 49 34 30 | mailto:A.H.M.Steenveld@marin.nl | http://www.marin.nl
MARIN news: http://www.marin.nl/web/News/News-items/Accurate-calculation-models-for-manoeuvring-simulations-1.htm
-----Original Message-----
From: Ivan Zhakov [mailto:ivan@visualsvn.com]
Sent: donderdag 11 februari 2016 08:23
To: Steenveld, Andre
Cc: users@subversion.apache.org
Subject: Re: svnversion output changed when redirecting the output. Why?
On 10 February 2016 at 18:09, Steenveld, Andre <A....@marin.nl> wrote:
>
> Hi,
>
> I’m working with svn (via TortoiseSVN) versions 1.7, 1.8 and 1.9 and due to external factors I cannot bring it up to the same version.
>
> Also, I’m using svn via the TortoiseSVN package but I believe that my question is related to svn and not to TortoseSVN, please correct me it this is not the case.
>
> I use the svnversion command to keep track of versions in my sandboxes. For this I redirect the output from svnversion to a file and use that file in other parts.
>
> For versions 1.7 and 1.8 the command line output from svnversion is identical to the redirected output. But for version 1.9 it is not and there is no command line option to get it to the `old style’ output.
>
> Here is an example for 1.8
>
> C:\…> svnversion .
> 22923:22924M
>
> C:\...>svnversion . > output.txt
> C:\...>type output.txt
> 22923:22924M
>
> And here is the same example but now for 1.9
>
> C:\…> svnversion .
>
> 22923:22924M
>
> C:\...>svnversion . > output.txt
> C:\...>type output.txt
>
> M
>
> 22923:22924
>
> Note that if the sandbox is not modified the first line is an empty one.
>
> Question:
>
> Why is the M (sandbox modified) on a separate line?
>
> How do I get ‘1.8’ behavior back for this 1.9 version of svnversion?
>
>
What exact version of TortoiseSVN 1.9.x do you use? Output of 'svn --version --verbose' command would be useful.
If I remember correctly some TortoiseSVN builds was compiled using static runtime and this caused some problems with stdout flushing.
--
Ivan Zhakov
Re: svnversion output changed when redirecting the output. Why?
Posted by Ivan Zhakov <iv...@visualsvn.com>.
On 10 February 2016 at 18:09, Steenveld, Andre <A....@marin.nl> wrote:
>
> Hi,
>
> I’m working with svn (via TortoiseSVN) versions 1.7, 1.8 and 1.9 and due to external factors I cannot bring it up to the same version.
>
> Also, I’m using svn via the TortoiseSVN package but I believe that my question is related to svn and not to TortoseSVN, please correct me it this is not the case.
>
> I use the svnversion command to keep track of versions in my sandboxes. For this I redirect the output from svnversion to a file and use that file in other parts.
>
> For versions 1.7 and 1.8 the command line output from svnversion is identical to the redirected output. But for version 1.9 it is not and there is no command line option to get it to the `old style’ output.
>
> Here is an example for 1.8
>
> C:\…> svnversion .
> 22923:22924M
>
> C:\...>svnversion . > output.txt
> C:\...>type output.txt
> 22923:22924M
>
> And here is the same example but now for 1.9
>
> C:\…> svnversion .
>
> 22923:22924M
>
> C:\...>svnversion . > output.txt
> C:\...>type output.txt
>
> M
>
> 22923:22924
>
> Note that if the sandbox is not modified the first line is an empty one.
>
> Question:
>
> Why is the M (sandbox modified) on a separate line?
>
> How do I get ‘1.8’ behavior back for this 1.9 version of svnversion?
>
>
What exact version of TortoiseSVN 1.9.x do you use? Output of 'svn
--version --verbose' command would be useful.
If I remember correctly some TortoiseSVN builds was compiled using
static runtime and this caused some problems with stdout flushing.
--
Ivan Zhakov