RE: svnversion output changed when redirecting the output. Why?

[Steenveld, Andre]

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.steenv...@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:i...@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  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: Apache 2.4, Worker MPM, SVN 1.7.20, MOD_DAV_SVN and Post-Commit Hooks

[Philip Martin]

Steffen Moser  writes:

> So my questions to you are:
>
>  1) Are there any known multi-threading problems with the combination
> Apache 2.4 MPM Worker, SVN 1.7.x, MOD_DAV_SVN and hooks?

I would expect it to work although we do not get many reports of
Subversion on Solaris so it is possible there is a bug.  Subversion 1.7
is old.

We did have a Solaris buidbot running Solaris 10 and it ran the
regression tests over svn:// with svnserve in threaded mode.  I believe
I also had success with the tests over http:// with Apache worker but I
can't remember for sure.

>  2) Is there any alternative to access an SVN repository via Apache
> besides using the MOD_DAV_SVN module in Apache? For example, can I
> possibly use "Fast CGI" to link SVN to Apache? (This is, for example,
> a solution to run the non-thread-safe PHP in a multi-threaded Worker
> MPM).

No.

>  3) What is the recommended way to solve the problem? Do I really have
> to go without a multi-threaded web server?

Is your repository BDB?  If so you could try migrating to FSFS.  If you
are using BDB which version is the library?

You could try running svnserve in threaded mode with the svn:// protocol
to see if the problem is limited to Apache.

You could try building more recent APR/Apache/Subversion.

-- 
Philip Martin
WANdisco

RE: svnversion output changed when redirecting the output. Why?

[Bert Huijben]

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.steenv...@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.steenv...@marin.nl 
  | www.marin.nl  

    
      
 
MARIN news: Viscous free-surface power predictions for self-propulsion using a 
hybrid RANS-BEM coupling procedure 

  

Re: Apache 2.4, Worker MPM, SVN 1.7.20, MOD_DAV_SVN and Post-Commit Hooks

[Philip Martin]

Philip Martin  writes:

> You could try building more recent APR/Apache/Subversion.

Since you are already building Subversion you could try running
Subversion's regression tests for Apache worker:

  make davautocheck CLEANUP=1 PARALLEL=1 APACHE_MPM=worker

-- 
Philip

Re: Help extending subclipse

[Brunoais]

what's below.

On 11-02-2016 20:54, Eric Johnson wrote:

Wrong mailing list.

You probably want the "dev" mailing list from this page:
http://subclipse.tigris.org/ds/viewForums.do

Eric.

On Thu, Feb 11, 2016 at 8:27 AM, Brunoais > wrote:


Hi,

I want to make a plugin to the subclipse.
Broadly speaking, it would work like this:

When the commit dialog appears, below the "", I want to add a file browser window that allows
to choose a file location in the filesystem.

For that file, I want to create a listing (full file path) of all
the files that are being committed (additions, editions and
deletions). That record is made only when the commit is issued, no
need to do it before that.

I also want to associate the file to where it is stored and the
message written in the commit messages list, but that's for later.

For starters, I need to know to which extension points should I
attach my code to and which dependencies will my code need. Are
you able to help me? Anything is welcome.

Thanks in advance

Re: Apache 2.4, Worker MPM, SVN 1.7.20, MOD_DAV_SVN and Post-Commit Hooks

[Philip Martin]

Steffen Moser  writes:

>  | Running tests in commit_tests.py [43/84]..success

One of the tests in commit_tests.py is 'hook_test' which runs start-,
pre- and post- hooks.  So it appears that your build can run hooks.

Not clear why you get a hang in your normal configuration.  Perhaps one
of the other Apache modules?  If you attach a debugger (dbx?) to the
process a stack trace might provide a clue.  The stack trace will be
more useful if you have debug symbols but your binaries may be compiled
without.

-- 
Philip Martin
WANdisco

Re: Apache 2.4, Worker MPM, SVN 1.7.20, MOD_DAV_SVN and Post-Commit Hooks

