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 relat

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

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

Hi all, we have an Oracle Solaris 11.3 x86_64-based server with the following components: - Apache 2.4.12(-0.175.3.0.0.30.0) - SVN 1.7.20(-5.12.0.0.0.91.0) SVN is connected to Apache with "mod_dav_svn" and I have a repository with a "post-commit" hook. The Apache package is the original pa

Re: cannot delete directory with deleted zombie-locked file

cpengr wrote on Tue, Feb 09, 2016 at 18:17:36 -0500: > Questions: > 2. How can I delete this directory tree? Try 'svn unlock --force' and 'svn rm' with URL arguments, e.g., svn unlock --force svn://svn/junk svn rm svn://svn/junk > 1. How did this happen? > 3. Do I need to take further a

Re: cannot delete directory with deleted zombie-locked file

cpengr writes: > 1. How did this happen? It could be: https://issues.apache.org/jira/browse/SVN-2507 > 2. How can I delete this directory tree? Use svn unlock URL rather than svn unlock PATH > 3. Do I need to take further action to report the issue, so the developers > can prevent