[Steffen Moser]

Hi Philip,

thank you very much for your fast reply!

On 02/11/2016 11:41 AM, Philip Martin wrote:
> Steffen Moser  writes:
> 
>> So my questions to you are:
>>
>>  1) Are there any known multi-threading problems with the combination
>> Apache 2.4 MPM Worker, SVN 1.7.x, MOD_DAV_SVN and hooks?
> 
> I would expect it to work although we do not get many reports of
> Subversion on Solaris so it is possible there is a bug.  Subversion 1.7
> is old.

You are absolutely right, it is quite old, but I haven't had the time
yet for integrating 1.8.x or 1.9.x into Solaris' build system.

Fortunately, there are only two quite small patches from Oracle which
the build system applies when compiling 1.7.x. Most probably, I just
have to look what is actually needed of these patches and in how far I
have to modify them to get 1.8.x or 1.9.x built. Most of the patched
items are related to the directory position of libraries in the system.

A simple exchange of 1.7.20 by 1.9.3 in Oracle's build tools failed as
it it doesn't apply the patches (but I tried it only quite quickly
today) correctly.

> We did have a Solaris buidbot running Solaris 10 and it ran the
> regression tests over svn:// with svnserve in threaded mode.  I believe
> I also had success with the tests over http:// with Apache worker but I
> can't remember for sure.
> 
>>  2) Is there any alternative to access an SVN repository via Apache
>> besides using the MOD_DAV_SVN module in Apache? For example, can I
>> possibly use "Fast CGI" to link SVN to Apache? (This is, for example,
>> a solution to run the non-thread-safe PHP in a multi-threaded Worker
>> MPM).
> 
> No.
> 
>>  3) What is the recommended way to solve the problem? Do I really have
>> to go without a multi-threaded web server?
> 
> Is your repository BDB?  If so you could try migrating to FSFS.  If you
> are using BDB which version is the library?

According to "svn/db/fs-type" it is FSFS, so non-thread-safe outdated
BDB libraries shouldn't be the cause of the problem.

> You could try running svnserve in threaded mode with the svn:// protocol
> to see if the problem is limited to Apache.

I'll try this. Thank you for the hint. I didn't know that the SVN daemon
is also capable of doing multi-threading.

> You could try building more recent APR/Apache/Subversion.

Good idea. I think I am proceeding this way:

 1) I try the SVN daemon instead of Apache/MOD_DAV_SVN.

 2) I am going to upgrade Apache from 2.4.12 to 2.4.16 as there are
binaries for Solaris 11.3 in an early access distribution:

https://blogs.oracle.com/solarisfoss/entr
/foss_evaluation_packages_for_solaris

 3) Subversion 1.7.x is indeed quite outdated. Therefore, I am going to
build Subversion 1.8.15 or, if possible, even 1.9.3.

 4) The version of APR which comes with Solaris 11.3 is 1.5.1, so it
should be not too old. Therefore I would try this as a last step.

Kind regards,
Steffen



-- 

Dipl.-Inf. Steffen Moser
School of Advanced Professional StudiesRoom: O27/317
Ulm University Tel: +49.731.50-24179
Albert-Einstein-Allee 11   Fax: +49.731.50-24182
89081 Ulm, Germany   http://saps.uni-ulm.de/

Re: Help extending subclipse

[Eric Johnson]

Wrong mailing list.

You probably want the "dev" mailing list from this page:
http://subclipse.tigris.org/ds/viewForums.do

Eric.

On Thu, Feb 11, 2016 at 8:27 AM, Brunoais  wrote:

> Hi,
>
> I want to make a plugin to the subclipse.
> Broadly speaking, it would work like this:
>
> When the commit dialog appears, below the " comment>", I want to add a file browser window that allows to choose a file
> location in the filesystem.
>
> For that file, I want to create a listing (full file path) of all the
> files that are being committed (additions, editions and deletions). That
> record is made only when the commit is issued, no need to do it before that.
>
> I also want to associate the file to where it is stored and the message
> written in the commit messages list, but that's for later.
>
> For starters, I need to know to which extension points should I attach my
> code to and which dependencies will my code need. Are you able to help me?
> Anything is welcome.
>
> Thanks in advance
>
>
>
>

Re: Apache 2.4, Worker MPM, SVN 1.7.20, MOD_DAV_SVN and Post-Commit Hooks

[Steffen Moser]

On 02/11/2016 12:01 PM, Philip Martin wrote:
> Philip Martin <philip.mar...@wandisco.com> writes:
> 
>> You could try building more recent APR/Apache/Subversion.
> 
> Since you are already building Subversion you could try running
> Subversion's regression tests for Apache worker:
> 
>   make davautocheck CLEANUP=1 PARALLEL=1 APACHE_MPM=worker

Good idea. These are the results of the autocheck script:

 | 
root@wega:~/repo-11.3/solaris-userland~gate/components/subversion/build/amd64# 
PARALLEL=1 APACHE_MPM=worker CLEANUP=1 
../../subversion-1.7.20/subversion/tests/cmdline/davautocheck.sh
 | davautocheck.sh: Using '/usr/bin/apxs'...
 | davautocheck.sh: Using '/usr/apache2/2.4/bin/httpd'...
 | davautocheck.sh: Using '/usr/apache2/2.4/bin/htpasswd'...
 | davautocheck.sh: Monolithic Auth module not found. Assuming we run against 
Apache 2.1+
 | davautocheck.sh: Found modules for Apache 2.3.0+
 | davautocheck.sh: Using directory 
'/root/repo-11.3/solaris-userland~gate/components/subversion/build/amd64/subversion/tests/cmdline/httpd-20160211-184247'...
 | davautocheck.sh: Adding users for lock authentication
 | Adding password for user jrandom
 | Adding password for user jconstant
 | Syntax OK
 | davautocheck.sh: HTTPD started and listening on 'http://localhost:5526'...
 | davautocheck.sh: HTTPD is good
 | davautocheck.sh: starting the tests...
 | ldd: 
/root/repo-11.3/solaris-userland~gate/components/subversion/build/amd64/subversion/svn/svn:
 unsupported or unknown file type
 | davautocheck.sh: Using default dav library
 | Running tests in auth-test [1/84].success
 | Running tests in cache-test [2/84]success
 | Running tests in checksum-test [3/84].success
 | Running tests in client-test [4/84]...success
 | Running tests in compat-test [5/84]...success
 | Running tests in config-test [6/84]...success
 | Running tests in db-test [7/84]...success
 | Running tests in diff-diff3-test [8/84]...success
 | Running tests in dirent_uri-test [9/84]...success
 | Running tests in entries-compat-test [10/84]..success
 | Running tests in error-test [11/84]...success
 | Running tests in fs-pack-test [12/84].success
 | Running tests in fs-test [13/84]..success
 | Running tests in hashdump-test [14/84]success
 | Running tests in locks-test [15/84]...success
 | Running tests in mergeinfo-test [16/84]...success
 | Running tests in op-depth-test [17/84]success
 | Running tests in opt-test [18/84].success
 | Running tests in parse-diff-test [19/84]..success
 | Running tests in path-test [20/84]success
 | Running tests in pristine-store-test [21/84]..success
 | Running tests in ra-local-test [22/84]success
 | Running tests in random-test [23/84]..success
 | Running tests in repos-test [24/84]...success
 | Running tests in revision-test [25/84]success
 | Running tests in skel-test [26/84]success
 | Running tests in stream-test [27/84]..success
 | Running tests in string-test [28/84]..success
 | Running tests in subst_translate-test [29/84].success
 | Running tests in target-test [30/84]..success
 | Running tests in time-test [31/84]success
 | Running tests in translate-test [32/84]...success
 | Running tests in tree-conflict-data-test [33/84]..success
 | Running tests in utf-test [34/84].success
 | Running tests in window-test [35/84]..success
 | Running tests in authz_tests.py [36/84]...success
 | Running tests in autoprop_tests.py [37/84]success
 | Running tests in basic_tests.py [38/84]...success
 | Running tests in blame_tests.py [39/84]...success
 | Running tests in cat_tests.py [40/84].success
 | Running tests in changelist_tests.py [41/84]..success
 | Running tests in checkout_tests.py [42/84]success
 | Running tests in commit_tests.py [43/84]..success
 | Running tests in copy_tests.py [44/84]success
 | Running tests in depth_tests.py [45/84]...success
 | Running tests in diff_tests.py [46/84]success
 | Running tests in entries_tests.py [47/84]

Re: Help extending subclipse

[Stefan]

Hi Brunoais,
On 2/11/2016 22:27, Brunoais wrote:

what's below.

On 11-02-2016 20:54, Eric Johnson wrote:

Wrong mailing list.

You probably want the "dev" mailing list from this page:
http://subclipse.tigris.org/ds/viewForums.do

Eric.

On Thu, Feb 11, 2016 at 8:27 AM, Brunoais > wrote:


Hi,

I want to make a plugin to the subclipse.
Broadly speaking, it would work like this:

When the commit dialog appears, below the "", I want to add a file browser window that
allows to choose a file location in the filesystem.

For that file, I want to create a listing (full file path) of all
the files that are being committed (additions, editions and
deletions). That record is made only when the commit is issued,
no need to do it before that.

I also want to associate the file to where it is stored and the
message written in the commit messages list, but that's for later.

For starters, I need to know to which extension points should I
attach my code to and which dependencies will my code need. Are
you able to help me? Anything is welcome.

Thanks in advance

I take it you wanted to forward that to the subclipse developer mailing 
list as Eric suggested. However, you ended up sending it to the 
subversion developer mailing list instead...

The subclipse dev list is d...@subclipse.tigris.org

Regards,
Stefan

Help extending subclipse

[Brunoais]

Hi,

I want to make a plugin to the subclipse.
Broadly speaking, it would work like this:

When the commit dialog appears, below the "comment>", I want to add a file browser window that allows to choose a 
file location in the filesystem.


For that file, I want to create a listing (full file path) of all the 
files that are being committed (additions, editions and deletions). That 
record is made only when the commit is issued, no need to do it before that.


I also want to associate the file to where it is stored and the message 
written in the commit messages list, but that's for later.


For starters, I need to know to which extension points should I attach 
my code to and which dependencies will my code need. Are you able to 
help me? Anything is welcome.


Thanks in advance

ApacheCon NA 2016 - Important Dates!!!

[Melissa Warnkin]

 Hello everyone!
I hope this email finds you well.  I hope everyone is as excited about 
ApacheCon as I am!
I'd like to remind you all of a couple of important dates, as well as ask for 
your assistance in spreading the word! Please use your social media platform(s) 
to get the word out! The more visibility, the better ApacheCon will be for 
all!! :)
CFP Close: February 12, 2016CFP Notifications: February 29, 2016Schedule 
Announced: March 3, 2016
To submit a talk, please visit:  
http://events.linuxfoundation.org/events/apache-big-data-north-america/program/cfp

Link to the main site can be found here:  
http://events.linuxfoundation.org/events/apache-big-data-north-america

Apache: Big Data North America 2016 Registration Fees:
Attendee Registration Fee: US$599 through March 6, US$799 through April 10, 
US$999 thereafterCommitter Registration Fee: US$275 through April 10, US$375 
thereafterStudent Registration Fee: US$275 through April 10, $375 thereafter
Planning to attend ApacheCon North America 2016 May 11 - 13, 2016? There is an 
add-on option on the registration form to join the conference for a discounted 
fee of US$399, available only to Apache: Big Data North America attendees.
So, please tweet away!!
I look forward to seeing you in Vancouver! Have a groovy day!!
~Melissaon behalf of the ApacheCon Team